Product Design · UX/UI · Healthcare · SaaS
Simplifying Complex Healthcare Operations
Care coordinators were running patients, tasks, schedules and field routes across disconnected screens. The platform was restructured around the day they actually work through.
- Role
- Product Designer
- Tools
- Adobe XD, Jira
- Platform
- Web app + mobile
Scroll to explore ↓
01 — Overview
Operational software, judged by how fast a shift ends
Complex healthcare workflows were transformed into clearer operational experiences: dashboard, patient management, care tasks, scheduling, field routes, notifications and a companion mobile application.
Users were not shopping. They were repeating the same twenty actions all day, and every extra click was multiplied by a caseload.
Designed for
Representative user profile
Nadia, 34
Care coordinator
Goal — see what is late, what is next, and who needs her, in one glance at the start of a shift.
Frustration — patients, tasks, schedules and routes spread across disconnected screens.
Representative user profile
Tomás, 29
Field nurse
Goal — get his next visit, patient notes and an outcome log on his phone between stops.
Frustration — operational software built for a desk, not a moving day.
02 — Challenge
Four jobs, four disconnected screens, one shift
Context
Patient history lived one place, today's tasks another. Coordinators rebuilt context by memory.
Priority
Nothing distinguished an urgent task from a routine one until it was overdue.
Scheduling
Schedule and route were planned separately, so travel time was invisible until the day started.
Field use
Staff on the road were handed a desktop layout shrunk onto a phone.
03 — Research & workflow mapping
I mapped the shift before I mapped the screens
- 01
The day starts with triage, not browsing. The landing screen had to answer "what needs me first".
- 02
Most task updates are one field. They did not deserve a full-page form.
- 03
Scheduling decisions are geographic. A route view had to sit beside the calendar.
- 04
Field staff needed three things on mobile: next visit, patient notes, and a way to log the outcome.
“Tell me what is late, what is next, and who I am seeing. Everything else can wait.”
04 — Architecture & wireframes
One spine: today, patients, schedule, routes
Today
Triage: late, next, escalations
Patients
Record, history, care plan
Schedule
Calendar with capacity
Routes
Geography and travel time
Field flow
What a nurse does between two doors
Next visit
Patient and address load from the schedule
Patient notes
History and care plan reviewed before acting
Log outcome
Vitals and task status recorded on the spot
Sync
Update reaches the coordinator's dashboard immediately
05 — Final interface
Dense where it helps, quiet everywhere else
06 — Outcome & learnings
Fewer screens per task
Coordinators cleared their task list without switching between screens.
Updating a task went from a multi-field form to a single tap.
Field staff started logging visits from the app instead of calling them in.
What worked
Designing the triage screen first gave every later decision a test: does this help someone start their shift faster?
What I would change
I documented the component states after the first build rather than before it, which cost a round of rework with engineering.