New Features and Updates

Setup

Payers

U12965 - New ERA Payer ID field: When ERAs are loaded into the system, we check the payer ID in the ERA file against the payer ID in the payer setup to determine the associated payer. However, there are instances where the payer sends a different payer ID in ERAs than what is used in the payer setup. To correctly assign the payer, we have added a new editable ERA Payer ID field under Setup > Payers > Submission. This field will also be checked for a match when an ERA is received.

EMR

Summary Chart

E17489 - Shut down Legacy Timeline: We have completely removed the existing legacy timeline from the patient charts and transitioned to the modern timeline component. With this update, all legacy timeline components have been shut down and moved, eliminating any option to revert to the legacy timeline.

Bug Fixes

Setup

Location Setup

B17552 - Updox Appointment Reminders - Location Sync Not Including Location Phone Number: We resolved an issue that prevented the Service Location phone number from syncing with the Updox Portal under the location Alias phone number. A code modification now ensures that the location phone number syncs correctly when sent to Updox.

EMR

Chart Tabs

B17550 - SOAP notes and letters not allowing edits upon initial load: Corrected an issue stemming from a fix to the text editor in release 24.107 that prevented soap notes and letters from being editable upon initial load, forcing the user to click "New" or switch between templates to enable editing.

iScheduler

Appointments

B14699 - Reminder Pro Export Excluding Patients with Apostrophe in the Name: Corrected an issue within iScheduler that was occurring when doing a Reminder Pro export for a patient with an apostrophe in their name. This was preventing patients with apostrophes in their names from appearing in the export.

Billing

Claim Query

B14757 - Copy Claim - Copying the Claim Substatus When it Should Not: Resolved an issue that was causing the Claim Substatus to be copied over when copying an existing claim. Since a duplicated claim is considered new and the substatus is typically used to identify payment plans and collection letter queues (which are not applicable to the new claim), we now set a blank substatus when a claim is copied.

Batches

B17624 - Statement Batching Grace Period Off by 1 Day: The grace period calculation for the statement batching was off by one day. For example, if a user entered 28 days in the setting, it was being considered as 29 days (28 + 1). We have now corrected this by updating the statement settings calculation to account for the correct number of days.

Deposits

B15920 - Deposit Reset Not Logging the Reset User: We have corrected an issue that was preventing a Deposit Reset from logging the user that triggered it. This was also causing the audit on payments to show "changed by" admin and not to reflect the user who reset the deposit.