A caregiver's morning — three generations, one app
The patient app wasn't built for patients. It was built for the family member who manages everyone else's appointments — and her own — between school drop-off and the office.
The most frequent user of the MediSero+ patient app is not the patient.
That sounds like a glitch. It isn't. When we segmented patient-app usage in February, the heaviest accounts were almost all adult women between 32 and 48, each with three or four "family members" linked to their account. The pattern was so clean it was almost funny: one user, one phone, one login, three or four people whose health was being managed from it.
This is not a regional thing. It's how families work. The mother who never quite retired from running the household ends up running the medical calendar of two parents, a spouse, and however many kids are still at home. The father has the WhatsApp group; the mother has the records.
What a typical morning looks like
One of our pilot clinics let us follow a few caregiver users for a week. Here's a composite morning, anonymised:
It's 7:15am. The caregiver is in her kitchen with one hand on a kettle. Her phone is on the counter. She opens MediSero+ and the first screen — Home — shows three profile cards stacked: Mother, Father, Self. She has notifications on the mother card: "Lab report uploaded." On the father card: "Refill due in 3 days." On her own card: nothing today.
She taps Mother. The lab report is a routine quarterly HbA1c — 7.1, slightly up from last quarter. There's a note from the endocrinologist: "Up by 0.4. Continue current regimen, recheck in 6 weeks." She forwards the report to her sister in Toronto via the Share button — long-press, "Share with family", picks her sister from the linked contacts. The sister gets a read-only copy with a one-line note: "Up slightly, doctor wants to recheck."
Back to Home. She taps Father. The refill notice is for his blood pressure tablets — telmisartan + amlodipine. She taps "Request refill". The screen shows the active prescription, the doctor who wrote it, and a button: "Send to doctor". She taps it. Done. The doctor will get a refill request in their inbox; if approved, the new Rx will go to the linked pharmacy automatically.
Now it's 7:24am. The kettle has boiled. She pours tea, opens her own profile, books a follow-up for her own diabetes consult next Tuesday — three taps, including picking the slot. Then she closes the app.
Total time spent: about ninety seconds.
What this replaces
Before MediSero+, the same morning involved:
- A WhatsApp message to the endocrinologist's receptionist asking when the lab report would be ready.
- A phone call to the father's GP receptionist to schedule a refill, because the GP doesn't do WhatsApp.
- A second phone call to the pharmacy to confirm they had the medications in stock.
- A photo of the prescription forwarded to the sister via WhatsApp, which involved finding the prescription paper, photographing it, and then realising the photo was unreadable and re-photographing it.
- An online form on a clinic's portal to book her own follow-up, which required filling in name, phone, DOB, problem (again, every time), and then waiting for an email confirmation.
The total time was somewhere between 25 and 45 minutes, spread across the day, and most of it was friction, not work.
The patient app didn't add a feature. It collapsed five surfaces — WhatsApp threads, phone calls, paper records, online portals, photo forwards — into one. Once it was one surface, the work to use it dropped to ninety seconds.
What we got wrong on the first version
Our first patient-app design assumed the patient was the user. Each account had one profile. Family members were a "linked contact" feature — you could see your spouse's records by switching profiles, but the experience was clearly secondary.
Then we watched real users. They didn't switch profiles — they wanted everyone visible at once. They didn't think of themselves as the "primary" account; they thought of themselves as the household's coordinator. Switching profiles felt like a context-shift in the wrong direction.
So we redesigned around aggregate-by-default. The home screen shows everyone you manage in one stack. Notifications are grouped per family member but visible at the household level. Vitals, refills, follow-ups all aggregate up. You can drill into a specific person, but the default is the household.
What this changed for the clinic
Two surprising downstream effects.
First, follow-up adherence went up. When the caregiver sees three "due in 3 days" notices on her home screen, she resolves them in batch. Before, each notice was a separate phone call she might procrastinate on. After, it's a 90-second pass through the app. Pilot clinics measured a 31% improvement in 30-day follow-up adherence on accounts with linked family members.
Second, FD phone-call volume dropped. About a third of inbound FD calls were "is the report ready?" or "can I refill X?" — both of which are now self-serve. FD-side analytics show roughly 40% fewer inbound calls per booked patient at clinics where 60%+ of patients have the app installed.
What we still need to fix
The single biggest complaint from caregiver users is elderly patient access to their own records. The 70-year-old father who has his own login (not linked to the daughter's) finds the app harder to use than the daughter does. Larger fonts and an "easy mode" toggle help, but the real fix is a "shared access" mode — where the elderly patient consents to give the caregiver read-write access while still owning their own login.
We're shipping that in May 2026. The technical work is done; the consent flow is the harder problem — making sure the elderly patient understands what they're agreeing to without making the consent screen so long that nobody finishes it.
Why this matters
If you're building a patient-facing health app, the first instinct is to optimise for the patient's experience as a single user. That instinct is correct only for healthy adults — which is a small fraction of the people who actually use the app. The heavy users are the family coordinators, and the design language for that role is different: aggregate, batchable, fast.
We didn't see this until we shipped the wrong thing first. If you're earlier in the journey than us, save yourself the pivot.
The patient app is at app.medisero.in. If you've thought about this problem differently, we'd genuinely love to hear it — hello@medisero.in.