SalusMedix is clinic and pharmacy software for Kenyan health facilities. One record covers the consultation, the dispensing, the M-Pesa payment and the eTIMS invoice, so nothing has to be reconciled later. It starts from KES 2,500 a month per branch, and annual billing gives two months free. Try the live demo first.
The demo runs on invented data with integrations simulated. Nothing in it is real. Full product at salusmedix.co.ke.

Every one of these is a gap between two systems that were supposed to agree.
The clinician wrote the prescription in a book. The dispensary keyed it into the POS. By month end the two disagree about what was given, and nobody can say which is right.
They were behind newer stock that arrived later and got dispensed first. Nobody was counting expiry dates, only quantities.
Somewhere between the till, three phones and a paper receipt book, a payment went in twice or not at all. Finding it takes an afternoon.
A coding error made at the consultation, discovered six weeks later by someone who was not there. The visit has to be reconstructed from memory.
You opened another location and it invented its own way of doing things. Comparing the two means exporting from both and hoping the columns line up.
Same patient, three months later, different clinician. The last visit is in a file somewhere, so the history gets taken again from scratch.
Appointments, consultation notes, ICD-11 coding, lab and imaging requests, maternity and MCH. The record follows the patient across branches rather than sitting in one building.
Stock is issued in expiry order automatically, so the boxes at the back cannot quietly go out of date behind newer deliveries.
Payment is taken against the visit, and the tax invoice is issued from the same transaction. The day's takings and the M-Pesa statement are the same list.
Not re-typed from it. The diagnosis, the coding and the items dispensed are already there when the claim is assembled, which is where most rejections come from.
A clinic with a dispensary, a standalone chemist and a larger medical centre can run side by side, each the way it actually works, with a group view across all of them.
Append-only, with multi-factor sign-in and data isolation between facilities. Built for the questions an inspection asks, not the ones a demo asks.
Read this before you buy, not after.
The claim pipeline, the FHIR bundle and the submission outbox are built and testable today. Live submission to SHA is gated on DHA HMIS certification, which is a vendor onboarding process rather than a coding task. If you need SHA billing switched on from day one, talk to us before you buy.
M-Pesa, eTIMS and SMS run on live credentials. Everything else in the clinical, pharmacy, billing and inpatient surface is working. We would rather you knew which half is gated than discovered it in month two.
Adding a clinician, a locum or a intern does not change the bill, and we take no share of what you dispense.
A clinic or chemist getting one record in place.
The full clinical, pharmacy and billing surface.
Pay annually and two months are free.
No revenue share, and no per-user fee.
No. SalusMedix is deliberately not a rip-and-replace. Most facilities start with the dispensary and the front desk, because that is where the disagreement between records actually costs money, and add consultation notes, lab, and inpatient later. Your existing patient list comes across at the start either way.
Yes. demo.salusmedix.co.ke runs a full working system loaded with invented data: a fictional three-branch group, so one login shows a clinic with a dispensary, a standalone chemist and a larger medical centre, plus the view across all three. Nothing in it is real and the integrations are simulated.
From KES 2,500 per branch per month, with a standard tier at KES 4,900 per branch per month. Annual billing includes two months free. It is a flat subscription, with no revenue share on what you dispense, and no per-user fee, so adding a clinician or a locum does not change the bill.
On infrastructure we operate, with data isolation between facilities enforced in the database rather than in application code. For facilities that require Kenyan data residency, there is a documented path to a Kenya-resident deployment. Ask us and we will show you the data-protection assessment rather than describing it.
This is the honest answer: offline operation is designed and partially built, not finished. If your facility loses connectivity regularly enough that dispensing must continue through it, tell us during the demo so we can be specific about what works today and what does not.
A fictional three-branch group, loaded and running. Fifteen minutes will tell you more than a call.