Translating EDI 837 claims into a database requires a pre-built database, schema, and parsing solution. Archiving claim data can be used to solve healthcare data retention requirements. T-Connect's database provides all of the HIPAA X12 schemas and can be deployed quickly into your organization. Translation of EDI claims to the database, .NET object model, XML, CSV, and JSON is also supported.
Store EDI 837 Data
To become more EDI capable, Caliber Health's T-Connect database solution provides a DB for each one of the transaction sets. Easily parse a file into the data storage without any mapping or coding. The solution is a complete end-to-end workflow that can poll a windows file folder, pick up the file, translate, validate X12, and store every data element into a relational data store.
Reporting for 837
Once snapshots of your EDI 837 data is loaded, organization can start to report off of the data. Reports to correlate EDI 835s or integrate EDI into your existing applications. Organizations can also run post-validation rules for encounter submissions and other outbound processing such as claim repricing, auditing, and other revenue cycle activities.
Correlating 837 Claims, 820 Remittances, and 999 Acknowledgements
Storing claim data also provides correlation capabilities for request and response tracking. Here are some examples:
- 999 acknowledgements for the 837 claims
- Correlate 837 EDI data with 277-CA claim acks to determine exactly what part of the claim was accepted or rejected
- 837 claims to 835 remittances can be very helpful determining claims paid across many different files, processes, and days
Here is an example of T-Connect query to pull claim, claim acknowledgements, and remittance advice transactions:
Find out more about T-Connect by visiting our product overview page!