Outpatient clinic scheduling database
This outpatient clinic scheduling ER diagram centers the appointment as the record that joins a patient, provider, and physical location. It then treats an encounter as a separate, optional record for the completed visit. That distinction supports common operational states such as booked, cancelled, no-show, checked in, and completed.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
A clinic needs a normalized core schema for booking visits and recording whether scheduled visits became encounters.
Key decisions
- Medical record number is unique on Patient.
- Provider NPI is unique for provider identification.
- Appointment links patient, provider, and location.
- Encounter is optional per appointment because cancellations may not create a visit.
- Appointment status preserves scheduling state.
When to reuse this
This core model suits ambulatory scheduling and can be expanded with insurance, referrals, clinical notes, and billing. Protected health information requires appropriate security controls.
Frequently asked questions
Why separate Appointment and Encounter?
Can an appointment have more than one encounter?
What is an NPI?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.