How it works

Reasoning a clinician can read, on a phone that needs no signal.

TPAS asks the questions your protocol asks, weighs what the health worker observes, and recommends only what the evidence supports. When it is unsure, it refers.

The reasoning

How sure it lets itself be depends on how far the examination has gone.

A score can be high and still not count. Until the health worker has examined the child, answered the safety checks and taken the decisive measurement, TPAS holds its confidence down.

  1. 25%Complaint onlyWhat the caregiver says brings in the protocol. It proves nothing on its own.
  2. 50%ExaminationThe health worker has looked, listened and recorded what they saw.
  3. 80%Safety checks answeredEvery danger sign in the protocol has an answer.
  4. 100%Decisive measurementA timed breath count, a rapid test or a vital sign, as the protocol requires.
The caps shown are those of the demonstration pneumonia protocol. Each protocol sets its own, signed with the rest.
  1. Only what is observed counts

    Every answer records where it came from: the health worker's observation, a vital sign, a rapid test, or only the complaint. A complaint scores nothing until someone has checked it.

  2. Two signals before treatment

    A diagnosis must pass its threshold and be confirmed by its decisive measurement. A high score without the measurement keeps asking.

  3. A danger sign refers, whatever the score

    A danger finding ends the questions, raises the severe diagnosis and fires the referral. Home treatment is not offered, and a pre-referral dose is given where the protocol says so.

  4. Every number traces to a person

    Weights, thresholds and dose bands are set by the clinician who wrote the protocol. The evidence behind each score is kept with the visit.

More than one illness at a time

A child with fever and cough is assessed for malaria and pneumonia together. Shared questions are asked once, and one plan is checked for drug interactions.

Mistakes can be undone

A corrected answer replaces the old one and keeps a link to it. Answers that depended on it are asked again, and the referral fires or clears.

Nothing skipped in silence

A health worker can skip a question they cannot ask, and must say why. The reason stays with the visit for the supervisor to read.

In the field

Made for a village visit, not a desk.

Works without a signal

Once a visit is open, questions, scoring, vitals, rapid tests, medicines given, referrals and escalations are recorded on the phone. Each kind waits in its own queue and is sent in order when the phone reconnects. Unsent work is never cleared.

Clinical tools in the flow

A 60-second breath-count timer, age-aware ranges for eight vital signs with critical flags, and the dose for this child's weight, with a warning when no weight was taken.

Readable in bright sun

A high-contrast mode one tap from the home screen. Screen-reader labels throughout, with urgent results announced as they appear.

A referral that travels

The handoff note follows the protocol's template and can be printed or shared from the phone. Leaving a visit without referring asks why, and the supervisor sees the answer.

Counseling in plain words

Each treatment comes with the protocol's own counseling, written for the caregiver: how to give the medicine, when to come back, and what should bring them back sooner.

A follow-up that is not forgotten

Escalations carry a deadline. When it passes without an outcome, the supervisor is alerted. The outcome is recorded when it comes.

One engine

The same answer in a village with no signal as in a clinic in town.

The decision engine is one program, built once and run in two places: on the health worker's phone and on the server. The signed protocol is the only input that changes what it does.

  • The same clinical cases are checked on the phone and on the server, to prove they agree.
  • The phone carries the active protocols, so a visit never waits for the network.
  • A supervisor can review any visit answer by answer, and every diagnosis says how it was made.
Signed protocol two signatures, one version Engine on the phone works offline Engine on the server supervision and review The same result same answers, same advice

Clinical content

Starting with the illnesses that kill children.

The demonstration protocols follow WHO's Integrated Management of Childhood Illness and community case management guidance, as adopted in Liberia's community health assistant algorithm.

  • General danger signs

    Asked first for every child under five. Any one sign refers, whatever else is wrong.

  • Pneumonia

    Cough or difficult breathing, 2 to 59 months. Timed breath count, chest indrawing, amoxicillin by weight.

  • Diarrhea and dehydration

    2 to 59 months. Dehydration classified, dysentery recognized, ORS and zinc.

  • Malaria

    Uncomplicated and severe. Treated only after a positive rapid test. Severe signs refer with pre-referral treatment.

Next in line: 26 diagnoses are already defined, including hypertension, diabetes, asthma, COPD and pre-eclampsia, and 32 WHO reference protocols sit in the library as drafts for a medical director to complete.

How we test it

Every protocol is walked on a phone before it goes live.

4protocols walked on a handset, case by case, against their expected outcomes before activation
85questions, each citing the guideline section it comes from
2places the same reasoning runs, the phone and the server, checked against the same clinical cases to prove they agree

Each serious defect found on a handset is fixed at its cause and given a lasting guard: a server rule that refuses the unsafe state, or a test that fails if it ever returns. We also attack our own approval rules on purpose, trying to get around signatures, roles and the order of steps.

Walk on a handsetFind the defect Fix the causeAdd a lasting guard against expected outcomesroot cause written up fixed and redeployeda server rule or a test

Request a demonstration

See TPAS reason through a visit.

In one hour, with demonstration data:

  • A visit on a phone, both paths: treat at home and refer
  • The protocol behind it, its sources and its signatures
  • The supervision dashboards and the period report
  • Your program's protocols, and what deployment would take

info@diggysolutions.com · +231 775 711 477
We reply within one business day. Oldest Congo Town, Monrovia, Liberia.