Northwestern Medicine » Patient Self-Scheduling

From manual scheduling and disconnected systems to one continuous patient experience.

Role
Senior UX Designer

Domain
Healthcare · Consumer UX · Enterprise Systems

Skills
Journey Mapping · Workflow Design · Systems Integration · Prototyping · Information Architecture · Stakeholder Collaboration · Accessibility

Overview

Finding a physician and scheduling an appointment should feel like one continuous task. At Northwestern Medicine, however, that journey crossed multiple platforms, teams, and technologies, often ending with patients requesting a callback to complete their booking.

I helped redesign the end-to-end scheduling experience, bringing together Northwestern's physician directory, Epic's scheduling platform, and the operational workflows behind appointment booking.

The goal was to let patients move from finding a provider to scheduling an appointment online, without unnecessary handoffs, repeated data entry, or premature account registration.

The Problem

One patient journey, multiple disconnected experiences

Northwestern Medicine's scheduling process spanned several independently developed systems:

  • Physician Directory: Northwestern's public-facing website, where patients searched for providers and explored care options.

  • Epic: The healthcare platform responsible for patient records, registration, and appointment scheduling.

  • Telephone Scheduling: Operators who handled appointment requests, contacted patients, and manually completed bookings.

Each environment had its own technology, interface conventions, and operational constraints. Moving between them introduced friction into what patients reasonably expected to be a single task.

For new patients, the prospect of registering for an account before even choosing an appointment added another obstacle.

The challenge wasn't simply redesigning individual screens. It was connecting an entire service experience across systems that weren't originally designed to function as one.

My Role

As Senior UX Designer, I mapped the end-to-end patient journey and developed the workflows and grayscale prototype that brought the proposed experience together.

This required close collaboration with Epic engineers, Northwestern's web and middleware teams, and representatives from the telephone scheduling operation.

Each team understood a different part of the process. My responsibility was to connect those perspectives, identify the breakdowns between systems, and develop an experience that balanced patient needs with technical and operational realities.

The resulting mapping and prototype provided a shared vision that could be reviewed across teams and demonstrated to senior physician leadership.

Research & Insights

Understanding the entire service, not just the interface

A critical part of the discovery process was understanding what happened before, during, and after a patient attempted to schedule an appointment.

Working with the scheduling operations team helped reveal the manual steps behind booking. Collaboration with Epic and web engineers exposed the requirements and limitations of the systems involved.

Mapping the complete journey revealed several opportunities:

  • Eliminate unnecessary handoffs. Patients shouldn't have to leave the digital experience and wait for a phone call to complete a routine task.

  • Preserve continuity between systems. Changes in platform, branding, or technology shouldn't force patients to reorient themselves.

  • Delay account creation. Patients should be able to explore providers and appointment options before committing to registration.

  • Avoid repeated data entry. Information already provided during scheduling should carry forward into the registration process.

These findings shifted the focus from optimizing individual interfaces to designing a connected patient journey.

Design

1. Mapping the future-state experience

I developed a comprehensive workflow mapping the patient's journey from physician discovery through appointment selection, registration, and booking.

The map accounted for interactions across Northwestern's website, Epic, and the supporting scheduling infrastructure.

It also gave stakeholders a common reference for discussing requirements, identifying dependencies, and understanding how decisions in one system affected the others.

2. Making registration the last step, not the first

One of the most important design decisions was allowing prospective patients to navigate the scheduling experience as guests.

Rather than asking users to create an account before exploring their options, the proposed workflow let them find physicians and select an appointment first.

Only when they were ready to complete a booking would registration become necessary.

This kept the patient's immediate goal, finding care, at the center of the experience.

3. Carrying information across systems

Deferring registration created an important technical challenge: preserving information collected during the guest experience.

I collaborated with the middleware team on a workflow that would pass relevant patient information into account creation, prepopulating fields wherever possible.

This reduced duplicate data entry and helped make the transition from guest to registered patient feel like a continuation of the same process.

4. Smoothing the transitions between platforms

The physician directory and Epic scheduling environment were built using different technologies, with varying navigation patterns, visual treatments, and branding.

Rather than treating those differences as isolated UI problems, I designed around the complete sequence of interactions.

The goal was to maintain clear next steps, consistent expectations, and continuity of information as patients moved between environments.

5. Bringing the experience together in a prototype

I translated the mapped journey into a comprehensive grayscale prototype.

The low-fidelity approach kept the focus on workflow, decisions, and system transitions rather than visual polish. It also made the complexity of the proposed experience easier to review with both technical and nontechnical stakeholders.

Together, the mapping and prototype demonstrated how independently developed systems could support a single, coherent patient experience.

Outcomes

The end-to-end journey mapping became a successful alignment tool across the teams involved in scheduling.

The prototype was demonstrated to senior physician leadership, illustrating how Northwestern could connect physician discovery, patient registration, and appointment booking into a unified self-service workflow.

Key accomplishments included:

  • Established a shared future-state workflow spanning the physician directory, Epic, middleware, and scheduling operations.

  • Designed a guest-first experience that deferred account creation until booking.

  • Collaborated with engineering on preserving patient information across the registration handoff.

  • Developed a comprehensive prototype demonstrating the connected experience to stakeholders and physician leadership.

  • Created a foundation for reducing reliance on manual callbacks and enabling patient self-scheduling.

The broader Northwestern Medicine digital patient platform served approximately 44,000 users daily, underscoring the scale and importance of improving its patient-facing experiences.

Artifacts

  • End-to-end patient journey map

  • Current-state and future-state workflow documentation

  • Grayscale scheduling prototype

  • Guest registration and data handoff flows

  • Cross-platform interaction designs

Previous
Previous

Fidelity » SimpleSwitch

Next
Next

Lumere » Cost Optimization SaaS Platform