API v2 covers billing data from the Elation EHR, not the Elation Billing product.API v2 gives you access to billing information captured in the patient chart, such as bills, billing codes, and outstanding balance. Integrations typically use these endpoints to send visit charges from Elation to a third-party practice management system, and to surface patient balance information in the Elation EHR.Claims, insurance payments, remittances, and patient statements belong to Elation Billing and aren’t available through API v2. Patient payments collected outside Elation can be recorded as patient liabilities. Practices using Elation Billing can query that data in the Hosted Database — see Claim, Charge, Payment, and ERA Matched Adjustment.
In the EHR
A bill contains the billing information associated with a visit note. Practices review draft and signed bills in Billing Home.Working with bills via the API
- Bill retrieval follows the visit note’s release state. By default, the list and retrieve endpoints return a bill only after its associated visit note is signed or the bill is explicitly released to the practice management system before signing. Pass
include_unreleased=trueto also read bills on unsigned visit notes, for example to review codes before the note is signed. - Bills on unsigned visit notes are drafts. Their codes can still change until the visit note is signed. Re-read a bill after the note is signed before relying on its codes, and send only bills where
ready_for_pmsistrueto a practice management system. - Creating a bill does not guarantee immediate GET visibility. Create Bill can return
201 Createdwith a bill ID while List Bills returns no result and Retrieve Bill returns404. Retain the ID returned by POST and do not retry creation based only on an empty list or404, because the stored bill can cause the repeated POST to fail as a duplicate. Passinclude_unreleased=trueto read the bill back before its visit note is signed.