ChatDiagram
ERD · Healthcare · Scheduling

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.

類型 ERD標準 Chen 1976 / Everest 1976 (crow's foot)引擎 schematex-erd更新時間 2026/9/22
Outpatient clinic scheduling
Drawing preview
需求

“Create an outpatient clinic scheduling ERD with Patient, Provider, Location, Appointment, and Encounter tables, the shown keys and attributes, appointments for patients with providers at locations, and optional encounters documenting appointments.”

接著試試Add appointment reminders.Add insurance coverage.
這張圖裡有什麼

看懂背後的決策。

01

Medical record number is unique on Patient.

02

Provider NPI is unique for provider identification.

03

Appointment links patient, provider, and location.

04

Encounter is optional per appointment because cancellations may not create a visit.

05

Appointment status preserves scheduling state.

This core model suits ambulatory scheduling and can be expanded with insurance, referrals, clinical notes, and billing. Protected health information requires appropriate security controls.

瀏覽所有 ERD 範本 →

常見問題

常見問題

Why separate Appointment and Encounter?

An appointment can be cancelled or missed, while an encounter records an actual clinical interaction.

Can an appointment have more than one encounter?

This model assumes one optional encounter; complex workflows can add a visit or encounter-part table.

What is an NPI?

It is a U.S. National Provider Identifier used to identify healthcare providers.