chew-copilot / 2025
2025 · AI · Experiments
CHEW Copilot
Triage guidance that speaks the clinic's languages.
Overview
A multilingual triage assistant designed for Nigerian community health extension workers — structured guidance across language and context barriers, built for low-friction, high-stakes frontline use.
- Role
- AI product · multilingual UX
- Year
- 2025
- Stack
- LLMs · multilingual UX · healthcare · triage
- Source
- GitHub ↗
CHEW Copilot — hero visual
image slot — asset coming later
Guidance for the thinnest tooling environment
Community health extension workers operate where the stakes are highest and the tooling is thinnest: brief consultations, mixed-literacy settings, and patients who may not share a language with the protocol documents. A generic chatbot demo fails here on three fronts at once — it assumes stable connectivity and long attention, it speaks one language confidently, and it optimizes for conversation rather than for a correct next action.
Guided steps, not open chat
Open-ended chat invites rambling precisely when a health worker has minutes. The assistant drives toward a structured outcome — symptoms in, triage guidance out — with each turn narrowing toward a decision instead of extending a conversation.
Story visual — Guided steps, not open chat
image slot — asset coming later
Five languages as a primary path
Detail view — Five languages as a primary path
image slot — asset coming later
Nigerian frontline care crosses English, Yoruba, Igbo, Hausa, and Pidgin within a single clinic day. Language support is designed as a primary path with consistent clinical meaning across switches, and every response ends in an actionable recommendation — refer, monitor, or reassure — with reasoning visible enough to trust and short enough to read between patients.
Structure
- 01
Symptoms in
- 02
Guided steps
- 03
Triage guidance
- 04
Refer / monitor / reassure
The result
The result is a focused concept for operational AI in public health rather than a generic chatbot demo — a working sketch of how language models can serve frontline workflows when the interface respects time pressure, language reality, and the need for auditable guidance.
- multilingual support
- frontline workflow
- health context
If I built it again
The interface constraint taught more than the model did: advise, never decide, and show your working in seconds. Next would be offline-first behavior and field testing with real workers to see which escalation cues actually get followed.
Further reading + source