For providers Integration
Your existing HIS keeps working.
PHB speaks FHIR.
HL7 FHIR R4 is the data standard. Your existing hospital information system connects via open-source adapters — no rip-and-replace required.
FHIR-native
Built on the global health data standard.
HL7 FHIR R4 is PHB’s data lingua franca. Every patient resource, clinical event and consent record is a FHIR-conformant bundle — exportable, portable and interoperable with any conformant system globally.
Clinical coding follows ICD-11, SNOMED CT, LOINC and RxNorm. Medication data aligns with the National Essential Medicines List.
HL7 FHIR R4ICD-11SNOMED CTLOINCRxNormNEML
Health Information Exchange
Your existing HIS keeps running. A FHIR adapter translates its native format into PHB-compatible bundles — no migration needed.
Exportable patient bundles
Any patient can export their full FHIR bundle at any time. Portable to any FHIR-conformant EHR worldwide.
Consent as a FHIR resource
Consent grants and revocations are modelled as FHIR Consent resources — part of the patient record, auditable and portable.
Versioned, idempotent writes
All write endpoints under /v1/ accept an Idempotency-Key. Safe to retry; guaranteed not to double-apply on network failure.
Open-source building blocks
We build in the open where we can.
phb-fhir-adapter
FHIR Adapter
Bidirectional translation layer between common Nigerian HIS formats and FHIR R4 bundles.
phb-ussd-kit
USSD Kit
Build USSD sessions with PHB's menu tree model. Tested against MTN, Airtel, Glo and 9mobile.
phb-telco-adapter
Telco & WhatsApp Adapter
Normalises telco session callbacks and WhatsApp webhook events into PHB channel events.
phb-hpn-lib
HPN Structure Library
Validate, parse and generate HPNs. Includes the Damm mod-10 check digit implementation.
phb-i18n
Multilingual Glossary
Clinical and UI terms in EN, Pidgin, Yoruba, Igbo and Hausa. Pull-request contributions welcome.
phb-consent-sdk
Consent SDK
Embed PHB consent flows in third-party apps. Handles offline consent codes and break-glass scenarios.
APIs & sandbox
Versioned REST APIs. Idempotent by design.
Every write endpoint accepts an idempotency key — safe to retry on network failure, guaranteed not to double-apply. All endpoints are versioned under /v1/.
- Versioned endpoints under /v1/ — no breaking changes without notice
- Idempotency keys on every write — safe to retry on network failure
- OAuth 2.0 with provider-scoped tokens
- Sandbox environment for testing without touching live patient data
- Webhook events for consent changes, appointment updates and billing
Build on PHB Connect.
Request sandbox access, browse the API reference or open a support ticket with the integrations team.