WHO-Grounded Triage Decision Support Tool Built in Base44WHO-Grounded Triage Decision Support Tool Built in Base44
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
I'm a medical doctor. The scariest decisions in medicine happen where there is no doctor.
When someone falls sick far from a hospital, a health worker (or the family) has to decide in seconds: is this an emergency, or can it wait? Guess wrong, and someone can die waiting.
For the Base44 Challenge I didn't want to ship a pretty landing page. I built the tool I wish those health workers had.
Meet TriageLine: WHO-grounded triage decision support, built entirely in Base44.
THE KEY IDEA Most AI health tools let the model make things up. TriageLine does not. The AI only NAMES the condition. A verified WHO protocol table then decides the severity, the exact dose, and the next step, with a page citation on every card. The AI cannot change a number on it. And if no protocol matches, it abstains: no citation, no plan, refer to a clinician.
HOW IT WORKS
Type the case in plain words, one free-text box: "child, 2 years, cough, fast breathing, too weak to feed."
The AI classifies it against the WHO list.
A verified WHO table (IMCI and mhGAP) returns the severity band, the exact dose, the next step, and the citation.
If it is an EMERGENCY, TriageLine automatically emails a doctor the full clinical summary to come in and escalate, and gives the patient an action-only summary.
Every case is recorded: a triage queue, an audit log, and analytics including time saved.
WHAT I BUILT
One-box intake plus AI classification across 30+ conditions
A verified WHO protocol table that binds every dose and citation, so no numbers are ever invented
EMERGENCY email escalation to a doctor, a real working automation
A patient-facing, action-only summary
A staff console: triage queue, audit log, analytics, role references
A safety abstain path when no WHO protocol matches
A dark, clinical design with a signature Pathway decision-spine that draws the one-way flow: the AI classifies, the table decides
THE PROCESS As a doctor, I went deep into the WHO triage protocols, the IMCI and mhGAP guidelines written for exactly these settings, and worked out how each case should map to a severity, a dose, and a next step. Then I designed the trust architecture (AI classifies, verified table decides) and built all of it in Base44: the data model, the roles and auth, the AI classification, the WHO protocol table, and the email escalation. Then I tested it live end to end, a real emergency case producing the cited card and a real delivered email to the doctor.
It is live. Try it: triage-line-flow.base44.app
#Base44Challenge @Base44
Kapil's avatar
I'd store the model's classification and the protocol-table version with each case, so the audit log can reproduce why that card appeared. When you update a WHO table, can you replay a fixed set of synthetic cases and review the output changes before the new version goes live?
Damilola's avatar
Great point, and yes to both. Right now every case is logged with the AI's classification and the exact WHO row plus page citation it resolved to, so the audit log can already show why a given card appeared. What you're describing next, stamping each case with the protocol-table...
Kapil's avatar
I'd include cases where a table update should change the result and cases where it should leave the result unchanged. Comparing the resolved row and citation alongside the classification should make unintended changes easier to spot.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started