Skip to content
PHB/Public Health Bureau
ENEnglishSign inCreate an HPN →
For providers HPN Connect

Your patients arrive with their record.
You change nothing.

HPN Connect gives every one of your patients a lifetime Health Point Number — and gives them the whole PHB front door — while your existing EMR keeps running exactly as it does today.

Connect your system →See how it works
One numberPHB-XXXX-XXXX-XXXX
The problem

Records are trapped because there is no shared key.

Every hospital’s system numbers patients its own way. The same person is one id here and a different id there — so no record can follow them. The result is repeated tests, missed allergies, blind referrals, and care that starts from scratch on every visit.

PHB fixes the missing piece: one lifetime number per person that every system can agree on — the way one bank number works across every branch.

What it is

PHB sits beside your system — never on top of it.

Your EMR keeps running
You send a patient’s identifiers; you receive an HPN. No migration, no rip-and-replace. The promise is “the patient arrives with their record” — not “replace your software.”
The HPN is the join key
Each record carries your own local id and the PHB HPN, side by side. Nobody renumbers anything — both sides just agree on who the patient is.
PHB becomes the patient’s front door
Most EMRs are internal-only. The moment a patient has an HPN, they gain the whole PHB app/web/USSD — and you built none of it.
How it works

One call. A deterministic ladder.

For each patient you send, PHB walks a fixed, deterministic ladder — an exact match or a fresh number, never a fuzzy guess:

  1. crosswalkAlready linkedWe've seen this patient from you before — the same HPN comes back. Re-sending is a safe no-op.
  2. HPNYou already hold the HPNIf your record already carries a valid PHB HPN, we honour it and link your local id to it.
  3. NINMatched by NINThe same person at two hospitals resolves to one HPN. This is what makes PHB a network, not another silo.
  4. phoneMatched by phoneA single phone on a single record links cleanly. More than one — we never guess; it routes to a human to confirm.
  5. mintNo match → a new HPNA new provisional HPN is issued. Name + date of birth + sex is enough — NIN can follow later.

NIN is optional — a dedup hint, never required and never trusted as proof until the patient verifies it themselves. The exchange returns an HPN and a status; it never returns a patient’s clinical record.

POST /v1/connect/patients/resolveHPN Connect
// authenticate the partner system
X-Partner-Key: <partner_key>
 
// request — NIN & phone optional
{
  "partner_patient_id": "BP-00184523",
  "first_name": "Amaka",
  "last_name": "Okafor",
  "date_of_birth": "1996-03-12",
  "sex": "female"
}
 
// response — an HPN, never a clinical record
{
  "hpn": "PHB-4029-8156-7734",
  "status": "provisional",
  "match_rung": "minted"
}
For the hospital

You keep everything. You add a front door.

  • Keep your existing EMR. Nothing to migrate, nothing to replace.
  • Your patients gain a front door — the whole PHB app/web/USSD — even if your system has none.
  • One identity that follows the patient across every facility they visit.
  • Identity only: we return an HPN, never a patient’s clinical record. No PHI leaves your walls.
For the patient

One number that finally belongs to them.

  • One lifetime Health Point Number — the same at every hospital, lab and pharmacy.
  • Their records can follow them instead of starting from zero each visit.
  • The full PHB patient experience: records, consent, family, payments, transparency.
  • They confirm their own NIN and phone later — their identity, their control.
Trust & safety

Identity is safety-critical. We treat it that way.

Never a blind merge
Two people are only ever joined by a deterministic key (HPN or NIN), never by a fuzzy name-and-birthday guess. Anything ambiguous waits for a human. A wrong merge is a clinical-safety event — so the bias is always toward not merging.
A signed agreement comes first
Your hospital is the data controller. Issuing HPNs to your patients runs under an NDPR data-sharing agreement — and because this exchange carries only an identity, never clinical data, it is the simplest such agreement to sign.
Stored in Nigeria, fully audited
Patient data lands in the sovereign store in Nigeria. Every issue and match is written to an append-only, hash-chained audit log — surfaced to the patient when they activate their account.
Where we are

Honest about what’s ready.

The identity layer is live today. The deeper record exchange is what we co-build with our first pilot hospitals — which makes them the reference integration.

Live today
  • HPN identity issuance + the partner crosswalk
  • The deterministic matching ladder (single + bulk)
  • API-key partner authentication
Built with your pilot
  • Clinical record exchange (FHIR push/pull)
  • Continuous auto-sync from your EMR
  • The patient claim / activation bridge
Deferred
  • Self-serve developer portal
  • Public sandbox + SDK
  • Conformance certification

Be the first hospital we connect.

The first hospital on HPN Connect becomes the reference integration. A clinician who is also a builder is exactly who we want to build it with.

Connect your system →See FHIR integration