Sovereign health data: why it matters and what it costs

In 2025, USAID and PEPFAR dramatically reduced funding for health programs in Ethiopia and other countries. The disruption was swift and brutal. It also made something abstract suddenly concrete: the countries that had allowed their health data to live in external systems, managed by international organizations or private vendors, were stuck.

They couldn't access their own data. They couldn't modify or redeploy systems. They couldn't make rapid decisions without consulting foreign stakeholders. Their health systems were hostage to external policy shifts.

This is why Opian is fundamentally committed to data sovereignty. Not because it's politically correct. Because the USAID disruption proved it matters.

What data sovereignty actually means

Data sovereignty is often framed as a political principle. It's not. It's infrastructure.

It means: - Patient health data is stored in-country, on infrastructure the country controls. - The country has the legal and technical ability to modify, redeploy, or shut down the system without vendor permission. - Data moves across borders only with explicit government authorization. - Health systems are not dependent on external cloud providers, vendors, or donor organizations for core operations.

The real cost

Here's what people usually don't want to talk about: sovereignty is not free.

Building systems that work offline and on-premise is harder than building SaaS. It requires more testing, more documentation, more support for country-specific infrastructure. The development roadmap is slower because you can't just push code to a central server; you have to work with countries on deployment and integration.

Hosting on a government's own servers is more expensive than cloud infrastructure when you account for operations and maintenance. Countries need to hire people, buy equipment, and maintain that infrastructure.

This cost is worth paying. But it's real.

Opian chose this approach because we believe it's the right one, but we don't pretend it's cheaper or easier. It's the long, harder path.

What changed when PEPFAR withdrew

When the disruption hit, organizations that had bet on external systems had to rebuild from scratch. Countries had to negotiate data handovers. Health systems lost access to dashboards and tools.

Opian facilities in Ethiopia kept working. The data was in the Ministry of Health's systems. The platform was running on in-country infrastructure. There was no renegotiation, no data export, no switching costs. When funding changed, the health system continued.

That's the value of sovereignty. Not control for control's sake. Resilience. Continuity. The ability to make your own decisions about your own health system.

Why it matters for Africa specifically

Sub-Saharan African countries are particularly vulnerable to the model of external data dependency. Most health information systems are built by international organizations and funded by donors. When donor priorities shift, so does the infrastructure and tools.

This has happened repeatedly. Systems built with one funder's money become unusable when that funder leaves. Countries are left with fragments of data in different clouds, incompatible formats, and no way to knit them together.

If African countries are going to own their health systems, they have to own their data. And that starts with the decision to build systems that are designed for in-country operation from day one.

What this means for Opian's product

ForLab+ and Link are both built on this principle. The database lives in-country. The system works offline. Deployments are modular so that countries can run just the pieces they need. There's no vendor lock-in because the architecture is open and documented.

This makes us slower to scale and harder to operate than a pure-SaaS competitor. But it also means that if we disappeared tomorrow, the health systems we built with would continue to work. The data would still be there. The system would still function.

That's the commitment.

Last reviewed: February 2026