Standalone apps for patients and care teams

The care plan lived in a paper folder.
A patient seeing four specialists had their plan spread across phone calls, folders and systems that didn't talk. Nobody had the whole picture, least of all the patient.
So I put the whole plan in one place.
One plan the care team builds and the patient follows, instead of two versions of it that never quite matched.
The care team builds it and watches it.
Everything a nurse needed was on the patient's page: the plan, the timeline, and a way to reach them.

The patient only has to see today.
Six tasks, a progress ring, and one tap to their care team. Testers kept pointing at the ring: that was the part that brought them back.

Three patients, one plan to hold them all.
Designed for three risk tiers rather than an average patient, each with its own values, goals and pain points.

A question shouldn't mean a phone queue.
Apollo answered in the app: triage first, then the article that actually answers the question.

Every icon drawn, not downloaded.
One set across care plans, scheduling, messaging and results, so a patient learned each shape once.
The weeks between visits stopped being invisible.
Daily check-ins, surveys and education, with 200+ wearables feeding it, so the care team could see the time they used to miss.
What it shipped with.
Patient personas
3 risk tiers
Resonance interviews
5
Wearable integrations
200+
Wearables through Validic; education content from Mayo Clinic, NIH and epocrates.
The Team
- 1 Senior Product Designer
- Care team engineering
- Clinical content partners
Timing
2017–2018
Care Plan design & validation
5 interviews
Resonance-testing round
Tools Used
Figma
Miro
Jira
Up next