ERD (Entity Relationship Diagram)

The ERD is the map of a system's data: what information is captured, how it connects, and what rules govern those connections. Executives who can read one gain X-ray vision into a vendor's system — because data structure, more than any feature list, reveals what the software actually treats as real.

What It Is

An Entity Relationship Diagram is a visual model of a database: entities (the noun-things the system tracks — Patient, Order, Invoice), their attributes (the fields on each), and the relationships between them (an Order belongs to exactly one Customer; a Patient may have many Prescriptions). Crow's-foot notation lines show cardinality — the one-to-one, one-to-many, many-to-many rules that encode business truth. An ERD is drawn early in design and maintained as the schema evolves; a stale ERD is a symptom, not a document.

Why It Matters to You

Reading an ERD lets you interrogate a system at the level that outlasts interfaces. If a vendor's ERD has no entity for the thing your business considers central — consent, referral, alert, whatever your domain's irreducible noun is — no amount of UI will fix that, and discovering it after deployment is catastrophically expensive. ERDs also expose integration reality: two systems can only share data cleanly where their entities and relationships align, and every mismatched relationship is future manual reconciliation work. You do not need to draw ERDs; you need to be able to point at one and ask why two entities connect the way they do.

When You'll Meet It

In design reviews and vendor due diligence. Ask for the ERD of any system you are buying — hesitation to produce one tells you either the schema is undocumented or the design will not survive scrutiny.