What we build

Nine areas, all of the same shape: a health institution owns it, a district officer uses it on a phone, a director reads it on Monday morning, and it still works in three years.

Disease surveillance and emergency response

The daily picture an emergency centre needs, reported from the district rather than assembled by hand.

Event and case reporting from the district upward, on a phone, in Somali and English.
Readiness from a checklist the ministry approves, never from a score we invented.
Reminders, escalation and a clear view of what is late and who holds it.
Partners and observers see aggregates. No names, no phone numbers, no personnel records.

Points of entry and cross border health

International Health Regulations work made operational at an airport, a land crossing and a seaport.

Health declaration before arrival, answered on the application the traveller already has.
A health pass with a single use code, and verification by scanning on an ordinary phone.
One clear verdict at the desk: valid here, wrong border, already used, expired, or refer.
Follow up of travellers under monitoring, and a national view of arrivals by border and by country of travel.

Registries and health information systems

The list an institution has to be able to trust: who, where, in what state, as of when.

Facilities, health workers, clients, assets and stock. One record per real thing, with the history of every change kept.
Roles and approvals that follow the administrative structure. A district sees the district. Nobody edits above their level.
Every create, update, verify and approve writes an audit row. A record is archived, never deleted.
Import from what exists already: spreadsheets, an old database, a paper form typed once at the district.

Reporting and decision support

Numbers a director can act on the same morning, from the data the system already holds.

Dashboards that open on a phone in a few seconds on a weak connection.
The weekly and monthly figures produced once, so a programme and a partner quote the same number.
Fixed template reports, weekly and monthly, filled from the database so two people cannot produce two different numbers.
Exports an analyst can open without asking us, and documents produced by the system with the institution’s emblem on them.

Health information exchange and interoperability

The connective layer. One picture for the ministry, instead of six logins and three spreadsheets.

Facility and health worker registries that every other system points at, so there is one list and not seven.
A client registry, so one person is one record across facilities rather than a new file at each door.
HL7 FHIR for client level exchange with electronic record systems, and DHIS2 for aggregate reporting.
Terminology and coding two systems can agree on, with the interfaces published so the next supplier can use them.

Community health and the frontline workforce

The largest health workforce in the region works outside facilities, and mostly without a system.

Community health worker registries and master lists: who is active, where, trained in what.
Household and client follow up that works with no signal and sends once the connection returns.
Supervision and task lists that put the visit which must not be missed at the top.
Referral between community and facility, and incentive or payment records with a reconciliation trail.

Health facility technologies

Where a facility needs a system, we adapt proven open source rather than writing something new.

Electronic medical records, laboratory, pharmacy, stock, appointments and referral, on established platforms.
Sized to what the facility can actually run, including the hours when power and connectivity are partial.
Configured with the people who will use it, in their language, with their forms.
Connected upward, so what the facility records reaches the national system without a second entry.

Data, analytics and applied artificial intelligence

A model prepares the work. A written rule and a person decide it.

Reading documents: guidelines, registers and scanned forms turned into data a system can use.
Language: translation and plain language rewriting between Somali, Arabic and English.
Patterns across reports that a weekly human review would miss, proposed for investigation rather than acted on.
Queues ranked so the reviewer sees the most important case first, with the whole queue still visible.

Policies, guidelines and toolkits

Technology is half of a national system. The other half is what governs it.

Data protection and privacy rules that match the national law, written so an officer can apply them.
Cybersecurity practice, access control and what to do in the first hour of an incident.
Standards adoption, digital health strategy and the investment case that pays for it.
Procurement requirements that keep the country out of a single vendor, and operating procedures for the people who run the system.

In every system, whether it is asked for or not

Somali and English in every screenArabic when the public needs it. Translation sits in files, not in code, so the ministry can correct a word without a release.

Row level security in the databaseScope is enforced where the data lives, not only in the interface. A test proves it for every role.

Audit from the first commitWho did what, when, and what the value was before. This is the part that survives an inspection.

Export and exitA full export of data and documents at any time, in open formats, with the schema written down.

Low bandwidth as a design ruleOne stylesheet, one script, pages measured in tens of kilobytes. Tested on a slow connection, not only on fibre.

If your problem is not on this list

It is still worth a call. The shape of the work in health is usually the same: a register, a rule, a report, and a person at a desk who has to act on it today. The same methods carry beyond health when an institution asks.

Talk to us