For clinics that run on stations, not appointments
A visit is not a straight line.
The doctor sends a patient to the lab. The lab sends them back. Meanwhile nobody at the front desk can say where anyone is or how long they have been waiting. Software that models a visit as one appointment cannot describe that morning. This does.
- 08:41Reception
- 08:52Triage
- 09:10Consultation
- 09:48Laboratory
- 10:20Consultationsent back
- 10:41Pharmacy
- 10:55Billing
One morning, as the system records it. The dotted line is the part most clinic software has no way to express.
Routing
Who may send a patient where is data, not code.
The allow list lives in a table. A clinic that adds a physiotherapy room changes a row, not a release. Send a patient somewhere the routing does not permit and the system refuses.
Patient privacy
The clinical database cannot read a name.
Names and national IDs sit in a separate schema, encrypted, behind a different database role. Everyday clinical work runs on a connection that was never granted access. Not “does not”. Cannot.
select * from clinical.visits; ok select * from identity.patients; denied
Chronic care
Who hasn’t come back.
A paper file holds a reading. It cannot produce a list, every morning, of the diabetes and hypertension patients whose review date has passed. For a clinic built on lifestyle disease, that list is the whole point.
14
overdue this morning, across four programmes