What's New in Release 12.10.0 (09/06/2023)

Important 12.9.2 feature clarification

Before diving into what's new in 12.10.0, there's an important clarification we need to address regarding the automated 45-day patient payment plan process introduced in version 12.9.2. As a refresher, this new process automatically removes patients from payment plans if they have not made a payment within 45 days from their last statement, or if 45 days have elapsed from the start of the payment plan and the last statement sent.

Prior to the implementation of this new process, there was a field under Settings > Automated payment plan called "Number of days between payment plan payments." The value entered in this field will regulate the number of days the patient has after the statement goes out to pay the bill. If the patient does not pay the bill within the number of days specified in this field, they are automatically removed from the plan. This field still exists and has not changed.

There has been some questions on how these two processes work in conjunction with one another. Here is the calcification:

  • If there is a value in the "Number of days between payment plan payments" field on the Settings page, that value takes precedent over the 45-day process implemented in 12.9.2.

  • If there is no value in the "Number of days between payment plan payments" field on the Setting page, the automated 45-day payment plan process will be enforced.

What's new in 12.10.0

Okay, let's get into what's new in 12.10.0!

We are listening! We knew there were several issues that needed our attention so instead of working on enhancements, the Billing team concentrated on bug fixes and performance improvements this time around. Because there are no enhancements, there is no 12.10.0 release video.

  • Submitting large batches: We found that some customers were having trouble sending batches with a large number of claims via the Manual Submission Queue page. To rectify this issue, we now break large batches into smaller batches of 200 or less. This is how that works:

    • A user navigates to the "Manual Submission Queue" page to submit the batch. If the number of claims within the batch exceeds 200 then when the user clicks the Submit button, the system will parse out the first 200 for the first batch and send it. The total in the "Queued claim" column will go down by 200 and the Submit button will highlight again. The user will continue to click the Submit button until all claims have been submitted in the batch.

    • All batches are sorted by last name, first name and date of service. Once a batch prints, if any additional claims are added to the batch, where the last name starts with a letter that was processed in a previous batch, that claim will appear at the top of the next processed batch. For example, if you have a batch of 1000 claims, when you click Submit, the 1000 claims are sorted and the first 200 are printed in alphabetical order. If you then add an additional claim to the remaining 800 and then pressed Submit, the 801 claims will be sorted and printed alphabetically. Therefore, if the last name on the claim you added started with an "A", that claim would appear at the top of the next group of 200 processed from the 801 remaining claims.

    • Each submission is a separate batch and will generate a PDF for that batch.

    • The Claim Batches page will show each PDF, the batch number, the number of claims in the batch, and the batch filename.

  • Batch submission failing: A customer’s batch submissions was failing in a specific date range. When the submission failed, the claims stayed in a “Queued for submission – Clearinghouse” status and were repeatedly submitted to the clearinghouse.

  • Facility payment posting: The ignored amount was impacting the outstanding balance on the facility after posting. If the balance was positive it was added to the balance, if negative,, it was subtracted from the balance.

  • Inability to delete notes made by others and attachments: Standard Users that were granted permission to delete notes made by others, and delete attachments, were unable to do so because the delete icon was unavailable.