elation_billing schema. The schema is populated for practices on the Elation Billing product; non-EB customers will see the schema present but empty.
New Tables
| Table | Added in | Description |
|---|---|---|
| era_matched_adjustment | 1.9.1 | ERA charge-level adjustment records with HDB practice, provider, and appointment cross-references applied. |
| user_role | 1.9.1 | Lookup mapping Elation Billing role identifiers (Admin, Biller, Staff, etc.) to human-readable names. |
| claim | 1.9.3 | The bill submitted to a payer for a patient visit, with the EHR bill, patient, practice, and five denormalized provider roles. |
| authorization | 1.9.4 | Prior authorizations issued by payers to patients at a practice, including authorized units, validity dates, and an active flag. |
| charge | 1.9.4 | Charge line items - the per-CPT lines on a claim, with units, total charged, adjustments, payments, and outstanding balance. |
Release Highlights
era_matched_adjustment (1.9.1) Each row represents one charge-level adjustment within an Electronic Remittance Advice, joined to HDB’s practice and canonical-physician identifiers and, where possible, the originating appointment. Thematch_confidence column grades the appointment-id inference - filter to provider_match for high-trust per-provider analytics. Other values (provider_mismatch, patient_practice_date_only, no_match) indicate progressively weaker attributions; provider_mismatch is common in incident-to billing where charges file under a supervising physician while the visit is scheduled under the rendering NP or PA. See the ERA Matched Adjustment article for example queries.
user_role (1.9.1)
Use the user_role lookup to translate role identifiers on Elation Billing user records into the labels shown in the application. See the User Role article for example queries.
claim (1.9.3)
One row per Elation Billing claim - the bill submitted to a payer for the services on a patient visit. Each claim links to its patient, practice, service location, and the EHR-side bill it corresponds to (via bill_id, empty when no matching bill exists in HDB). Provider data is denormalized: for each of the five Thor provider roles the row carries the provider’s name and NPI directly:
rendering_provider_name/rendering_provider_npireferring_provider_name/referring_provider_npisupervising_provider_name/supervising_provider_npibilling_provider_name/billing_provider_npiordering_provider_name/ordering_provider_npi
is_billed), reconcile claims to EHR bills (bill_id), follow corrected and voided resubmissions (icn, icn_code), or roll up volume per provider via the rendering or billing NPI. See the Claim article for example queries.
authorization (1.9.4)
Prior authorizations issued by payers, with authorized units, validity dates, and an active flag. There is no built-in “units used” counter; join claim on claim.authorization_id to see how an authorization has been consumed. The claim.authorization_id field is only populated when staff explicitly linked the authorization on the claim, so untagged claims will not appear in the join. See the Authorization article for example queries.
charge (1.9.4)
One row per Elation Billing charge line - the per-CPT detail beneath a claim. Each row carries the CPT and modifiers, units, line note, NDC drug fields, and the running financial state: total_charges, adjustments, payments, and balance, plus balance_responsibility (the party currently on the hook). Use charge to split patient-AR from payer-AR, drive a “ready to bill” worklist (first_billed is null), reconcile claim totals against the sum of their lines, or report per-CPT volume and revenue. For the per-ERA adjustment history rather than the latest running totals, use era_matched_adjustment. See the Charge article for example queries.
Tables in the
elation_billing schema are scoped to EB-qualified practices. If your practice is not on Elation Billing, the schema is provisioned but empty.