Choosing a Hospital Management System in Kenya (2026)
Buyer’s Guide · 8 min read · Updated 2026-06-26
There is no shortage of hospital management systems on the market, but most were built for somewhere else. A system that cannot handle SHA claims, M-Pesa, PPB compliance, and unreliable connectivity will cost you more in workarounds than it saves. This guide covers what actually matters when choosing an HMS in Kenya in 2026.
Start with the Kenya-specific must-haves
Generic global systems fall down on the things that are non-negotiable here. Before anything else, confirm the system handles:
- SHA / SHIF claims natively eligibility checks, coded claims, and reimbursement tracking, not a bolt-on.
- M-Pesa billing STK push with automatic confirmation, ideally split cash + mobile payments.
- PPB compliance a controlled substances register if you run a pharmacy.
- KRA eTIMS compliant tax invoicing.
- Offline capability the system has to keep working when the internet drops.
If a vendor cannot demonstrate these working, the rest of the feature list does not matter.
The core modules to evaluate
A complete HMS should cover the full patient journey:
- Patient registration and electronic health records
- Appointments and scheduling
- Triage and the emergency department
- Laboratory orders and results
- Pharmacy and inventory
- Billing, claims, and payments
- Reporting and analytics
Be wary of buying five separate systems that don't talk to each other. The value of an HMS is that the encounter, the prescription, the lab order, and the bill are one connected record.
Questions to ask every vendor
- Is SHA/SHIF claims support built in, and can you show it working today?
- How does M-Pesa STK push reconciliation work end to end?
- Do you have a PPB-compliant controlled substances register?
- What happens when our internet goes down mid-shift?
- How is our data isolated from other facilities on your platform?
- What does onboarding and staff training look like?
- How is the system priced as we add branches or users? See typical HMS pricing in Kenya as a benchmark.
Red flags to avoid
- "We can customise it for Kenya" meaning it isn't, yet.
- No clear data isolation story for a multi-facility platform.
- Per-seat pricing that punishes you for growing.
- A demo that only ever shows the happy path.
- No offline mode in a country where outages are routine.
On-premise vs cloud
Cloud (SaaS) systems remove the burden of servers, backups, and updates, and they make multi-branch reporting straightforward, provided the vendor has solid data isolation and an offline mode for connectivity gaps. On-premise gives you physical control but makes you responsible for uptime, security, and disaster recovery. For most Kenyan facilities, a cloud system with offline support is the pragmatic choice.
Where AfyaConnect fits
AfyaConnect was built specifically for Kenya and East Africa. SHA/NHIF/SHIF claims, M-Pesa STK push billing, the PPB controlled substances register, and KRA eTIMS are native, not customisations. It runs as an installable PWA that keeps working offline and syncs when connectivity returns, and every facility's data is isolated with row-level security. It covers the full journey from registration to claims in one connected record, and over 40 facilities across the region already run on it.
The best way to judge an HMS is to use it. Explore the full feature set, then register your hospital or your pharmacy to try it with your own workflow. Still running on paper or Excel? Read what actually changes when you switch.