7.5.0 Release Notes

Expected Release Date: Tuesday 4/10/2024

Feature Enhancements:

Release 7.5.0


Populate authorization number on 837i file



When creating an 837 institutional (837i) file, if there is an authorization number on the line item, then the REF✱G1 line populates with the authorization number on the file.


When an authorization has different details/number, then it should be on a separate CLM line.



Populate SV202-07 on 837I & Populate SV101-07 on 837P (procedure code description)



SV202-07 on 837I & SV101-07 on 837P now populate with the procedure code description, so that payers will not reject claims for a "non-specific procedure code."



Resolved Issues:

Release 7.5.0


Statement Dates showing as zeros in 837i file



Statement Dates/Date of Service were not populating correctly in Institutional claim (837i) files for the Medicaid Party Type.


Previously, if there was an Activity Code Override by Insurance with the inpatient box checked (Path: Maintenance and Setup > Activity Codes > Activity Code Insurance Coverage > Activity Code Insurance Coverage Override by Insurance), the 837 Institutional file would populate without Statement Dates or Dates of Services. This has been corrected.



"Only use Diagnosis from line item" error



Previously on the 837 Form, when using the Only use Diagnoses from Line Item check box, depending on your filters, you might receive an internal error. The internal error has been resolved.



Adjustments Kicking down for mass grant payments: IDPH


In File > Billing> Bulk Insurance Payment, the Bulk Insurance Payments Form was kicking down any remaining balance when the Adjust Off Credit box was checked and the Adjustment Note was in the Transaction Note Not To Kickdown List.

The balance now adjusts off using the Adjustment Note instead of kicking down to the next payer to cause inaccurate balances.



835 Form Error when using 'un-roll txns' checkbox


Previously, if the Un-Roll Transactions (Beta) check box was checked, you would receive an internal error when trying to open an 835 file. The internal error has been corrected.