Hospital Management Systems in Kenya: Cost, Features and Compliance

What drives the cost

Two hospitals can be quoted wildly different prices for what sounds like the same system. The difference is almost always in these factors, so price them explicitly rather than comparing headline numbers.

• Scope of modules: outpatient only, or inpatient, theatre, maternity and multiple departments.
• Number of sites and users, and whether pricing is per user, per facility or per patient visit.
• Integrations: insurers and SHA, laboratory analysers, M-Pesa, accounting and SMS.
• Data migration from paper records or a previous system.
• Hosting, support, training and the on-site presence needed during go-live.
• Security testing and compliance work required before the system can hold patient records.

The modules that decide the return

Registration and billing come first, because every other module feeds a charge into the patient's bill. The single most common revenue leak in facilities we see is services rendered but never billed: a lab test ordered on paper, a drug dispensed without a charge. An HMS closes that gap only if clinical orders and dispensing create charges automatically.

Pharmacy and stores come next: batch and expiry tracking, reorder levels, and dispensing tied to prescriptions. Then claims. Insurer and SHA claims are rejected for missing pre-authorisations, codes and signatures, and a system that captures those at the point of care rather than at month end recovers real money.

Claims, SHA and insurers

Claims integration is where HMS projects most often disappoint. Each insurer has its own requirements, and the public health insurance scheme has its own processes and systems that facilities must work with. Ask vendors precisely which payers they support, whether claims are submitted electronically or printed and re-entered, and how rejected claims are tracked back to the cause.

Expect this area to change. A vendor who can show how they absorbed the last change in scheme requirements is a safer bet than one with the longest feature list.

Patient data and security testing

Health data is sensitive personal data under the Kenya Data Protection Act, which carries stricter conditions on processing and on who may access it. A facility is the data controller and remains accountable when a vendor hosts the system. You need role-based access (a receptionist should not read clinical notes), audit logs of who viewed which record, encrypted backups, and a data processing agreement with the vendor.

Health systems are also increasingly expected to show evidence of security testing. Digital health solutions seeking certification with the Digital Health Agency have to present penetration testing and vulnerability assessment reports, so build security testing into the project plan rather than bolting it on before an audit.

Implementation realities

Plan go-live around your quietest period, keep experienced support staff on site for the first weeks, and run billing in parallel until daily takings reconcile. Clinicians adopt a system when it saves them time at the point of care, so involve a doctor and a nurse in choosing the clinical screens, not only the administrator.

Ask what happens during an internet outage. A hospital cannot stop registering patients because a fibre line is down, so the system needs a credible offline or local fallback.

Key takeaways

• HMS cost is driven by modules, sites, integrations, migration and support, so price each explicitly.
• The fastest return is revenue: automatic charges from orders and dispensing, and fewer rejected claims.
• Claims integration with insurers and SHA is where projects most often disappoint; test it specifically.
• Health data is sensitive personal data: role-based access, audit logs and a processing agreement are essential.
• Plan security testing into the project, especially if you will seek DHA certification.

Frequently asked questions