01
Patient Identity
One patient. One record. Everywhere.
In the first pilotWithin one facilitySee the module Patient IdentityPre-launch · Selecting the first cohort
Health infrastructure for Africa,starting with Sierra Leone's clinics.
HealthOS is the shared record beneath hospitals, clinics, insurers and ministries. One record for every visit, prescription and payment, built to grow into shared national infrastructure — engineered for the connectivity, regulation and scale African health systems actually operate in.
Built for hospitals, clinics, insurers, and public health systems
HOS-DEMO-0001Illustrative: Fictional data. Not a live system.
- 01 Clinic · Identity matched
- 02 Laboratory · Lab result attached
- 03 Pharmacy · Prescription dispensed
- 04 Insurer · Claim validated
- 05 Ministry of Health · Counted in the national view
Illustrative. One record moving between facility types. Not live data; no real facilities are shown.
Engineered to the standards national systems require
HL7 FHIR R4
Clinical data exchange
ICD-11 · SNOMED CT
Coded diagnoses and terminology
OpenHIE architecture
National exchange patterns
ISO 27001 controls
Information security baseline
Data residency
Set by national law
Standards HealthOS is built to. Formal certification follows first production deployment.
Starting with clinics
Designed first for a clinic's working day.
The first pilot is with clinics. It covers four jobs that take a clinic's time every day and every month.
Daily takings and cash-up
Each payment is recorded against the visit it pays for, so the day is cashed up against a record, not a notebook.
Prescriptions and pharmacy stock
Medicines are dispensed against the prescription, and stock comes down as they are dispensed.
The monthly facility return
The monthly return is drawn from the visits already recorded, not counted again by hand.
Works offline
Work carries on when the connection drops, and is sent when it returns.
The problem
Africa is not short of healthcare software. It is short of healthcare infrastructure.
Facilities have systems. What they do not have is a layer beneath those systems that agrees on who the patient is, what happened, and who pays. Every initiative built without that layer starts by rebuilding it.
Follow one patient
One visit. Five institutions. One record.
Follow a fictional patient through a single episode of care. Each institution adds to the same record instead of starting its own.
Illustrative: Fictional data. Not a live system.
Skip past the patient storyPlatform roadmapThe first pilot includes patient records within one facility, clinical operations, the clinic's own pharmacy and billing. The rest is the roadmap.
01 · Clinic
Registers at a clinic
In the first pilotThe problem
The patient has no continuous identity
A patient is a new patient at every facility. History, allergies, results and prescriptions stay in whichever building produced them, so clinicians decide with a fraction of the record.
Care restarts at every door
Identity matched
The clinic finds her existing record instead of opening a new one.
02 · Laboratory
Has a blood test
RoadmapThe problem
Systems cannot address each other
Lab, pharmacy, billing and insurance run separate software with no shared contract. Every connection becomes a bespoke project instead of a property of the platform.
Integration as a project, not a property
Lab result attached
The result is written to the same record the clinician is reading.
03 · Pharmacy
Collects her prescription
the clinic's own dispensary
In the first pilotPrescription dispensed
The pharmacist sees what was prescribed and dispenses against it.
04 · Insurer
The visit is claimed
RoadmapThe problem
Money moves slower than care
Claims are assembled by hand after the fact, from notes that were never structured for adjudication. Rejections are discovered weeks later, and the facility carries the float.
Revenue detached from the encounter
Claim validated
The claim is checked against the encounter it pays for, before it is submitted.
05 · Ministry of Health
The visit is counted
RoadmapThe problem
The national picture arrives too late to act on
Capacity, utilisation, disease signal and spend are reassembled by hand each reporting cycle, from sources that disagree. By the time the picture is complete, the decision has passed.
Reporting cycles, not real time
Counted in the national view
The visit appears in the same numbers the ministry reads, from the same source.
The platform
Five systems that most countries buy separately. One record underneath.
HealthOS is not a suite of products that integrate. It is one data layer with five surfaces on top — which is why identity, care, money and intelligence stay consistent without an integration programme.
Platform roadmapThe first pilot includes patient records within one facility, clinical operations, the clinic's own pharmacy and billing. The rest is the roadmap.
02
Clinical Operations
The whole clinical day on one record.
In the first pilotSee the module Clinical Operations03
Revenue Cycle
Claims that are complete before they are submitted.
Billing · pilotClaims · roadmapSee the module Revenue Cycle04
Health Intelligence
The operational picture, while it still matters.
RoadmapSee the module Health Intelligence05
Multi-Facility Control
One platform, an entire network.
RoadmapSee the module Multi-Facility ControlWho it serves
One record. Four institutions that have never shared one.
Care is delivered by providers, financed by payers and stewarded by government. HealthOS is designed so all three read and write the same record instead of reconciling three versions of it.
Hospitals
Admissions, theatre, wards, laboratory, pharmacy and billing on one record.
Departments stop re-entering what another department already knows.
See the page for hospitals and clinicsClinics
Fast registration, structured notes and same-day billing without an IT department.
Designed to run on the staff and hardware the clinic already has.
See the page for hospitals and clinicsInsurers
Structured, coded claims arriving from the encounter that produced them.
Fewer rejections, shorter cycles, a smaller fraud surface.
See the page for insurersGovernments
Capacity, utilisation and spend assembled from live facility data.
A national picture that is current, not a quarterly reconstruction.
See the page for ministriesPublic health agencies
Surveillance and programme monitoring on the data clinicians already record.
Disease signal in its first week, not its first month.
See the page for ministriesHealthcare networks
Shared standards across sites with local workflow autonomy.
One operating picture across every facility in the group.
See the page for hospitals and clinicsWorks where the network does not
Try it: cut the network.
Illustrative clinic
Illustrative: Fictional data. Not a live system.NetworkOffline
Working offline. New events are kept on this device.
- 08:12Lab test orderedQueued on this device
- 08:08Prescription dispensedQueued on this device
- 08:04Patient registeredSynced
First deployment
We are building in Sierra Leone first
A platform that claims to serve a continent and starts everywhere serves nobody. HealthOS is being built for one national health system first — its facilities, its payers, its regulator, its connectivity — because a shared record has to work completely somewhere before it can work anywhere.
Expansion follows proof, not funding rounds.
If it runs where you are, the next step is a conversation. Not a procurement process. We are selecting the first cohort of facilities now.
Request a briefing