Hospital

patients, doctors, appointments and prescriptions. 8 tables, 31 columns, no data.

The map

Each line runs from a linking column (N) to the key it points at (1). The same tables are listed below as text.

The tables

patients

id bigintPK
full_name varchar(200) required
born_on date
phone varchar(30)

doctors

id bigintPK
full_name varchar(200) required
speciality varchar(100) required

wards

id bigintPK
name varchar(200) required
beds integer required

appointments

id bigintPK
patient_id bigint→ patients required
doctor_id bigint→ doctors required
starts_at timestamptz required
status varchar(30) required

admissions

id bigintPK
patient_id bigint→ patients required
ward_id bigint→ wards required
admitted_at timestamptz required
discharged_at timestamptz

medicines

id bigintPK
name varchar(200) required
form varchar(50) required

prescriptions

id bigintPK
appointment_id bigint→ appointments required
medicine_id bigint required
dose varchar(100) required

invoices

id bigintPK
patient_id bigint→ patients required
total numeric(12,2) required
paid boolean required

What you could look at in SSDO

Ask which tables touch patients (a sensitive-looking name; SSDO only describes it).
prescriptions.medicine_id is not declared as a link: see how SSDO infers it and says so.
Open App Simulation and trace a booking from the appointment table.

Create a free workspace and open this sample All samples

PK is a primary key. “→ table” is a link (a foreign key) to that table. This page is a description of a structure we wrote; it holds no rows.