DHS builds modular hospital and clinic platforms that cover reception, doctor, lab, pharmacy, telemedicine, billing, admin, and reporting on a single patient record. The library currently runs to over 30 reusable modules.
Today · St Mary's
Outpatient · Tuesday morning
Cases
47
Avg wait
18m
AI prep'd
12
The screens below illustrate how the DHS platform runs across a typical clinic day, with each module reading from and writing to the same shared patient record.
Patients today
47
+8 since yesterday
Queue
12
4 active now
Lab orders
9
3 pending
Avg. wait
18m
↓ 4 min
Today's queue
LIVETelemedicine
2 sessions active
Dr. Osei
video · 14 min
Nurse Ali
audio · 3 min
AI assist
A.M. · case prepared
Clinician reviews · decides
Outpatient clinic setup · 8 of 12 modules active
The consultation view brings the patient record together with an AI-drafted intake summary, the relevant labs from the last six months, the short history from the prior visit, and the original inbound message that started the case.
Welcome
Dr. K · Tuesday
In queue
12
Avg wait
18m
Active
5
Next: M.K. · 34
Routine · WhatsApp · AI summary ready
Modules in the platform
Compose what the setting needs. Skip what it doesn't.
Each module is real, in-use, and adapts to local workflow.
The platform ships as a library of over 30 modules, configured per deployment. A rural clinic might activate eight modules, a 220-bed hospital network might run twenty, and a maternal health programme might combine six standard modules with three custom ones built for the operation.
DHS module library
Every module we've built, available for every programme.
Patient access
Single inbox for channels
WhatsApp flows
Conversational intake
USSD menus
Works on any phone
SMS reminders
Confirmations · follow-ups
Voice intake
Phone-first triage
Callback workflow
Queued return calls
Intake structuring
Free text → fields
Triage assist
AI priority signals
Patient records
Longitudinal EMR
Records bridge
Into existing EMRs
Care team UI
Doctor · nurse · admin
Appointments
Booking · reminders
Telemedicine
Video · async consults
Lab integration
Orders · results
Pharmacy workflows
Prescriptions · stock
Reporting
Programme · ops · donor
Audit trail
Action and role logs
Mobile money
M-Pesa · MoMo · Airtel
Insurance claims
Public · private payers
Community health
CHW field workflows
Field intake
Offline-first forms
Connectivity sync
Resume when online
Multi-language
EN · SW · LG · FR · AR
Maternal health
Antenatal · postnatal
Every DHS programme is composed from this library. When something is missing for a setting, we build it and the library grows.
The four design choices below sit underneath every module in the platform. They shape how data flows, how the system behaves on weak networks, how AI is reviewed, and how every action is recorded.
Every module writes to the same patient record. Reception, doctor, lab, and pharmacy all read from the same data, so a phone number updated at the front desk is visible to every clinician through the same shift.
Every device running DHS keeps a local copy of the data it needs. Consultations continue when the network drops, and the device syncs cleanly with the cloud once the signal returns. Sites with weekly power outages run DHS reliably.
The platform exposes AI for intake structuring, summaries, triage signals, and routing. A clinician reviews every output before it touches the record. The full AI architecture sits on the AI-supported workflows page.
Every read, write, AI call, and access event is logged with user, role, time, and source. Audit reports run on demand for ministry inspections, donor reviews, and internal reviews from the same trail.
The AI side in detail: AI-supported healthcare workflows →
DHSAFRICATell us about the building. How many beds, how many outpatients, what currently runs the front desk, where the paper still lives. We come back with the module list we would propose and what the first ten weeks would look like.
About a minute · No commitment