Skip to main content

KenMD

Transitioning to DHA-Certified EMRs: What Kenyan Facilities Are Learning

When Cabinet Secretary for Health Aden Duale told providers that all public health facilities would be fully digitalised by 1 October 2025, the deadline sounded absolute. Reporting from The Eastleigh Voice captured the ambition: paper registers replaced by HMIS, SHA systems linked, and patient records accessible through national platforms such as AfyaYangu. The policy direction was clear—healthcare in Kenya would run on certified digital rails.

A year on, the story is more textured. Migration has moved fast in parts of the public sector while faith-based and private facilities catch up. The Ministry extended some transition windows—including HMIS migration timelines reported into late 2026—so counties and hospital boards could finalise vendor contracts, train staff, and align with the Social Health Authority (SHA) without abruptly cutting off patients. That pause is not a retreat from digitisation; it reflects how heavy a lift it is to change clinical, billing, and reporting habits at thousands of sites simultaneously.

What the law now requires

The Digital Health (Health Information Management Procedures) Regulations, 2025 (Legal Notice 76 of 2025) put certification in plain terms. Under Regulation 37, a healthcare provider or facility shall not use a digital health solution in the provision of healthcare services unless that solution has been certified by the Digital Health Agency (DHA). Controllers and processors also cannot access the Comprehensive Integrated Health Information System without using certified software and meeting security requirements in the Certification Framework.

That language shifts procurement conversations. Instead of asking whether an EMR “has modules,” boards should ask whether it appears on the public registry with a valid certificate ID, who the health data controller is, and when certification expires. DHA publishes certificates with start and end dates; full certification typically runs two years under the current framework, so governance committees need renewal triggers the way they track drug licences or fire certificates.

Certification is not the same as go-live

One of the most useful public explanations DHA has published is the end-to-end certification journey on certification.dha.go.ke. The certificate is step eleven in a thirteen-step path—not the finish line. After laboratory testing and national validation against the health exchange and SHA rules, DHA issues the certificate and lists it on the register. Putting that system in front of patients at a specific facility still requires facility go-live approval, SHA acknowledgement, and production credentials.

Facility leaders we speak with sometimes discover this only when finance expects live claims but IT is still on a vendor sandbox. The lesson: budget for two programmes—product certification (vendor-led) and facility activation (facility-led with county or hospital IT).

How far migration has reached

Press reporting in 2026 cited strong uptake among public Level 2–4 facilities—with ministry figures suggesting full completion in that tier—while faith-based and private providers lagged. That pattern matches what implementation teams see on the ground: county hospitals received central support; mission hospitals and standalone clinics had to self-fund licences, connectivity, and vendor support.

DHA’s facility-facing register (the public view at certification.dha.go.ke/facilities) ties together KEPH level, ownership type, SHA activation status, and the certified system a site is meant to run. Medical directors can compare their row with what staff actually log into each morning. Mismatches—a “SHA active” flag but no trained billing clerk, or a certified product name that differs from the deployed build—are early warnings before auditors or claims rejections surface the gap.

What DHA tests before it certifies

Applications arrive on Form HMIS 4 with a stack of evidence: self-attestation, incorporation, ODPC registration, a Data Protection Impact Assessment, security and backup policies, cybersecurity assessment, and more. DHA then scores the product against functionality, reporting, security, and interoperability. For facility demo committees, those buckets translate into concrete questions:

  • Can clinicians document a full outpatient visit without workarounds that break reporting?
  • Does the system emit the alerts and aggregates MOH expects?
  • Are roles, consent, and audit logs demonstrable?
  • Has the vendor shown exchange with AfyaLink registries in test environments?

Reporting from civil society and media during the SHA transition also highlighted a different risk: facilities can be digitally locked out of payer systems when registry metadata, KEPH level, or licences do not align—even if clinicians continue seeing patients physically. Digitisation therefore binds clinical software to master facility data maintained nationally. Your EMR choice and your facility registry record must stay in sync.

A practical verification playbook

  1. Search the certification registry for the exact product and version your vendor proposes.
  2. Download or archive the certificate PDF; note expiry and assign an owner for renewal.
  3. Cross-check your facility row on the public facilities register—KEPH level, certified system name, SHA status.
  4. Request the vendor’s latest self-attestation and ODPC documentation for your data controller file.
  5. Schedule a joint session with IT and revenue cycle to map go-live prerequisites (production credentials, SHA acknowledgement).
  6. Plan training waves: clinicians first, then billing clerks once tariffs and intervention codes are loaded.

Where KenMD fits in the transition

KenMD (MNOCK LIMITED) is listed with DHA certificate CERT-2026-NFLP7QYX (issued 5 November 2026; expires 4 November 2028). Certification confirms conformance with the Kenya Digital Health Certification Framework; DHA does not endorse individual products. Facilities should verify the listing independently and then run local workflow pilots—maternity, chronic disease, minor procedures—that mirror the services they will bill through SHA.

Teams that treat DHA certification as the start of a transition programme, not a checkbox, tend to fare better when national deadlines tighten again. The regulatory direction is settled; the operational work is facility by facility.

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.

Sources and further reading