Trust That Travels

A nurse at a border clinic is holding a vaccination card she cannot check. The patient crossed overnight with a paper record, a phone full of photographs and a clinical history held somewhere in a system the clinic has never heard of. She can accept the card on faith, repeat the vaccine, or turn the patient away. None of those choices is good medicine, and each one costs money the health system does not have.

Repeat that moment across more than fifty countries and millions of traders, students, migrant workers and displaced families, and you have the practical shape of Africa's interoperability problem. The difficulty is rarely that nobody has written a standard. It is that a record produced in one country carries no proof the next country can rely on.

The stakes are rising. Most African countries are pursuing Universal Health Coverage (UHC), the goal that everyone can use the health services they need without financial hardship, and most are using digital health to get there. That drive has made integration and interoperability, including across borders, a priority. Coverage that works only inside one country's systems leaves out exactly the people who move.

The standards exist. The trust does not.

The policy groundwork is more advanced than many outsiders assume. The African Union Health Information Exchange (AU-HIE) guidelines and standards were launched in Nairobi in March 2023, with 38 member states represented, setting out what each country must meet to reach health data interoperability [1]. The Smart Africa Digital Health Blueprint, validated by the Smart Africa Board of Heads of State on 12 November 2025, points countries to international standards such as HL7 Fast Healthcare Interoperability Resources (FHIR), the leading standard for exchanging health data, and notes that Africa CDC encourages member states to adopt them [2]. The number of countries in the WHO African Region with a digital health policy or strategy rose from 20 to 36 of 47 between 2016 and 2022 [3].

Yet in January 2026, when the Africa Centres for Disease Control and Prevention (Africa CDC) launched its Central Data Repository, it described public health data on the continent as still "fragmented and dispersed across multiple systems that are often not interoperable" [4]. That matters, because Africa CDC also reports that public health emergencies across the continent rose by 40% between 2022 and 2024, reaching 213 incidents [4]. Outbreaks do not wait at border posts.

Standards tell two systems how to format a record. They do not tell a clinic in one capital whether to believe a record signed in another. That second question is about trust, and it is the one African interoperability keeps stumbling over.

Why interoperability keeps stalling

A 2026 scoping review of interoperability in Africa found wide differences between countries, with Uganda, South Africa and Kenya showing more momentum, and named the same obstacles again and again: limited technical capacity, fragmented infrastructure and weak regulatory support [7]. On the ground, six problems tend to arrive together.

1. Systems built for programmes, not for patients

Many digital health investments have been vertical and partner-driven: an HIV system here, an immunisation register there, each designed for one programme and one funder [8]. Each works on its own terms. None was designed to speak to the others, let alone to a neighbouring country.

2. Meaning that does not survive the journey

Two systems can exchange a file perfectly and still disagree on what it says. A vaccine code, a test result unit or a date format that means one thing in one register can mean something else in another. Moving data is the easy part. Keeping its meaning intact is harder.

3. Power and bandwidth

Any design that assumes a constant connection to a central server fails in a rural clinic on a generator, or at a border post with one bar of signal. Checks that only work online will not be used where they are needed most.

4. Sovereignty

No ministry of health will pour its citizens' records into a database run by another government, a donor or a foreign company, and it should not have to. Many continental data proposals stall at exactly this point.

5. Trust between institutions

Even when a record arrives intact, the receiving clinician needs to know who issued it, whether that issuer is recognised, and whether the record has since been withdrawn. Paper certificates are easy to forge, and a scanned PDF is no better.

6. Capacity and cost

Proprietary platforms with per-facility licences price out exactly the health systems that need connection most, and they leave ministries dependent on vendors for every change.

How GDHCN solves the trust problem

The Global Digital Health Certification Network (GDHCN) is WHO's answer to the trust question, and its design is simple enough to explain in one sentence: countries share keys, not patients.

It works like passport control. A border officer does not phone the issuing government to confirm every passport; they check security features the issuer is known to use. In GDHCN, each participating country lodges its public cryptographic keys in a directory that WHO manages. When a health authority issues a digital certificate, such as a vaccination record or a test result, it signs it with its private key. Any participant using the directory can then confirm that the certificate came from a recognised authority and has not been altered [9].

WHO never holds or sees the personal data inside those certificates; that stays with each country [9][10]. Participation is voluntary, and the network follows WHO SMART Guidelines and HL7 FHIR specifications, so it fits the standards African countries are already adopting [10]. It grew out of the EU Digital COVID Certificate system, which connected 76 countries and territories, and has been run by WHO since 2023 [5].

That history also shows the gap. Only four countries in the WHO African Region (Benin, Cabo Verde, Seychelles and Togo) were able to join the EU network [5]. In October 2025, the EU and WHO agreed an €8 million grant for 2025 to 2028 to widen GDHCN adoption in sub-Saharan Africa, working with regional partners including Africa CDC [5]. WHO also sees the network as a route to a digital International Certificate of Vaccination or Prophylaxis (ICVP), the Yellow Card, in line with the updated International Health Regulations (IHR) [5]. In March 2026, the International Organization for Migration (IOM) became the first international organisation to join, bringing people on the move into scope [11].

How the pieces fit together

Before looking at the software, it helps to see the whole picture. Cross-border trust in Africa works at three levels, and each level has a different owner.

Only one thing crosses the border: the patient, carrying a record that proves itself.

How BulletTrain does it

BulletTrain is Symphonix-Health's open-source, FHIR-native interoperability engine, released under the Apache 2.0 licence. Among its services is a GDHCN service that handles the full life of a cross-border health certificate: issuing it, checking it, and withdrawing it when needed. In outline:

The certificate carries its own proof. No central database is consulted about the patient.

Challenge by challenge

Set against the six obstacles above, this is how the combination of GDHCN and BulletTrain responds.

There is a wider caution too. Africa CDC's model for assessing health information exchange maturity has four domains: leadership and governance, management and workforce, ICT infrastructure, and standards and interoperability [12]. Software speaks to one and a half of those. The rest is institutions, people and money, and no platform substitutes for them.

Where a ministry can start

Cross-border interoperability does not begin with a continental platform. It begins with one certificate that already crosses borders, between two countries that already share patients.

1. Settle who holds the key. Decide which body signs on the country's behalf, and keep the private key in hardware the ministry controls. Everything else depends on this.
2. Start with the Yellow Card. Vaccination certificates already cross borders on paper, WHO sees GDHCN as the route to a digital version, and forged cards carry a real public health cost.
3. Test with a neighbour before a continent. Two ministries issuing and verifying each other's certificates in a real border clinic will teach more than any pilot confined to one country.
4. Build on what exists. Connect the immunisation register and electronic record systems already in place, rather than commissioning another vertical system.

The frameworks are written and the funding is moving. The certification network already exists. The remaining work is to connect Africa's clinics to it in a way that ministries own, clinicians can use offline, and patients never have to think about.

Universal Health Coverage that stops at the border is not universal. Making a health record trusted wherever the patient goes is part of the UHC promise, not an extra. That is the work BulletTrain was built for.