ERD

Inpatient medication administration database

This medication administration ER diagram models the core records needed for an inpatient electronic medication administration record. A patient can have an admission, and an admission can receive many medication orders. Each order identifies a formulary medication, dose, route, and status. Individual administration records capture the time, administering nurse, and result.

UPDATED 2026-09-23
TYPEErd
USE-CASEHealthcare
EXAMPLEInpatient medication administration database
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

An inpatient pharmacy workflow needs separate records for the patient stay, prescribed medication, order, and each administered dose.

Key decisions

  • Admissions link patients to a unit and admission time.
  • Medication NDC is unique in the formulary table.
  • MedicationOrder carries dose, route, and status.
  • Administration records each dose time and nurse identifier.
  • One order can have many administrations.

When to reuse this

This model supports a basic eMAR design. Production medication systems need clinician identity, verification, allergy, interaction, and audit controls.

FAQ

Frequently asked questions

Why record each administration separately?01
One order may result in multiple doses, each with its own time and outcome.
What is an NDC?02
A National Drug Code identifies a specific drug product in the U.S.
Can a patient have several admissions?03
Yes. The Patient-to-Admission relationship supports many stays over time.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.