Patient app for a clinic group
A consumer app that never authenticates against the clinical user table.
The problem
The clinics ran on a system whose identity model belonged to staff: doctors, receptionists and administrators, each carrying clinical permissions. Patients needed an app of their own. Putting them into that same user table would have left every consumer account one bug away from clinical access.
What I built
Patients get a separate identity with its own registration, device tokens and sessions, linked to the clinical patient record rather than merged into it. The app talks to a dedicated, versioned mobile API instead of the staff endpoints, which keeps the consumer surface free to change without touching the clinical system. The client is Flutter, so one codebase covers both platforms.
Where it landed
A consumer account cannot inherit a clinical permission, because it is not the same kind of account. The app also ships on its own release cycle.