Overview
Unified Clinical Workflows Across a Fragmented Legacy System
DaVita Healthcare Partners ran multiple disconnected clinical tools across their dialysis network. Nurses, PCTs, and billing staff each worked from separate applications for patient registration, scheduling, coding, and prescriptions. None of them connected.
I joined a centralized UX team contributing to two parallel tracks: updating a prototype suite that had gone stale on outdated clinical data, and designing new UX for ICD-10 billing, patient scheduling, and ePrescribe workflows. Both required learning a clinical domain fast and producing work that held up under scrutiny from physicians, product managers, and compliance teams.
Download Full PDF - Page 2
Clinical Patient Record, Read Mode
Key Metrics
Multiple Clinical Applications Delivered, Zero Rework from Stakeholders
- Stakeholder approval: All assigned screens completed and signed off by product managers, project managers, and UI leads
- Scope: Contributed UX across billing, patient registration, ICD-10 coding, scheduling, ePrescribe, and payer intelligence modules
- Process compliance: SharePoint-based approval workflow used for all deliverables, with zero revision loops after final reviews
- Clinical alignment: Conducted on-site clinic visits and cross-functional sessions with nurses, PCTs, and a nephrology physician to validate design decisions
- Legacy modernization: Converted outdated vendor Fireworks prototypes into Axure RP Pro high-fidelity wireframes with updated clinical data
Download Full PDF - Page 10
ePrescribe - New Prescription Order
Challenge
Outdated Prototypes, New Compliance Requirements, and Users Who Could Not Afford Errors
A vendor-built prototype suite existed but was years out of date, built in Adobe Fireworks, and too outdated to hand off to development. At the same time, the federal ICD-10 transition was forcing billing teams to change how diagnoses were coded across the entire organization.
The stakes were real. These tools supported nurses and PCTs during active patient care. Confusion in the interface had direct consequences for patient safety, billing accuracy, and regulatory compliance.
My job was to learn the clinical domain, translate business requirements into interaction design, and deliver production-ready visuals for development, all while working within a shared component library and a team spread across multiple cities.
Download Full PDF - Page 3
Clinical Record, Edit Mode with ICD-9 to ICD-10 Lookup
Role & Collaboration
UX Analyst, Embedded in a Centralized Cross-Functional Team
- Visited DaVita dialysis facilities to observe current documentation workflows
- Facilitated remote and in-person working sessions in Nashville, TN and Kansas City, MO with product managers and clinical analysts
- Collaborated with nurses, PCTs, and a nephrology physician to validate screen logic and data needs
- Converted legacy Fireworks vendor prototypes into Axure RP Pro high-fidelity wireframes
- Designed within a shared UI component library using Kendo UI to minimize development customization
- Used a SharePoint-based review workflow to obtain sign-off from business analysts, product managers, and UI leads
Download Full PDF - Page 6
Maestro - Patient Sheet, Edit and Read States
Research & Strategy
Clinic Observation and Cross-Functional Input Drove Every Design Decision
Before touching a wireframe, I visited DaVita clinics to watch how staff actually worked. Observing a PCT document patient information mid-treatment or a billing coordinator toggle between coding screens showed me things requirements documents skip over entirely.
I brought those observations into working sessions with product managers, clinical analysts, and a nephrology physician. Each session kept design decisions accurate and on-screen language consistent with how clinical staff actually work.
For ICD-10, I designed a lookup interaction letting billing staff cross-reference codes without leaving the patient record. For scheduling and facility management, I worked from business requirements to map data relationships and build screens around how clinic staff actually structured their day - by facility, POD, and chair assignment.
Download Full PDF - Page 4
Maestro Facility Map in read mode showing the POD and chair grid layout
Impact
Clean Handoffs, Compliant Workflows, and Clinical Staff Who Could Actually Use the Tools
Every assigned module was approved without a revision loop. The SharePoint review process kept feedback structured and the development team unblocked.
The ICD-10 lookup removed the need for external code reference tables during an already high-pressure compliance transition. The ePrescribe and refill management screens cut the number of steps to complete medication tasks. Facility and scheduling tools gave administrators a cleaner view of daily clinic operations.
Several modules were later placed on hold pending broader project decisions. The work that shipped was validated by every stakeholder and handed off without redesign.
Dialysis Clinic nurse checking patient vitals.