> ## 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.

# 2026-11-19

This release adds 81 relationships to the [entity relationship diagram](https://dbdocs.io/hosteddb_support/hosted_database_snowflake), so more of the ways your Hosted Database tables join are documented in one place. It is non-breaking under [Change Management](https://help.elationhealth.com/articles/hdb/change-management.md): no table or column changes.

## New Relationships

| Table | Column | Joins to |
| - | - | - |
| med\_order\_fill | `med_order_id`, `patient_id`, `medication_id` | `med_order.id`, `patient.id`, `medication.id` |
| med\_order\_thread | `latest_med_order_id`, `discontinue_order_id`, `patient_id`, `practice_id` | `med_order.id`, `discontinue_med_order.id`, `patient.id`, `practice.id` |
| med\_order\_icd10\_codes | `med_order_id`, `icd10_code` | `med_order.id`, `icd10.id` |
| med\_order, discontinue\_med\_order, referral\_order | `prescribing_user_id` | `user.id` |
| misc\_orders | `patient_id`, `practice_id`, `prescriber_user_id` | `patient.id`, `practice.id`, `user.id` |
| lab\_order | `ordering_provider` | `user.id` |
| lab\_order\_answers | `lab_order_id` | `lab_order.id` |
| patient | `practice_id`, `primary_physician_user_id`, `primary_care_provider_id`, `patient_passport_user_id` | `practice.id`, `user.id`, `canonical_physician.id`, `user.id` |
| health\_maintenance | `patient_id`, `doc_tag_id`, `lab_report_id` | `patient.id`, `document_tag.id`, `report.id` |
| vital\_bp | `vital_id`, `patient_id`, `practice_id`, `visit_note_id` | `vital.id`, `patient.id`, `practice.id`, `visit_note.id` |
| visit\_note | `physician_user_id` | `user.id` |
| visit\_note\_bullet | `parent_bullet_id`, `replaced_by_visit_note_bullet_id` | `visit_note_bullet.id` |
| office\_messages, office\_messages\_recipients | `sender_id`, `sent_to` | `user.id` |
| passport, passport\_message\_thread | `sender_practice_id`, `user_id` | `practice.id`, `user.id` |
| patient\_history | `icd9_id`, `snomed_id` | `icd9.id`, `snomed.uq_snomed` |
| patient\_problem\_code\_hcc | `icd10_id` | `icd10.id` |
| icd10, icd9 | `imo_id` | `imo.uq_id` |
| external\_patient\_id | `master_id` | `master_patient.id` |
| user | `canonical_physician_id` | `canonical_physician.id` |
| medication, service\_location, t\_qualified\_patient | `practice_created_id`, `practice_id` | `practice.id` |
| bill | `billing_provider_id`, `rendering_provider_id`, `supervising_provider_id` | `user.physician_id` |
| med\_order, patient\_immunization, health\_maintenance, passport, provider\_availability | `supervising_physician_id`, `administering_physician_id`, `ordering_physician_id`, `physician_id`, `recipient_physician_id` | `user.physician_id` |
| claim | `authorization_id`, `account_id`, `co_pay_id` | `authorization.id`, `elation_billing_account.id`, `payment.id` |
| charge | `last_billed_id` | `patient_insurance_eligibility.id` |
| clearinghouse\_transaction, era\_matched\_adjustment, insurance\_eligibility\_check, patient\_insurance\_eligibility | `claimmd_payer_id` | `payer.payer_id` |

The seven patient forms tables in the `early_release` schema also gain their relationships, joining each other and `patient`, `practice`, `appointment` and `report`.

## Release Highlights

**Medication history joins end to end**

A fill now joins to the order it fills, and a prescription thread joins to its latest order and to the order that discontinued it. With `med_order_icd10_codes`, you can follow a medication from the prescription to its fills and the diagnoses it was ordered for.

**Physician columns join to `user.physician_id`**

The bill's billing, rendering and supervising providers, the supervising physician on a prescription, and the physician columns on `patient_immunization`, `health_maintenance`, `passport` and `provider_availability` all hold a physician id rather than a user id. Join them to `user.physician_id`, not `user.id`. Columns named `*_user_id`, such as `prescribing_user_id`, join to `user.id`.

**Elation Billing**

A claim joins to its authorization, its billing account and its co-pay payment. `charge.last_billed_id` joins to `patient_insurance_eligibility.id`, the coverage the charge was last billed to, not to `patient_insurance`. Many charges hold `0` or nothing in `last_billed_id`, and those rows don't join. `claimmd_payer_id` joins to `payer.payer_id`.

**Joining tables**

The diagram now opens with a note on how to read its relationships. They show which columns join, and they are a guide rather than a guarantee:

* An `id` column isn't always unique. `icd10.id` and `icd9.id` repeat once per IMO mapping, so a join on `icd10.id` can return several rows per diagnosis code.
* A foreign key column can be empty, or hold a value with no matching row.
* The `uq_` column on a table, where there is one, is the column that is unique per row.

*If you have any questions about this topic please reach out to [Elation Support Portal](https://help.elationhealth.com/articles/support-portal-introduction.md) with the subject line HDB - \<your\_question>*
