Hospital management software for Kenyan clinics and hospitals.

Patient records that scale from a one-room clinic to a multi-department hospital

The system we build starts at registration and follows the patient all the way through. A front-desk clerk registers a new patient once — national ID, insurance details, next of kin, contact — and that record becomes the single source of truth for every subsequent encounter. Outpatient and inpatient workflows are handled separately but linked: an OPD consultation that escalates to admission does not require re-entering the patient's history on a new form. Clinical notes, diagnosis codes, investigation requests, and discharge summaries are all attached to the same longitudinal record. For facilities that grow, the architecture grows with them. A single-branch clinic and a hospital with three outpatient departments, a maternity wing, and a surgical ward run the same underlying system — we configure the module set and department structure to match your layout. Ward rounds, bed assignments, and inpatient nursing notes fit into the same interface that a small clinic uses for daily OPD. No rip-and-replace when you expand; the schema is designed for it from day one.

• Single patient registration record used across all departments and visits
• Separate OPD and IPD workflows with linked clinical history
• Diagnosis recorded against ICD codes for claims and reporting
• Triage scoring and consultation queue management for busy outpatient settings

Pharmacy, lab, and inventory connected to the patient record — not running in isolation

The gap between the consultation room, the pharmacy, and the laboratory is where most of the waste in a Kenyan facility lives. A doctor prescribes; the patient carries a handwritten slip to the pharmacy; the pharmacist types it into a separate stock book; the lab result comes back on a printed slip that may or may not be filed in the correct folder. The system we build eliminates every one of those manual handoffs. When a clinician writes a prescription, it appears on the pharmacist's dispensing queue immediately — no slip, no re-entry. When a lab investigation is requested, the lab technician sees it on their worklist and posts results directly against the encounter; the clinician sees them in the same interface the moment they are verified. Inventory is tracked at the line level: every dispensing event decrements the pharmacy stock ledger, reorder thresholds trigger alerts before you run out, and the purchasing record ties back to a supplier invoice. The same stock discipline applies to surgical consumables, reagents, and ward supplies — any category you want to track.

Billing that fits Kenya — NHIF/SHA claims, M-Pesa patient payments, KRA eTIMS invoicing

Billing is where Kenyan health IT has consistently failed facilities. Generic systems generate invoices but leave the NHIF or SHA claim as a manual step. eTIMS compliance gets bolted on as an afterthought. M-Pesa is a separate device on the counter. We design the billing module around Kenyan reality from the start. Every billable event — consultation fee, dispensed drug, lab test, bed-day, procedure — is captured at the point of service and flows into the billing engine automatically. For NHIF- or SHA-covered patients, the system maps services against the applicable scheme tariff and generates a pre-validated claim batch ready for submission, reducing the back-and-forth with the insurer that costs facilities cash-flow weeks. For cash-paying patients, M-Pesa STK push is integrated directly via the Daraja API: the billing clerk initiates the request from the system, the patient confirms on their phone, and the payment is confirmed and receipted in under a minute — no handling cash, no separate POS reconciliation. Every invoice is posted to the KRA eTIMS API at the point of generation, keeping the facility continuously compliant rather than scrambling at audit time.

• Automatic NHIF/SHA tariff mapping and claim batch generation
• M-Pesa STK push via Safaricom Daraja — confirmed and receipted in the same interface
• KRA eTIMS invoice posting at the point of billing, not retrospectively
• Split billing for partial insurance cover — scheme portion and patient co-pay tracked separately

Built to spec, white-label, role-based — yours on delivery, not rented forever

Every facility operates differently. The module configuration, department structure, tariff schedule, report formats, and even the terminology on the interface (some facilities say "patient file", some say "case sheet") all vary. We do not ship a generic product and ask you to adapt your workflow to it. We scope the build with you, agree the feature set in writing, and build to that spec in fixed-price phases — you know the cost of each phase before we write a line of code. Role-based access control is built in from the ground up, not added as a permission setting after the fact. Doctors see clinical notes and investigation results. Pharmacy staff see prescription queues and stock, not financial reports. Billing staff see the accounts module, not clinical records. Administrators see everything their role is configured to see. Audit logs record who accessed or changed every record, with timestamps — a requirement for any health system that takes patient data seriously and a necessity for facilities preparing for regulatory inspection. On delivery, we transfer full IP to you: source code, database schema, API documentation, and a deployment runbook. If you want us to host, maintain, and continue developing the system, that is an optional retainer — from $3,500 per month — not a condition of owning the software. You are not renting access to your own patient data.