Public health agencies
Surveillance and programme monitoring on the data clinicians already record.
Disease signal in its first week, not its first month.
Who it serves
HealthOS for ministries
Capacity, utilisation and spend assembled from live facility data. A national picture that is current, not a quarterly reconstruction.
04
Health Intelligence
The operational picture, while it still matters.
Occupancy, throughput, stock, revenue, clinical quality and disease signal computed on live data — the same numbers for the ward manager, the finance director and the ministry, because they come from one source.
- Live operational dashboards
- Clinical and financial analytics
- Statutory and donor reporting
- Decision support at the point of care
Facility today
Data residency
Designed to be deployed in-country where regulation or policy requires it. The sovereign deployment model is designed so patient data never has to leave the jurisdiction that governs it.
Deployment
Three ways to run it. One codebase.
How HealthOS is hosted is a procurement and sovereignty decision, not a product decision. The platform is designed to be the same in all three.
Sovereign / on-premise
Illustrative: A simplified diagram, not an architecture specification.Inside the country
Your infrastructure
Government or institutional
- Data
- Keys
- Operations team
In-country cloud region
National or regional provider
- —
HealthOS
Regional hosting and operations
- HealthOS support
Data and keys will sit inside government infrastructure. Your team will operate it, with HealthOS support.
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.
Questions we are asked
The questions procurement asks first
Relevant to youWhere does patient data live?
Wherever national law requires. HealthOS is designed to deploy to managed cloud, to an in-country region, or inside government infrastructure. The sovereign model is designed so that data never has to leave the jurisdiction that governs it.
Relevant to youHow do you handle consent across facilities?
Consent is a recorded object with scope and expiry, not an implicit property of holding a login. Cross-facility access will be granted against that record, and every access written to an immutable audit trail.
Relevant to youWhich country are you starting in?
Sierra Leone. HealthOS is founded and built by Sierra Leoneans, and the first deployment is at home rather than in whichever market looked most convenient. The constraints here — intermittent connectivity, mixed-capacity facilities, constrained budgets — are the constraints that make a platform portable to the rest of the continent. Expansion follows proof.
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