M-Pesa and SHA are underway.
Everything else plugs in.
Tabibu is being built for the payment rail and the national insurer a Kenyan hospital actually uses. Each integration below is listed with its real status — we only list what's committed on the roadmap.
Payments
M-Pesa
STK Push from the cashier desk. The patient confirms on their phone, the receipt posts back to the invoice, and the till balances against the ledger at close — no spreadsheet reconciliation.
- STK Push at any till
- Auto-reconciled receipts
- Refunds tracked against the original invoice
Insurance
SHA
Claims compile from the clinical record — the right codes attached automatically — and submit electronically to Kenya's Social Health Authority. Rejections return with a reason you can act on.
- Claims generated from the chart, not re-typed
- Electronic submission and status tracking
- Rejection reasons routed back to billing
Every integration, honestly staged
Statuses reflect the current product roadmap, not marketing copy. If your facility depends on something that isn't listed, tell us in a demo request — roadmap priority follows facility needs.
Nothing on this list has to be exhaustive
The extension architecture is designed exactly for this: once the SDK ships, something a facility needs that isn't on this page is a manifest and a Go binary away — not a fork of the core, and not a wait for our roadmap.
manifest.toml (design draft)
[extension] name = "lab-connect" category = "lab" [extension.events] subscribe = ["lab.order_created"] [extension.ui] has_ui = true
A new country won't need a new hospital system
The clinical record — registration, triage, wards, pharmacy, offline sync — is the same everywhere. What changes at the border is which payment and insurance extensions are installed. That's the whole point of building it this way.
Talk to us about your market