This release adds five Elation Billing tables to the Hosted Database, completing the lookup-table set that surrounds Elation Billing claims, and documents the claim -> legal_entity relationship.
New Tables
| Table | Description |
|---|
| legal_entity | The tax-ID-holding billing group a practice bills claims under. Referenced by claim.legal_entity_id. |
| worklist | Claims flagged onto a biller worklist, with the claim’s outstanding balance at the time. |
| worklist_reason | The reason a claim was placed on a biller worklist. |
| tag_system | The Elation Billing tag catalog - tag definitions (label, color, type), including global Elation defaults. |
| tag | Individual tags applied to claims, patients, and other billing entities. |
Schema Changes
| Table | Column | Description |
|---|
| claim | legal_entity_id | Now documented as a foreign key to the new legal_entity table - the billing entity the claim was submitted under. The column already existed; this release adds the documented relationship. |
Release Highlights
legal_entity
The tax-ID-holding billing group a practice bills under - name, tax id, NPI, taxonomy, addresses, and the default-entity flag. Each claim records the entity it was billed under via claim.legal_entity_id, now documented as a foreign key so the relationship shows up in the schema/ERD. See the Legal Entity article for example queries.
worklist
Claims flagged onto a biller worklist, with the claim’s outstanding balance captured when it was flagged. Joins to the claim via claim_id (the Elation Billing claim id, claim.id - not the EHR bill). See the Worklist article for example queries.
worklist_reason
The free-text reason a claim was placed on a worklist, joined to the claim via claim_id. A worklisted claim can have one or more reasons. See the Worklist Reason article for example queries.
tag_system
The catalog of tags (label, color, type) a practice can apply, including the global Elation defaults (for example QUEUED, BILLED) replicated per practice with a null practice_id. The custom flag separates practice-created tags from Elation defaults. See the Tag System article for example queries.
tag
Individual applied tags. The tagged object is identified polymorphically by related_id + tag_type; the label and color come from tag_system via tag_system_id. For claim-type tags, related_id is the Elation Billing claim id and joins to claim.id. See the Tag article for example queries.
These tables are present only for practices on the Elation Billing product. If your practice is not on Elation Billing, they are not created in your Hosted Database.
