charge, claim, payment, patient, and patient_insurance it relates to, where known.
This table’s columns and relationships are shown in the Hosted Database schema.
The relational columns are all nullable - a transaction only carries the ones that apply to it, so
charge_id, claim_id, payment_id, patient_id, and patient_insurance_id are frequently empty. patient_id and patient_insurance_id are also empty when the Elation Billing record does not map to an EHR entity.- Payments vs. adjustments by practice or date (
type) - The full financial history behind a single claim or charge
- Adjustment reason codes (
code) and their amounts - Reconciling a payment against the transactions it produced