Problem
Patients at Rwandan health facilities wait three to four hours to be seen. They travel without knowing whether the facility accepts their insurance (Mutuelle, RAMA/RSSB, MMI), what they will pay, or how long the queue is — and facilities still run visits on paper registers.
Solution
A two-sided platform. Facilities onboard their staff and run reception, walk-ins, the live queue with triage and lab loop, consultation records, prescriptions, dispensing, billing and disputes. Patients see that data as insurance acceptance, bookable slots and their live place in the queue, on the web PWA or the Android app.
My Role
Co-built with Innocent Bugingo; I wrote most of the code (166 commits): the staff and patient web apps, the shared UI kit and API client, the Flutter patient screens, and the Django scheduling, patients, visits, clinical and facilities modules.
Challenges
The queue number only exists if reception enters it, so the facility side had to be built before the patient app. Patient data is protected in the database itself with PostgreSQL row-level security, and the API is tested against it in CI.
Impact
Every web-MVP sprint is built — onboarding, live queue, booking, clinical records, pharmacy, billing, notifications, disputes, the admin console, the public site and the Android app — with a live demo. A Rwandan staging environment and clinical sign-off come next.
Architecture
Patient PWA + staff web (React, TypeScript)Android patient app (Flutter)Django REST API + WebSocketsPostgreSQL with row-level securityRedis + Celery background jobs