Enrollment Channels
Viewing as
Enrollment
How PHC workers get into the registry
Three channels meet workers wherever they are: a WhatsApp bot for smartphone-equipped LGA coordinators, a USSD shortcode for any feature phone, and a low-bandwidth web form (Sprint 2) for desktop browsers. All three write to the same FHIR R5 registry.
WhatsApp
Smartphone enrollment — chat with Claude Haiku
The bot walks the worker (or their coordinator) through enrollment in conversation — name, cadre, LGA, ward, PHC, council number, optional NIN. Pidgin and Hausa supported. Submits a Practitioner + PractitionerRole to HAPI live.
Number
+234 XXX XXX XXXX
Set
NEXT_PUBLIC_WHATSAPP_NUMBER in .env.localScan to chat
USSD — SPINE
Any feature phone — no smartphone, no data plan
Dial the shortcode on any phone. English, Hausa, Pidgin menus. Worker can check own status, view posting, update contact phone. Covers the ~50% of PHC workers without a smartphone.
Shortcode
*384*77463#
77463 = SPINE on the keypad
Scan for AT simulator
Web form
Low-bandwidth self-service for desktop browsers
Sprint 2 — a lightweight, low-bandwidth web form for workers with desktop or shared office access. NDPA-compliant self-service: a worker updates her own contact, posting, and views her credential, without needing to call the LGA office. Mirrors the USSD menu in a browser.
Wireframe only today. Architecture preserved — the same FHIR write API the WhatsApp + USSD bots use will back this form. Sprint 2 ships the UI on top.
Wireframe coming Sprint 2
Recent enrollments — live from HAPI
Loading…
Channel source-tagging (which bot/form each enrollment came through) ships in Sprint 1 alongside the audit log integration. Today we show every recent Practitioner without the source attribution — honest about the gap.