The Case for Patient Identity in Africa

Patient apps are often discussed as convenience: booking, reminders, results, teleconsults. Useful, but they don’t solve the deeper constraint.

In many African health systems, patients do not “exist” consistently across the ecosystem. They exist as fragments: one identity at Facility A, another at Facility B, a different member record with an HMO, and paper in between. When identity is fragmented, portability is impossible. Your history does not travel. Your benefits do not travel. Care keeps resetting.

That is the real unlock patient platforms are moving toward: a reliable identity layer that makes care and benefits portable across facilities and networks.

Why identity is the bottleneck

Identity is where small errors become system-wide friction. If a patient cannot be matched to the right record, everything downstream weakens: prescriptions, results, referrals, claims, pre-authorisations, follow-ups.

This is also a safety issue. WHO’s patient identification guidance recommends using at least two identifiers (such as name and date of birth) to match patients correctly, and its guidance on digital health interventions notes that accurate patient identification is necessary to track services across facilities and health workers.

At the system level, the problem is simple: multiple databases create multiple “truths” about the same person. That is why architectures like OpenHIE include a Client Registry (Master Patient Index) as a core component for uniquely identifying individuals across fragmented systems and linking records.

Portability is the practical test of patient-centred care

Portability is what happens when a patient moves and the system still works.

When coverage is not portable, patients are effectively restricted to specific facilities or locations. A narrative review of universal health insurance models in Africa documents cases where insurance portability is limited because eligibility is tied to where beneficiaries live or where schemes are organised.

Even where portability exists on paper, it can fail in practice when identity and eligibility checks are inconsistent at the point of care. That is when patients pay out-of-pocket “for now,” providers hesitate, and payers dispute claims later.

Several markets have attempted to tighten this chain through verification and digitised workflows. Ghana’s NHIA has referenced verification technologies, including biometric approaches, aimed at improving processes, and an ISSA case note describes Kenya’s NHIF introducing electronic claims processing to improve reimbursement turnaround time. These are not “app stories.” They are identity-and-workflow stories.

What patient apps become when identity and benefits can travel

Once a patient can be reliably identified across providers and payers, patient apps stop being a convenience layer and start functioning as a system navigation layer.

• Verification replaces guesswork: eligibility, benefits visibility, and pre-authorisation become more predictable.
• The record becomes a thread: consistent identity makes it more feasible to stitch context across visits and facilities.
• Claims become cleaner: disputes reduce when the person and encounter are verifiable. Standards like HL7 FHIR’s Patient “$match” operation and the HL7 Identity Matching guidance exist for exactly this kind of cross-organisation matching.
• Continuity becomes portable: follow-up and care plans can follow the patient’s real movement, not the boundaries of a single facility system.

The constraint that cannot be ignored: uneven connectivity

Identity and portability cannot be built on an “always-online” assumption. GSMA’s Sub-Saharan Africa reporting notes that mobile internet use is growing, but the usage gap remains large: many people are covered by mobile broadband but are not using mobile internet. 

The durable approach is multi-rail: assisted onboarding at facilities, low-data experiences, and channels beyond apps where needed.

How Helium Health intends to come in

Helium Health sits close to where identity is created and used: at the point of care, inside provider workflows. Our view is that portability will not be solved by launching another patient interface. It is solved by building a patient platform anchored in reliable identity and standards-aligned interoperability, so benefits and records can move with the patient across facilities and networks.

Practically, that means building toward:

• identity matching that can work across organisations (not only within one facility), aligned with emerging interoperability approaches (including FHIR-based patient matching guidance)
• payer connectivity that supports eligibility and benefit visibility at the moment of care
• an interoperability mindset consistent with architectures that treat client registries and interoperability layers as core building blocks

Learn more about our patient platform at www.heliumhealth.com/myhelium/

The North Star

Patient apps are useful. But in Africa, the next step is bigger than apps.

The north star is identity that works everywhere, and benefits and records that can travel. Until that exists, care will keep resetting every time a patient changes location, provider, or payer context.

The platforms that win the next phase will not be the ones with the most features. They will be the ones that solve the identity and portability layer that everything else depends on.