ERA charge-level adjustment records with HDB practice, provider, and appointment cross-references applied. Each row represents one charge-level adjustment within an ERA. The table schema can be found in our HDB dbdocs reference. For reporting on but not limited to:Documentation Index
Fetch the complete documentation index at: https://help.elationhealth.com/llms.txt
Use this file to discover all available pages before exploring further.
- Adjustment totals by payer, practice, or service date
- Denial rates and denial reasons by CPT code
- Per-appointment revenue when joined to the appointment table
- Per-provider revenue when joined to canonical_physician
- Drill-down on a specific claim or charge
Each row carries a match_confidence column that grades the appointment-id inference. Filter to
match_confidence = 'provider_match' for high-trust per-provider analytics. The provider_mismatch class is common in practices that bill incident-to (charges file under a supervising physician while visits are scheduled under the rendering NP or PA), and the appointment_id on those rows points at the supervisor’s appointment rather than the rendering visit. patient_practice_date_only and no_match rows have a null appointment_id.Charges and adjustments for a date range
Pulls every charge-level adjustment row for a given service-date window with the per-row financials and payer detail.Practice-level totals over a period
Rolls up charges, adjustments, and totals per practice and payer for a given service-date window. Useful for AR snapshots and payer-mix analysis.Per-appointment revenue
Joins ERA rows to the appointment that produced them. Filters toprovider_match so each appointment’s totals reflect a confident link to the rendering provider’s visit.
The
era_matched_adjustment table lives in your elation_billing schema while the appointment table lives in your standard schema. Either set your default schema or qualify both tables with their schema names when running this query.