How we work

A consistent approach across every DHS project.

Every DHS engagement follows the same shape: four principles, a six-step process, and a typical timeline of ten to twelve weeks from setting visit to first live case.

Four principles Six steps 10 to 12 weeks
Four principles

The principles that guide every DHS engagement.

These four principles apply across hospital deployments, NGO programmes, foundation builds, and partner integrations. They are based on experience with what makes healthcare software useful at the daily working level.

01

Design around the workflow

DHS starts each project by understanding how care moves at the site, where it stalls, and what staff currently work around. Features are built where they change a real workflow, and the platform configuration is shaped by that.

02

Design for everyday use

DHS designs for the realities of a busy clinic: fluorescent light, gloved hands, frequent interruptions, and reception staff working through a queue. Screens are kept simple, with the relevant information visible at a glance.

03

Keep clinicians in control

DHS AI structures intake, drafts summaries, and surfaces triage signals. A clinician approves each output before it touches a record, and every call is logged with input, model, time, and reviewer for audit.

04

Stay engaged after go-live

DHS staff are on the ground through the first week of live operation and remain on call for support afterwards. Each deployment has a named operations lead at the client side and a named engineer at DHS to coordinate the post-launch period.

The six steps

How a DHS project moves from setting visit to first live case.

The six steps below apply across hospital deployments, NGO programmes, and partner integrations. Depth and emphasis vary by setting, while the sequence of work stays consistent.

  1. 01 Step 01

    Setting visit

    Two DHS staff spend five to ten days on site, observing reception, following a case through the clinic, and meeting the people who run the workflow today. This time produces the basis for everything that follows.

    Reception
    Consult
    Lab
    Pharmacy
  2. 02 Step 02

    Workflow mapping

    Before any software is built, DHS maps how patients move through the operation today. The map covers entry points, handoffs, where information drops, and where it gets re-entered. The clinical lead signs off on the map, which then becomes the specification.

    Patient
    Channel
    Intake
    Routing
    Care
  3. 03 Step 03

    Channel selection

    DHS selects inbound channels based on what patients use at the site. Feature-phone communities typically rely on USSD, smartphone populations on WhatsApp, and the clinic desk is included in most deployments.

    WhatsApp live
    USSD live
    SMS live
    Phone live
    Clinic desk live
  4. 04 Step 04

    Build for daily use

    DHS iterates the first build until reception can complete a case in under thirty seconds and a clinician can read the brief in five. Screens are kept simple, with only the fields and actions that staff need for the workflow.

    Today's queue LIVE
    • M.K. WhatsApp
      Mild fever · 2 days Live
    • A.O. USSD
      Lab follow-up Scheduled
  5. 05 Step 05

    AI where it helps

    AI is added where it reduces repetitive structuring work for staff: intake, triage signals, case summaries, and routing. Outputs route through a clinician for review, and every call is logged for audit.

    AI prepared 3 notes
    • Likely respiratory · routine
    • Consider CBC if symptoms persist
    • Follow-up · WhatsApp 24h
    Clinicians review · provider decides
  6. 06 Step 06

    Go-live on site

    Two DHS staff are in the building for the first three days of live operation, sitting with reception, clinicians, and the lab to address issues as they come up. Handover to a named operations lead happens at the end of the first week.

    Rollout · 4 weeks On track
    Deploy
    Deploy
    W3 Training
    W4 Iterate
Before and after

A composite view of operations before and after a DHS deployment.

The illustration below combines patterns seen across several DHS projects rather than a single case study. Specific numbers vary by site, while the overall shift towards a shared queue and a unified patient record is typical.

Before a busy Monday morning

Appointments · Tue

p. 47
  • 10:00M. K.
  • 10:30A. Otieno
  • 11:00?? walk-in?
  • 11:30S. W. (no show)
  • 12:00Mr K !! URGENT
  • 12:30P. Wanjiku

Mr. K

call back!! 11am

Lab result??

where is it

3 missed callsReception line
WhatsApp?USSD?SMS?
  • Inbound calls overwhelm a single phone line, with patients dialling repeatedly to reach the front desk.
  • Case notes are spread across paper files in reception, the doctor's office, and the lab, with frequent inconsistencies between them.
  • The care team works from memory, WhatsApp screenshots, and printed lists, with limited shared visibility on case status.
  • Past AI initiatives remain stuck at proposal stage and have yet to make it into daily operations.
After the same operation, eight weeks later
DHS care system
LIVE
One queue · all channels12 active
  • M.K.WhatsApp
    Mild fever · 2 daysDr. KLive
  • A.O.USSD
    Lab follow-up · CBCNurse AScheduled
  • S.W.Phone
    Prescription refillReceptionDone
  • P.W.SMS
    Antenatal reminderCHW · MPending
AI prepared 8 cases · all reviewed by clinicians
  • Inbound channels including WhatsApp, USSD, SMS, phone, and walk-ins all feed into a single case queue with a unique ID per case.
  • A shared patient record is visible to reception, the doctor, the lab, and the pharmacy, with role-based access to the relevant fields.
  • Clinicians open each case with a short AI-drafted summary, the original inbound message, and the relevant patient history loaded.
  • Every AI-assisted action is recorded with input, model, output, reviewer, and timestamp for audit and review.
What the first ten weeks look like

The four phases of a typical DHS engagement.

DHS has run this shape across hospital deployments, NGO programmes, foundation field rollouts, and integrations with existing EMR systems. Total duration varies with scope, with smaller projects compressing the first phases and larger ones extending the rollout phase.

  1. Weeks 1 to 2

    01

    Setting visit

    DHS staff visit the site, observe the existing workflow, map the constraints with the clinical lead, and draft the project specification.

  2. Weeks 3 to 6

    02

    Prototype

    DHS builds the first working version, used in one controlled flow at one location with feedback from the staff who will use it daily.

  3. Weeks 7 to 10

    03

    Deploy and train

    DHS handles a staged rollout across reception, doctor, lab, and pharmacy with around two days of hands-on training per role, and stays on site through go-live week.

  4. Ongoing

    04

    Support and iterate

    A named operations lead at the client and a named DHS engineer coordinate weekly check-ins for the first quarter, with iterative updates planned into the engagement.

DHSAFRICA
Start a project

Tell us what you want to build.

DHS works with hospitals, clinics, NGOs, foundations, and international partners. The guided check below takes about a minute and gives us enough context to write back the same working day.

About a minute · No commitment