New Relationships
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. Withmed_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
idcolumn isn’t always unique.icd10.idandicd9.idrepeat once per IMO mapping, so a join onicd10.idcan 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.