The scenario
Design an ER diagram for a heart disease research database that tracks patient demographics, risk factors, cardiac imaging, treatments, and outcomes to support clinical studies.
What is in this drawing
Read the decisions behind it.
01
Used native erd syntax with table blocks and named cardinality refs (crowsfoot) instead of mixing Mermaid erDiagram.
02
Separated patient demographics from risk factors, imaging, treatments, and outcomes to normalize research data.
03
Modeled many-to-many between Patient and ResearchStudy via an Enrollment table with composite primary key.
When building a relational schema for medical research databases requiring normalized patient data, longitudinal records, and study enrollment tracking.
More like this