The product
An operating system, not a set of forms over a database.
Three things make something an operating system: it runs regardless of the environment, it provides primitives other things are built on, and it schedules and supervises the work. HealthOS is built to do all three.
01 — Runs anywhere
Connectivity is a feature tier, never a dependency.
The device layer is complete, not a demo mode. If a feature only works online, we don't consider it finished. The hub is transport, not intelligence. The cloud is the arbiter that everything converges to.
- Layer 3
HealthOS Cloud
Needs internetRemote access, multi-branch consolidation, backup, and the supervision engine that watches every facility.
- Layer 2
Facility Hub
Needs only the building networkA small box on the building LAN. Every device in the facility stays in sync with no internet at all.
- Layer 1
Device
Needs nothingEvery clinical and operational workflow, complete, on the device itself. Encrypted local database.
Each layer degrades into the one below it. Cloud unreachable, the building keeps running. Hub down, every device keeps working. Everything reconciles when the connection returns — with no one pressing anything.
02 — Supervises
Software that behaves like a member of staff who never sleeps.
Recording what happened is the easy half. HealthOS watches the data fabric and acts on it — which is the difference between a system of record and a system that actually runs the place.
Clinical rules that fire on real events
Configurable rules watch the data as it is written — critical lab values, medication-safety checks, deterioration signals — and raise alerts and tasks without anyone opening a dashboard.
Escalation that finds a person
When something needs a human, the system goes and finds one. It doesn't wait for the right person to happen to check the right screen.
Guarded paths for sensitive actions
Death recording, sentinel events and medication safety get their own deliberate flows — never a stray button sitting next to a routine action.
Work that routes itself
Pay for a lab test at the desk and the request is created and the patient sent to the lab — not back through triage. Visit types route themselves at the point of payment.
03 — One record
Every department composed from the same primitives.
The patient, the encounter, the order, the charge, the audit entry — every module is an application built on those, which is why theatre and mortuary and accounting genuinely share one record instead of exchanging files.
Patient flow
From the front desk through consultation — one continuous queue, not four handoffs.
Inpatient care
Bed management, nursing charting and dietetics — the ward's daily rhythm, in one place.
Specialty units
Theatre, maternity, dialysis and blood bank — specialty care with its own workflows, still one record.
Diagnostics
Lab and imaging results land straight in the chart, never a separate system to check.
Pharmacy
FEFO dispensing and department sub-stores, keeping every ward's cabinet stocked and expiry-safe.
Supply chain
Central store to procurement to supplier returns — full inventory chain, fully accounted for.
Finance
Billing, claims and accounting all reconciled against one charge master.
Records & compliance
Statutory registers and incident reporting, held to the same audit trail as everything else.
Operations
HR, payroll and shift management, plus built-in messaging and reporting across every branch.
04 — Built for health data
The security model, stated plainly.
Most vendors assert this in a sentence. Here is what is actually implemented, so you can hold us to it.
PHI encrypted at rest
The encryption service initialises before anything touches patient data — not as a later pass over records already written.
Role-gated access
Every module and action is permission-checked against the signed-in role, enforced on the server rather than hidden in the interface.
An audit trail that cannot be edited
Every clinically or financially significant action is recorded. The log is append-only — entries cannot be altered or removed, including by an administrator.
NDPR-aligned handling
Built to Nigerian data-protection expectations, with the authoritative record protected so no single device can corrupt or destroy shared truth.