WHO Africa Unveils Health Data Hub to Connect Fragmented Systems

WHO’s African regional office has unveiled an operational version of a health data platform intended to connect information that is now scattered across disease programmes, national reporting systems and incompatible software. The Regional Health Data Hub was presented as health ministers and senior officials from 47 countries met in Addis Ababa for the regional committee, placing a long-running informatics problem at the center of the continent’s health agenda.

The hub is not yet the finished, automatically connected continental system its name may suggest. WHO describes the current release as a minimum viable product: a working proof of concept with country pages, dashboards, cloud hosting and a central repository. A beta is planned for 2027, while seamless exchange with national systems and a region-wide governance protocol remain 2030 goals. That distinction matters because the project’s value will depend less on a polished portal than on whether countries can supply timely, comparable and trustworthy data.

From separate programmes to one data layer

The immediate ambition is to reduce the fragmentation created when malaria, immunization, tuberculosis, HIV, workforce and surveillance programmes collect and store information separately. According to WHO’s detailed progress report, datasets covering those areas, as well as polio and sexual and reproductive health, have already been loaded into a centralized data lake.

The platform uses international interoperability and metadata standards and is being aligned with other regional systems through a hub-and-spoke model. In practical terms, that should make it easier to compare an outbreak signal with immunization coverage, workforce availability or health-facility capacity instead of asking analysts to reconcile incompatible spreadsheets and databases during a crisis. The live hub provides the common entry point, while national systems remain the sources and custodians of much of the underlying information.

The operational need is visible in the region’s simultaneous burdens. A ministry responding to Ebola, cholera or measles must understand where cases are occurring, which facilities can isolate and treat patients, how quickly laboratories are reporting and whether supplies and trained staff can reach the affected area. Those facts often live in different programme systems. Connecting them does not replace field investigation, but it can reveal where the next question should be asked.

This is a consequential change in architecture. A regional dashboard can display indicators, but a shared data layer can also support routine exchange, reproducible analysis and a consistent definition of what each indicator means. Without those foundations, two countries may report similarly named measures that were collected at different intervals or calculated from different populations. The hub’s metadata work is therefore as important as its visible charts.

AI arrives before the data problem is solved

WHO is incorporating predictive analytics and artificial intelligence to forecast trends, identify health risks, fill some data gaps and support early warning. A chatbot can already search datasets and generate summary reports. Those functions could shorten the distance between a question from a health ministry and an actionable answer, especially when an analyst needs to compare multiple disease and system indicators quickly.

But AI cannot make inconsistent source data reliable. WHO’s own system assessment places the region’s overall health-information-system maturity at 58 percent, an “early” level, based on assessments completed by 37 countries in 2024. It also records striking variation, from 29 percent in Mauritania to 85 percent in Tanzania. Although use of DHIS2 for centralized reporting expanded from 32 countries in 2019 to 43 in 2023, shared software does not automatically produce shared definitions, complete records or timely submissions.

The most responsible use of the hub’s AI layer will therefore be to expose uncertainty rather than conceal it. Forecasts should show missingness, update frequency and confidence; summaries should link back to their source datasets; and decision-makers should be able to see when an apparent trend reflects a reporting change. Otherwise, a faster analytical system could distribute a weak signal more efficiently without improving the decision it supports.

Eighteen countries are shaping the first version

WHO has engaged 18 countries in reviewing the initial platform and the accompanying governance framework: Benin, Burkina Faso, Central African Republic, Chad, Côte d’Ivoire, Democratic Republic of the Congo, Ethiopia, Guinea-Bissau, Kenya, Liberia, Mali, Niger, Rwanda, Senegal, Sierra Leone, South Sudan, Tanzania and Zambia. Each has nominated focal points to align technical content with national priorities, negotiate data-sharing arrangements, establish interoperability and pilot the system.

That country involvement is essential because a regional repository cannot simply extract national data and call the result integration. Ministries need to retain authority over official figures, correct errors and understand who can access what. WHO’s earlier geodatabase offers a useful precedent: national focal points maintain verified information on health facilities, population and administrative boundaries, while automated comparisons and quality checks help manage changes over time.

The same model is harder when records concern disease surveillance, reproductive health or other potentially sensitive domains. The current governance framework sets principles for ownership, stewardship, access rights, privacy and confidentiality, but the formal protocol is not due until 2027. Until those rules are endorsed and implemented, expansion should be measured by trusted data-sharing relationships—not simply by the number of datasets copied into the lake.

Infrastructure remains the decisive constraint

The progress report is unusually direct about what could derail the project. Different software, standards, architectures and reporting formats still impede comparison. Limited bandwidth, unreliable electricity and inadequate information technology infrastructure can interrupt access and delay exchange. Funding reductions could constrain maintenance, upgrades, support and training, while weak national systems may not generate data of sufficient quality in the first place.

WHO recommends low-bandwidth and offline-capable systems, along with solar power and battery banks where necessary. That is more than an implementation detail. A hub designed around continuous broadband would privilege better-connected ministries and facilities, reproducing the very visibility gaps it is supposed to close. Screens for direct dashboard access are planned for member states, but connectivity, local analytical capacity and resilient workflows will determine whether those screens inform decisions or become static displays.

The financing case also requires discipline. The World Bank argues that digital health investment should prioritize problems, connect existing systems and scale what works, rather than digitize for its own sake. For the regional hub, that means testing whether it improves concrete decisions: allocating vaccines, identifying an outbreak sooner, locating understaffed districts or reconciling facility lists before an emergency response.

A platform becomes infrastructure only through use

The hub now sits inside a broader institutional redesign. WHO Africa’s Vision 2035 calls for data management, analytics and digital health systems to share one regional infrastructure, reducing duplicated costs and inconsistent standards across programmes. That makes the hub both a technology project and a test of whether organizational silos can actually be dismantled.

The near-term milestones are concrete. The development team must turn feedback from the 18 pilot countries into a stable 2027 beta, finalize data-sharing agreements, publish the governance protocol and prove that low-connectivity users can work reliably. It should also report measurable quality indicators: dataset completeness, reporting delays, interoperability coverage, corrections, user activity and examples of decisions changed by the evidence.

If those measures improve, the hub could become the connective tissue for disease surveillance, service planning and health-system accountability across the region. If they do not, it risks becoming another portal layered on top of fragmented national systems. The launch in Addis Ababa is therefore an important operational milestone, but the real achievement will be a trusted regional practice in which countries can exchange data without surrendering stewardship—and act on it before a preventable gap becomes a crisis.