Release 16.22.0 - November 16, 2026

Highlights

New features

Enhancements

Improvement: Universal Import Now Uses the Patient’s Default Office When the File Has No Office

Universal import files often contain only the data exported by the EHR, frequently omitting the office location. Previously, the system defaulted such claims to the practice’s main office when no office was on the file. This resulted in inaccurate location data for patients seen elsewhere, requiring manual correction.

With this release, when a Universal Import file doesn’t include an office location, CMD now uses the patient’s default office for the claim. 

First Pass Claim Count Gadget Now Refreshing Daily

(Re-releasing): Our "First Pass Resolution Rate" dashboard gadget had not been refreshing on a daily basis due to performance issues. With the recent move of Data Snapshots and reporting queries to a Read Replica database, additional capacity became available in our nightly database processing, allowing gadget refresh times to be moved earlier. 

With this release, the First Pass Resolution Rate (Claim Count) gadget will now update daily, giving you more current data each time you view it. 



Resolutions

Resolved Issue: Insurance Transfer Amount Report Field Not Returning Insurance Transfers

Resolved an issue where, the Insurance Transfer Amount report field didn’t work as intended. It looked for the source of an applied account credit in a way that never matched, because CMD always records the source of a transfer as 1. A single applied account credit can draw on several account credits, which can come from different payers, so CMD doesn’t record one source for it. As a result, the field didn’t pick up your insurance transfers.

With this release, the field now checks the account credit that funded the transfer. If more than one credit was used, CMD uses the one with the largest amount. If several have the same amount, it uses the one entered first.

Resolved Issues: Universal Import Reliability

In this release, we resolved multiple universal import issues:

Adding a Blank Insured Party and Marking Patients and Claims Incomplete: Corrected a Universal Import issue where, if you imported claims for existing patients with Universal Import, and your file had insurance details such as an authorization number or the patient’s relation to the insured but no payer, the import added a new, blank insured party to each patient instead of using the insurance already on file. Because the new insured party had no name, the import then marked every patient and claim from the file as incomplete.

Using the Fee Schedule Price Instead of the Price in the File: Corrected a Universal Import issue where, the “Set charge pricing based on unit price received in interface message?” interface setting was not being respected and Universal Import still used the price from the fee schedule for the charge (not the unit price in your import file). Basically the import preview showed the file’s price, but the claim that was created had the fee schedule price.

Import Failing With a Generic Warning and Creating Duplicates When Retried: Resolved a universal import issue where, in some cases, an exception stopped a Universal Import partway through. You saw a generic warning and stayed on the message preview screen, and nothing prevented you from clicking again. Each retry started the import over, so repeated attempts could create duplicate import formats and duplicate patients and claims.

Resolved Issue: ERA Claims Not Matched When the Member ID Has Leading Zeros or the Last Name Is Formatted Differently

When an ERA doesn’t send back the TCN, CMD matches each payment to a claim using patient details. One of the matches uses the member ID, last name, date of service, procedure code, and billed amount. It didn’t work in two cases:

  • Member IDs that start with zeros.
  • Payers that format the last name differently from how it’s stored in CMD.

In those cases the payment showed a Claim Not Found error, and you had to select each claim by hand. This release resolves this issue and CMD now matches claims correctly. 

Resolved Issue: Reference Numbers and Authorizations Lost When Combining Claims

Corrected an issue where, when you combined claims in Claim Control, the new combined claim didn’t carry over the Original Reference # or the authorization numbers and types from the claims you combined.

With this release, combining claims now copies the Original Ref. # fields and the authorization numbers to the new claim.

This issue has been fixed and the Refund to Original option is no longer shown when there is nothing left to refund on the payment.

Resolved Issue: WebAPI Request Failing When a Patient Reference Number Is Too Long

Corrected an issue where, if an integration sent a patient reference number longer than 20 characters through the WebAPI, the request failed. CMD allows 20 characters in this field. The response was confusing since it said "SUCCESS" but gave the message “Unexpected error trying to process claim review,” so it looked as if the request had worked when it hadn’t been fully processed.

This issue has now been fixed. If a patient reference number is longer than 20 characters, CMD now ignores that value and processes the rest of the message normally. The patient or claim is then created without the reference number.