Kenya’s dual transition—DHA-certified clinical systems on one side, SHA purchasing on the other—converges in the Health Information Exchange. AfyaLink (and the related AfyaConnect developer portal) is where patient registries, shared health records, consent, terminology services, and FHIR claims meet. Facilities that treated integration as a post-go-live task learned expensive lessons in 2025 when clean clinical notes still produced rejected claims because facility IDs, intervention codes, or coverage objects did not match payer rules.
Implementation guides from DHA and practitioner write-ups such as the HMIS–HIE integration checklist published by AfyaStack reinforce the same message: the EMR must own the mapping layer between bedside documentation and national bundles. KenMD prepared this briefing for hospital IT directors, HMIS leads, and revenue cycle managers sequencing work after EMR selection and SHA contracting.
Why AfyaLink sits at the centre
AfyaLink exposes REST APIs secured with tokens obtained through DHA’s authentication flow. Behind those endpoints are the national client registry, facility registry (Master Facility List), practitioner registry, Shared Health Record, consent services, and payer-facing claim and pre-authorisation routes. DHA’s certification programme explicitly tests interoperability—a certified EMR is expected to demonstrate that it can exchange data in approved formats. Facility go-live, however, still requires production credentials, SHA acknowledgement, and validation that the deployment at a specific site matches registry data.
Think of AfyaLink as the switchboard: your certified EMR is the handset. Without both, calls do not connect.
Registry-first discipline
Official claim integration documentation lists pre-submission validation as step one—lookup patient CR IDs, facility FIDs, and practitioner PUIDs before building a bundle. That sounds administrative, but it is where many rejections originate.
- Patients: dynamic client search must resolve the same identifier the front desk captured. Typos or partial matches propagate into duplicate claims.
- Facilities: organisation resources must carry the FID SHA expects, aligned with e-contracting records and KEPH level.
- Practitioners: care teams reference licensed practitioners; locum or visiting staff without PUID mapping stall authorisations.
When press reports described facilities “locked out” of SHA, the underlying issue was often registry state, not clinical capacity. IT leads should schedule quarterly reconciliations between the Master Facility List, SHA contract data, and EMR configuration tables.
From charge capture to FHIR bundles
Claims ride on FHIR R4 transaction bundles submitted to endpoints such as POST /v1/shr-med/bundle with application/fhir+json. DHA’s claims guide reads like a revenue-cycle checklist translated into standards language:
- Map SHA intervention codes (e.g. SHA-08-004) to local service catalogs; flag pre-authorisation requirements in the UI.
- Load tariffs so clinicians see SHA-payable amounts and patient co-pay where applicable.
- Capture diagnoses with ICD-11 (terminology server prefixes differ by environment—UAT vs production).
- Build bundles with consistent
fullUrlreferences linking Patient, Organization, Coverage, Encounter, Condition, and Claim resources. - Submit, store claim IDs, and poll status endpoints or configure payer callbacks for adjudication updates.
Integration notes emphasise idempotency: resubmitting the same claim ID returns the original response—useful for debugging, dangerous if staff manually duplicate visits. PHC encounters may require zero-total claims when intervention codes designate primary care benefits; billing teams unfamiliar with that rule saw confusing rejections during early SHA rollout.
Sandbox to production: a realistic timeline
AfyaConnect’s onboarding path mirrors what large hospitals already run for other enterprise go-lives:
- Register the facility and obtain sandbox credentials.
- Map local codes to national terminology; exercise client registry and SHR reads/writes.
- Run end-to-end scenarios—outpatient visit, inpatient discharge, pre-auth surgery, chronic refill.
- Complete workflow validations with DHA or vendor partners; fix data quality issues surfaced in reports.
- Request production keys only after facility go-live approvals and SHA acknowledgement.
Budget six to twelve weeks for a mid-sized hospital if tariff mapping and ICD-11 search are net-new. Smaller clinics move faster when they limit initial scope to outpatient SHIF visits before adding theatre or renal bundles.
Organisational roles that make or break integration
Clinicians must document diagnoses and procedures that map to billable interventions—not shadow shorthand that finance cannot code. Nurses and front desk staff ensure identities and consents are correct before encounters open. Revenue cycle owns claim status dashboards and escalates payer denials with clinical context. IT monitors token expiry, callback TLS endpoints, and environment promotion. Leadership funds the overlap period when dual entry or manual claim files persist while automation matures.
Provider surveys during the SHA transition consistently flagged portal downtime and unpredictable adjudication. Technical integration does not eliminate those issues, but it reduces self-inflicted denials—the ones fixable by aligning codes, IDs, and bundles with published rules.
Working with a DHA-certified EMR such as KenMD
KenMD’s DHA certification (CERT-2026-NFLP7QYX) attests that the product met national conformance tests, including interoperability expectations. Each facility still completes AfyaLink onboarding, loads SHA tariffs for its contracted services, and validates production flows with its county or payer liaison.
Teams evaluating integration vendors should ask for: a registry validation module, ICD-11 search strategy (API vs cached index), pre-auth UX, claim status polling, and a documented path from sandbox to production aligned with DHA’s thirteen-step certification diagram. KenMD customers can engage our team via Get Started for joint planning with hospital IT.
Closing perspective
AfyaLink is the technical expression of Kenya’s policy bet: care financed by SHA should be documented once, exchanged securely, and reimbursed against shared rules. Facilities that invest upfront in registry hygiene, code mapping, and clinician training ride national transitions more smoothly than those that bolt billing onto paper charts after patients queue at the desk.
Get the Full Walkthrough
KenMD is DHA-certified for Kenya’s digital health framework. Request a demo or explore Learn KenMD for module-based billing training aligned with SHA workflows.
