Architecture
A layer, not an application
HealthOS sits beneath the systems a country already runs. Facilities keep what works; the record, the identity and the exchange move to a layer everyone can address.
- 01
Points of care
Hospitals, clinics, laboratories and pharmacies — using HealthOS directly, or connected through the API while they keep existing systems.
- 02
Exchange and identity
The master patient index, terminology services, consent and the audit trail. This is the layer that makes a record portable between institutions.
- 03
System of record
One clinical and financial history per patient, versioned and auditable, with residency and retention designed to be governed by national policy.
- 04
Consumers
Payers adjudicating claims, ministries measuring capacity and disease signal, and facilities running their own operations — all reading from the same source.
Open standards, documented API
HL7 FHIR R4 resources and a documented REST API. Connecting a system that already exists must never require a bespoke project.
Works where the network does not
Facility operations are designed to continue through an outage and reconcile on reconnection. Intermittent connectivity is a design constraint, not an edge case.
Incremental adoption
A network can start with identity alone, or one facility, or one department, and extend. Nothing requires a single-step national cutover.
Works where the network does not
Try it: cut the network.
Illustrative clinic
Illustrative: Fictional data. Not a live system.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
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