Claims workflow status
A clear boundary between billing records in Curenium and external payer exchange.
What is available now
Curenium stores bills, transactions, insurance profiles, and prior-authorization records. Staff can use those records to prepare and review billing information within the application.
What this guide does not claim
The current code does not establish a production ANSI 837 submission path, an ERA/835 reconciliation service, automated claim scrubbing, denial routing, or scheduled batch submissions. Those processes require payer or clearinghouse integration and end-to-end validation before they can be described as live features.
Continue to use your approved payer and clearinghouse process for submission, acknowledgments, denials, and reconciliation. An internal Curenium record is not a payer response.
Back to insurance and billing