Family links, allergies and long-term conditions travel with the patient to every visit — not just the one open on your screen right now.
One record per patient, for the life of that patient — not one folder per visit. Family links (a household under one head), allergies and long-term conditions are captured once and travel forward to every future appointment, note, prescription and bill automatically.
Every clinic on the platform runs on this module — it is the one thing every other module is built on top of.
A patient's history lives in whichever register, app or memory the last visit happened to land in.
Without a carried-forward record, the same allergy question gets asked at every visit — and sometimes it isn't.
A mother, child and grandmother end up in three disconnected paper folders instead of one household record.
The same person, re-registered under a slightly different phone number, quietly splits their own history in two.
Every patient row carries its clinic's id and is filtered by it with a database-level scope on every query. If that scope can't resolve a clinic — a platform-level request, for instance — it returns nothing rather than guessing. One clinic's staff cannot see another clinic's patients under any normal use of the product.
Nothing else in OPD Suite writes a visit, a note, a prescription or an invoice without attaching it to a patient record — appointments, consultation notes, e-prescriptions and billing all hang directly off this module.