Healthcare UX Ecosystem

Care@Home

Three connected products. One unified care experience.

An integrated remote patient monitoring ecosystem โ€” built for clinicians, patients, and admins to work in harmony.

Adobe XDFigmaIllustratorAgile MethodologyDesign SystemsHealthcare UXPrototypingUser Research
Explore all 3 platforms
0 Platforms
Ecosystem
0+ Screens
Designed
0+ Sprints
Delivered
Healthcare
Industry

System Architecture

How It All Connects

Not three isolated apps โ€” one interconnected care ecosystem where configuration, data, and actions flow between platforms in real time.

01
Designer Dashboard
Control Plane โ€” Admins & Clients
Care PathsProgramsRulesBranding
Configures both platforms
02
Patient App
Data Source โ€” Patients
VitalsRemindersSymptomsChat
Real-time patient data
03
Clinician Dashboard
Care Delivery โ€” Healthcare Providers
AlertsRecordsAnalyticsCare Plans

Single Source of Truth

Designer Dashboard owns every care path, questionnaire, and monitoring rule โ€” pushed to both apps without a redeploy.

Bidirectional Care Loop

Patients record vitals and complete tasks; clinicians review, adjust, and respond โ€” all in real time.

Role-Aware Design

Tasks for patients, alerts for clinicians, controls for admins โ€” three languages, one shared design system.

The Ecosystem

Three Products.
One Mission.

For each product: the story behind the pixels, then the live prototype.

01For Healthcare Providers

Web Dashboard

Real-time patient monitoring at scale

A comprehensive clinical interface enabling healthcare providers to monitor vitals, review patient histories, manage care plans, and respond to alerts โ€” all from a single dashboard.

The UX Story ยท Chapter 01
01

Web Dashboard

Where nurses see the complete patient picture, so no deterioration goes unnoticed

01How it started

"These are premium clients. We cannot miss anything. Every patient deserves 100% care."

Care@Home was serving Mayo Clinic, Novartis, and other major health systems. Their patients were not in hospital beds. They were at home, monitored remotely. Nurses needed to spot deterioration before it became an emergency. Missing a single signal could mean missing a life threatening event.

Patient list โ€” every patient, every vital, at a glance
02Setting the scene

2

Designers

1

PM

5+

Engineers

100+

Sprints

03THE COMPLETE PATIENT VIEW

Nurses do not just need vitals. They need the entire clinical picture in one place.

Vitals

Continuous and episodic. BP, heart rate, SpO2, glucose, weight. Graphs over time.

Information

Demographics, medical history, care team, primary and secondary care paths.

Evaluations

How patients answered questionnaires. Heart failure, COPD, symptom reports.

Medications

Active and discontinued. Dosage, frequency, titration notes, tolerance issues.

Audio Samples

Cough and speech recordings for clinical analysis.

Clinical Notes

Symptom escalations, intervention notes, observations from the care team.

Care Logs

Operational history. Video calls, chart reviews, durations, outcomes.

Patient Diary

Patient generated notes. "Medication out of stock." "Feet swollen today."

Devices

Connection status, battery levels, last sync. BP cuffs, wearables, scales.

04STEPPING IN THEIR SHOES

Watched nurses during their monitoring shifts. Saw how they triaged. What they trusted. What they ignored. Where they got pulled into noise. Heard the same concern repeatedly: "What if I miss someone getting worse?"

05Key painpoints
01CLINICIANS

Drowning in alerts, missing the urgent ones

02DATA

Scattered across multiple tools and tabs

03TRIAGE

No way to know which patient needs attention first

06Existing vs Desirable Future

EXISTING

  1. 01Vitals in one tool
  2. 02Notes in another
  3. 03Medications in a third
  4. 04Patient calls go through email
  5. 05Nurses jump between systems
  6. 06Critical signals get lost

Fragmented. Risky. Easy to miss things.

DESIRABLE FUTURE

  1. 01One patient view, all data unified
  2. 02Vitals, evaluations, medications, notes
  3. 03Care logs and patient diary in context
  4. 04Device status visible at a glance
  5. 05Nurse stays in one tool
  6. 06No data missed, no time wasted

Unified. Confident. Complete.

07Designing

Three explorations.

REJECTED

Everything on one screen

Information dense, but nurses had to scan through noise to find what mattered. Too much cognitive load.

REJECTED

Alert centric dashboard

Showed alerts first, patients second. Nurses lost context. They needed the patient story, not just the alarm.

SHIPPED

Categorized patient view

One patient at a time. Information organized by clinical category. Nurses see what they need, when they need it. No noise, no scrolling for the signal.

08The trade-off

Nurses lost the population overview by default. The dashboard now opens to a patient list, not a vitals heatmap. Power users who liked seeing all 60 patients at once had to switch views. A deliberate choice. The depth of one patient mattered more than the breadth of all of them.

Patient list โ€” what the dashboard opens to now
09What it unlocked

Nurses stopped opening five tools to understand one patient. The complete patient story lives in one place. Vitals, medications, evaluations, care logs, patient diary, all visible in context. No data missed. No deterioration unnoticed.

100% care, the way premium clients deserve.

See the live prototype
Patient diary โ€” every signal the patient reports, in context
10 ยท The Live Prototype

Watch the shipped product in action.

LIVE PROTOTYPE
Vitals MonitoringPatient RecordsCare PlansAlert SystemAnalytics
02For Patients

Mobile Application

Healthcare in the palm of your hand

A patient-facing mobile app for iOS and Android, supporting vital recordings, medication reminders, symptom tracking, education, chat with clinicians, and remote device pairing.

The UX Story ยท Chapter 02
02

Patient App

Daily care for people who are unwell, without overwhelming them

01How it started

"If recording vitals takes ten minutes, elderly patients give up. We need it to take two."

Care@Home is remote care. Patients are at home, not in hospital. They are often elderly, often managing multiple chronic conditions. The app cannot ask too much. Every extra tap is a missed reading. Every missed reading is a clinical risk. Every confused patient is one who stops using it.

2 minTarget time to record a vital

Down from 10 minutes. The threshold between a habit and an abandoned app.

iOS ยท Patient
Care@Home
Today's tasks โ€” what the patient sees the moment they open the app
02Setting the scene

1

Designer (sole)

1

PM

5+

Engineers

100+

Sprints

03FIVE TABS, ONE GOAL

The bottom navigation is the entire product. If it does not work, nothing else matters.

Today

What needs doing right now

Vitals

Record and review measurements

Medication

What to take, when

Activity

What you completed today

Settings

Devices, preferences, support

04THE TODAY SCREEN

When a patient opens the app, they see one thing first: what they need to do today, in plain language, with their device status confirming everything is ready.

"By 11 AM, record your blood pressure. Your wearable is 100% charged. Your BP cuff is ready."

Not a calendar. Not a list of metrics. Not a wall of charts. Just the next task, the device they need, and the time. Recognition, not recall.

iOS ยท Patient
Care@Home
Today's tasks โ†’ Blood pressure recorded
05Key painpoints
01PATIENTS

Cognitive overload from too many options

02DEVICES

Pairing felt as complex as setting up a new phone

03DATA

Missed readings meant clinicians lost visibility

06Existing vs Desirable Future

EXISTING

  1. 01Open app to a complex dashboard
  2. 02Hunt for "record BP" button
  3. 03Pair device manually each time
  4. 04Navigate through three screens
  5. 05Submit and confirm
  6. 06Total time: 8-10 minutes

Friction. Frustration. Patients give up.

DESIRABLE FUTURE

  1. 01Open app, see today's task
  2. 02Tap "Record BP"
  3. 03Device auto pairs (already known)
  4. 04Reading captured automatically
  5. 05Confirm with one tap
  6. 06Total time: 2 minutes

Easy. Habitual. Patients return daily.

07Designing

Three explorations.

REJECTED

Calendar grid view

Showed everything at once. Felt clinical and overwhelming. Elderly patients felt judged by what they had not yet done.

REJECTED

Long checklist

Too many items visible. Patients lost focus. The next thing they needed to do was buried.

SHIPPED

One task card at a time

Always shows the single next thing to do. Plain language. Time stamped. Device status confirmed. No friction.

08The trade-off

Power users who liked seeing the whole week at a glance lost the calendar view by default. It is still available behind a setting, but the home screen now shows only the next task. The 80% of patients who were overwhelmed mattered more than the 20% who were confident.

iOS ยท Patient
Care@Home
Today's tasks โ€” the home screen now shows only the next thing to do
09What it unlocked

Patients stopped abandoning the app in week two. Recording vitals became a 2 minute habit, not a 10 minute chore. Clinicians stopped chasing missing readings. The app became part of the daily routine, not another thing to manage.

The simplest part of the platform. The most important.

See the live prototype
iOS ยท Patient ยท Step 1/4
Care@Home
01 ยท Open the task. Empty form, clear prompt.
10 ยท The Live Prototype

Watch the shipped product in action.

LIVE PROTOTYPE
Vitals RecordingRemindersSymptom DiaryClinician ChatDevice PairingEducation
03For Admins & Clients

Designer Dashboard

Customize the experience without code

A centralized no-code platform empowering clients and stakeholders to configure web interfaces, manage branding, and tailor the patient-facing experience โ€” all while preserving design system integrity.

The UX Story ยท Chapter 03
03

Designer Dashboard

One configuration tool. Three downstream products. Programs running across geographies and languages.

01How it started

"Mayo Singapore needs the heart failure questionnaire in English, Spanish, and Chinese. Every program is a custom build."

Care@Home was rolling out to major US health systems and global pharma partners. Each program needed its own care path, its own vitals, its own questionnaires, in its own languages. Engineering kept rebuilding the same setup for every new client. Onboarding took weeks per program.

Scroll
Custom questionnaire โ€” branching logic, three languages, one configuration screen
02Setting the scene

1

Designer (sole)

1

PM

5

Engineers

1

QA

100+

Sprints

03ONE TOOL. THREE DOWNSTREAM PRODUCTS.

A single change in the dashboard reaches every product clinicians and patients use.

Patient creation โ€” defines the onboarding fields the patient app collects
BP measurement โ€” defines the schedule and devices the web dashboard tracks
04WHAT THEY CONFIGURE

A program for heart failure or COPD is not one screen. It is a stack of decisions.

Mobile preview โ€” see exactly what patients will see
Tablet preview โ€” same configuration, different surface

A STACK OF DECISIONS

  1. 01Care path
  2. 02Vital monitoring
  3. 03BP measurement
  4. 04Schedule 1
  5. 05Frequency: Day / Week
  6. 06Session start & end time
  7. 07Repeat pattern

Seven levels deep, for one vital, in one care path. Every program is hundreds of these decisions, structured.

05Key painpoints
01CLIENTS

No control over their own programs

02ENGINEERING

Repeating the same setup per program

03SYSTEM

No safe path between custom and consistent

06Existing vs Desirable Future

EXISTING

  1. 01Client emails clinical requirements
  2. 02PM logs engineering tickets
  3. 03Engineers configure manually
  4. 04QA tests against requirements
  5. 05Release in next sprint
  6. 06Repeat for next program

Slow, manual, scales linearly with clients

DESIRABLE FUTURE

  1. 01Admin opens dashboard
  2. 02Picks care path and program
  3. 03Configures vitals, schedules, rules
  4. 04Previews each downstream product
  5. 05Publishes to production

Self serve, safe, scales without engineering

07Designing

Three explorations.

REJECTED

One long form per program

Every field for every product in one scrollable form. Admins lost their place by row twelve. Configuring the Patient app and Web dashboard felt like the same job, which it wasn't.

REJECTED

Sequential wizard, one product at a time

Step through Patient app, Web dashboard, HCP app in order. Admins finished step one with no way to compare it to step two. The shared logic between products got lost between clicks.

SHIPPED

One category, one product, one preview

Configure one category at a time. Switch the tab to preview how it lands in the Patient app, Web dashboard, or HCP app. The admin always knows what they are editing and where it will show up.

08The trade-off

The dashboard exposes a lot. Every vital, every schedule, every language, every rule. Admins can configure it all, but it requires training. This is not a tool a nurse picks up in five minutes. A deliberate choice. Depth for the people who run the platform, simplicity for the people downstream.

Program features โ€” every toggle a deliberate exposure of depth
09What it unlocked

Hospital onboarding stopped going through the engineering queue. Admins built and updated their own programs. The same platform now serves heart failure in Singapore, COPD elsewhere, and a dozen other protocols, without a custom build for each.

Built once. Configured infinitely.

See the live prototype
Multiple shipped programs running in parallel
10 ยท The Live Prototype

Watch the shipped product in action.

LIVE PROTOTYPE
UI CustomizationBranding ControlsLive PreviewDesign SystemRole Management

Project at Scale

1000+ Screens. iOS & Android.

Every flow. Every edge case. Every state. A complete patient mobile app designed from the ground up over 100+ sprints.

All Care@Home patient mobile app screens โ€” iOS and Android
Complete design specJust a portion
Authentication
Device Pairing
Home
Settings
Reminders
Questionnaire
Blood Pressure
Weight
ECG
Cough/Speech
Chat
Blood Glucose
Symptoms
Education
Body Temp.
Patient Diary