'/%3e%3cpath%20d='M92%2044a34%2034%200%201%200%204%2033H66'%20fill='none'%20stroke='%23fff'%20stroke-width='12'%20stroke-linecap='round'%20stroke-linejoin='round'/%3e%3ccircle%20cx='96'%20cy='32'%20r='9'%20fill='%23FF6A2B'/%3e%3c/svg%3e)
About
Health records that follow the patient, not the building
GSHS exists because a Nigerian patient's history is scattered across paper folders in facilities that cannot talk to each other — and because fixing that must not mean handing everybody's records to everybody.
How GSHS started
The idea began with a familiar scene: a patient arriving at a new hospital with a plastic bag of old results, a half-remembered drug name and no way to prove any of it. Clinicians repeat tests because they cannot trust what they cannot see. Patients pay twice. Pharmacies dispense against documents they have no way to check.
The obvious answer — put everything in one national database — is the wrong one. It concentrates risk, and it takes the decision away from the person the records are about. So GSHS took a different route: give each patient one health identity, keep each hospital's records under that hospital's control, and make sharing an explicit, time-limited act the patient authorises.
Around that core we built what a working facility actually needs day to day — registration, consultations, prescribing with real allergy checks, laboratory and imaging, pharmacy stock, admissions and billing — because a consent model attached to records nobody keeps properly is worth nothing.
The principles we build to
Validate before reveal
A hospital asking about a patient from another facility learns only that the identity exists and is active. Nothing about the person is disclosed until that person authorises it.
Consent has a shape
Permission is never a blanket yes. A patient chooses what categories of record are shared, with whom, and for how long — and can withdraw it before it expires.
Nothing happens unseen
Every registration, disclosure, emergency access and configuration change is written to an audit trail that administrators and oversight officers can read and filter.
Safety beats convenience
An allergy conflict blocks the prescription rather than warning about it. Stock that is not there cannot be dispensed. The system is designed to be hard to bypass quietly.
Who is behind it
Golad leadership
Founding team
GSHS is built by Golad Technologies Limited, a Nigerian technology company working in health infrastructure. Named leadership profiles and photographs are being finalised and will be published here.
Clinical advisory group
Practising clinicians
Consultants, pharmacists and laboratory scientists from Nigerian facilities review each module before release, so workflows match how care is actually delivered here rather than how a textbook describes it.
Governance & privacy
Data protection
A dedicated privacy function owns the consent model, break-glass review and audit retention, and is the point of contact for regulators and hospital compliance teams.
Head office
Come and take it apart
We would rather you tested the awkward parts — consent, audit, emergency access — than watched a polished slide deck.