Highlights
| New Features | Enhancements |
|---|---|
| EOB Info Available in Claim & Follow Up Sections |
WebAPI Enhancements |
New features
EOB Information Now Available in Claim & Follow Up Sections
When working claim appeals and denials, users were previously having to juggle multiple windows to see the claim EOB details. In this release, we added a new tab that allows customers to quickly access this information directly within the Claim and Follow Up Management sections so that users can access this information without the need to leave the current screen. The new EOB Info tab is available from the side-panel dropdown (in the Claim and Follow Up sections) and will allow users to view the EOB details including remittance code information. 
To view the EOB details, click the desired check information to open the EOB details window. 
This new tab applies to manually posted insurance payments and applied ERAs. For more info on viewing the EOB Info from a claim or Follow Up, visit our View EOB Info On Claim or View EOB From Follow Up Help Articles.
Enhancements
Web API Enhancements
We added some updates and improvements to the WebAPI so that the following data that was previously only supported either on HL7 or XML is now supported on both.
- Last Menstrual Period: Added Support for receiving the Last Menstrual Period field on inbound claim messages (HL7 claims). This was previously supported only on XML.
- Accident/Illness Date: Added Support for receiving the Accident/Illness Date field on inbound claim messages (XML claims). This vital information for PT and Worker's Comp providers was previously supported only on HL7.
- Race, Ethnicity, Language: Added Support for receiving the Meaningful Use fields for Race, Ethnicity, and Language on inbound claim messages (XML claims). This Meaningful Use information was previously supported on HL7 but undocumented on XML.
Please note that customers need to update the data they send to CMD to take advantage of these new available fields.
We also added a Provider Matching Warning. This means that if a provider name is sent in the interface message and the system selects a provider where the first and last name (or just organization name) is not an exact match, the system will create the claim as usual. However, it will post a Warning message to Interface Tracker stating that the provider was selected based on ID even though the name does not match.
Increased Maximum Length of TCN Prefix
Currently users can enter a TCN Prefix in the Practice section. This is typically done by Support and used by the clearinghouse, but some users may set their own if they do not share an NPI across multiple CMD customers.
Previously, this field was limited to 4 characters. Based on customer requests and considering that our TCNs are 11 characters long and the maximum TCN length in ANSI is 20 characters, we increased the length of the TCN Prefix and Statement TCN Prefix fields to 6 characters. 