The scenario
A dental clinic specializing in orthodontics needs a physical data model to store patients, orthodontists, procedure catalog, treatment plans with itemized procedures per tooth, appointments, and payments.
What is in this drawing
Read the decisions behind it.
01
Separate ProcedureCatalog from TreatmentPlanItem to normalize procedure codes and default costs.
02
Model many-to-many between TreatmentPlan and ProcedureCatalog through TreatmentPlanItem with tooth_number and sequence_no.
03
Link Payment directly to TreatmentPlan to track plan-level billing.
Use this schema when building a dental or orthodontic practice management system that requires treatment plan versioning, itemized procedures, appointment tracking, and payment recording.
More like this