Providence Telestroke & Express Care

Designing high-stakes clinical workflows for on-demand emergency care. From a real-time telestroke platform with remote diagnostic hardware to a multi-product Express Care scheduling suite used by patients across Providence's network.

  • Role: Product Designer
  • Company: Providence Health & Services, Digital Innovation Group
  • Timeline: 2017–2018
  • Platform: Web, iOS, Android
  • Tools: Sketch, InVision (Craft), Zeplin, Abstract, Adobe Creative Cloud, Storybook, React Toolbox, Source Sans Pro

The Problem #

Providence's Digital Innovation Group was building two distinct healthcare products simultaneously, each with fundamentally different users and stakes. On one side: emergency clinicians managing time-critical stroke alerts across a distributed hospital network, switching between four separate systems during a patient handoff, every second of context-switching a clinical risk. On the other: patients trying to navigate between four separate care services (Urgent Care, Virtual, Primary, Same-Day) that had no shared scheduling layer, no common identity, and no consistent experience.

The existing tools had been built for billing and back-office workflows. Neither was designed for how clinical staff actually worked under pressure, or for patients making care decisions in moments of stress or uncertainty.

My Role #

Providence's Digital Innovation Group brought me in as a product designer with a dual mandate: design the clinical workflows for a new video-based emergency care platform, and rearchitect four existing care services into a unified scheduling and marketing suite with a shared multitenant architecture. I worked with Sunny Lee and Kelly Elston on the research and service design phases across both products, and led visual design and interaction design from early wireframes through the Storybook component library. My contribution spanned discovery research, service design, interaction design, design system development, and engineering collaboration through to production.

Telestroke Platform #

Providence needed an on-demand emergency room video call platform that could handle remote diagnostic instruments (cameras, handheld JedMed tools, and hardware mounted on carts) alongside a live patient record pulled from the medical database Epic. The clinical UX challenge was significant: providers rarely looked at a screen during the critical first minutes of a telestroke consult. They used the interface as a reference after the initial assessment. Observing clinical staff during actual patient handoffs revealed this early and it inverted our original information hierarchy. We moved the patient vitals and NIH Stroke Scale tool from a secondary panel into the primary video overlay where they could be scanned peripherally, not hunted for.

After partnering with Sunny Lee and Kelly Elston to research Providence's established caregiver process, protocol, and hardware, we designed and tested service workflows and case management tools. The result was a platform that put patient context exactly where a clinician's attention already was.

Provider view of the video service from a cart situated in a patient's room. Clockwise from the top left: Patient information card with NIH Stroke Scale tool, provider account, audio/video controls, remote camera controls, saved XYZ view positions, self view, on-cart tool controls.

Example of switching to the handheld JedMed video tools. The UI had to remain legible with a provider's attention split between the instrument and the patient.

Telestroke dashboard for centralized management of session requests and hardware connectivity with partial Epic API integration for patient records.

Progression of screens for a hardware diagnostic system. During an onsite research session a nurse described their training for medical hardware: as soon as a tool wasn't working, there was no time for diagnostics — just move on to the next procedural step. This helped us rework a technician-led diagnostic tool to instead run automatically on the platform side, checking its own status and reporting to an IT lead.

Express Care Suite #

A quartet of established care services, Urgent Care, Virtual Care, Primary Care, and Same-Day Care, were rearchitected as a suite of Express Care options and brought together on a shared marketing and scheduling platform with a multitenant architecture. The user problem: patients experiencing a non-emergency health issue faced four separate websites, four separate scheduling systems, and no guidance on which type of care they actually needed.

The design challenge was building one shared experience that could surface the right care option for a patient's specific situation: handling symptom triage, insurance coverage and cost transparency, appointment selection, and registration across four distinct service contexts and multiple Providence locations.

A clinic location page with appointment time selection, symptom triage, insurance coverage and costs.

Custom skin for the prototype dashboard (patient detail view) built on Salesforce.

Patient registration — dark theme, multi tenant. The form handled family registration while maintaining Epic record-matching accuracy.

The same registration flow in light theme, multi tenant. Material's theming system let us adapt to different care contexts without rebuilding components.

An example of different form states used throughout the paperwork sections.

Material's card-based structure imposed on the sign-up forms.

Toast and status bar error states.

Progress indicators and success states imposed to clarify user actions.

Modifying Material for Healthcare #

Material Design out of the box felt too clinical for healthcare, too cold for a platform where both patients and caregivers were under stress. We warmed it systematically: Source Sans Pro for its humanistic feel, increased corner radii, expanded padding throughout. Those weren't aesthetic choices, they were empathy decisions, backed by feedback from users who described the default Material feel as "like a database."

The system was grounded in a 960px wide 12-column structure and 16px baseline grid. Material's theming architecture let us maintain visual consistency across multiple Providence brand applications, including a dark theme for the telestroke clinical context and lighter variants for patient-facing Express Care screens, from a single component set.

The engineering collaboration was built directly into the workflow. Working with the team in Storybook, taking React Toolbox and subbing in custom typography, rounded corners, and opened-up styles, meant interaction patterns migrated into components without a handoff gap. Design decisions stayed intact through to production.

Design language applied to a provider's detail view.

Leveraged Material's mentality for simple theming variations and a single type choice. A 960px wide 12-column structure and 16px baseline grid formed the basis of the Material modifications.

A prototype user flow, as seen in Sketch + InVision's Craft prototyping method.

Research & Wireframes #

Collaborated with Sunny Lee to help develop a mapped-out user flow.

Collaborated with Sunny Lee to accommodate native apps interacting with web services.

Collaborated with Sunny Lee on administrative dashboard wireframes. Many iterations until we ended up with something that helped the staff and didn't add daily stress.

Collaborated with Sunny Lee to develop mobile wireframes for video visits.

Express Care scheduling flow wireframes, early IA and navigation structure.

Registration and account management wireframe review, iterating on form structure and step sequencing.

Scheduling and intake wireframes, symptom triage and insurance coverage flows.

Outcome #

The telestroke platform launched as Providence's on-demand emergency video service, integrating with Epic for live patient record access during active sessions. The Express Care suite consolidated four separate scheduling experiences onto a shared multitenant platform, reducing friction for patients navigating between Urgent Care, Virtual, Primary, and Same-Day appointment types.

The design system established during this engagement, Material-based with healthcare-specific modificationsm was adopted by subsequent product teams within the Digital Innovation Group. Working directly in Storybook with engineering meant components shipped with design intent intact, without a separate handoff cycle.