Building Health-Tech for Nigeria's Infrastructure Reality

The assumptions baked into most software

A lot of software is designed around a quiet set of assumptions: power is stable, internet is fast and constant, and a five-second API timeout is a rare, tolerable annoyance. Those assumptions hold in a lot of the world. They don't reliably hold in a Nigerian hospital ward or exam hall, and pretending otherwise produces systems that work perfectly in a demo and unreliably in production.

Designing for what's actually there

Both EMS and HMS are built to run on an institution's own local network specifically because that removes the internet as a dependency for the parts of the job that genuinely can't afford to fail — a live computer-based test, a clinician pulling up ward occupancy mid-shift. Connectivity is only required at the edges: licensing, and whatever reporting an institution chooses to do externally, never for the core operation itself.

Reliability as a design constraint, not a feature

We treat audit trails, role-based access, and offline-first operation as engineering requirements from day one, not things layered on once a v1 already works. That's a deliberate choice: clinical and examination software doesn't get graded on how good it looks in a pitch deck, it gets graded on whether it's still working correctly during the one moment — a mass casualty event, a national exam — where failure isn't an option.