ERbuddy
2025
From medication tracking to shared care coordination
ERbuddy already tracked medications and appointments. I identified an underserved patient–caregiver communication gap, led the product strategy and multi-role architecture, and carried three core flows through seven moderated usability sessions.
Overview
What is ERbuddy?
ERbuddy is an early-stage health management app for patients and the people who support them. Its beta brought medication reminders, appointments, and medical history into one place. Our brief was to understand why families were not using it consistently and identify what the product was missing.
Product | A mobile app for managing personal and family health information. |
|---|---|
Primary users | Patients, family caregivers, and supporters involved in ongoing care. |
Existing beta | A mobile app for managing personal and family health information |
Client challenge | Understand why families were not using the beta regularly and what the experience was missing |
Our response | A shared care direction built around role-aware navigation, easier health updates, and account switching |
Patient
Shares health updates
Medications, appointments, symptoms and feelings
ERbuddy
Keeps care information technology
Gives patients and caregivers one place to view and update what is happening
Caregivers/supporters
Follows and supports
Checks current information, helps coordinate care and switches between profiles
The paper bag
Dosage written by hand, sometimes translated so a caregiver could read them
The portal login
One per hospital, non-connected, most never opened for the person being cared for not
Memory
"They said they took it. Maybe they forgot." No shared either way
The daily phone call
A caregiver an hour away, judging a parent's condition by the sound of their voice.
Families were still managing care outside the app
The missing piece was not another way to track medication. It was a shared way to understand what was happening.
My Contribution
My role in the project
My Team
From left to right: Our professor, Josh,
Our Clients, Ashish and Gurmeet,
Claire,
Sakshi,
Karla
Before designing new screens, I focused on two questions, Where could ERbuddy offer something different and how should the product support both patients and caregiver?
I led
The competitive analysis, product audit, strategic framing, client presentation, information architecture, and task flows.
I worked with the team on
User interviews, research synthesis, usability testing, and high-fidelity design
Outcome
What we delivered
Use market research to narrow the brief
The competitive review was most useful when it helped us decide what not to build, rather than becoming a feature-comparison exercise.
Design roles as part of the interface
Multi-role products need more than account permissions. People need constant clarity about whose information they are viewing and what they can change.
Test relationships, not one isolated tasks
A longer pilot with real families would be the next step to understand whether shared visibility improves day-to-day coordination over time.
Delivery & Status
What we delivered
We presented a shared care direction for ERBuddy, demonstrated three tested flows, and handed the final architecture and design files to the client
3 Flows
Shared navigation, symptom and feeling updates, and account switching.
7 Sessions
Moderated usability testing that led to four design changes
Full handoff
Final information architecture, flows and design files delivered to ERbuddy.
Delivery & Status
What we delivered
What I would measure Next:
After launch, I would track whether caregivers can switch profiles successfully, whether patients complete health updates, and whether caregivers feel more informed about the patient’s current condition.
