Patient journey platform - healthcare UX case study

01

Scattered journey mapping became one reusable product model

Healthcare teams get one structured way to create, adapt and enrich complex patient and professional journeys, in every market.

Every team described journeys, touchpoints, emotions and service gaps in its own way. Knowledge was hard to reuse and decisions were hard to align.

My answer: a shared hierarchy, room for local adaptation, evidence in layers and an accessible component system.

Product names, client identity, original screens and operational data are left out on purpose. The screens here are my own 2026 redesign on a fictional journey: the interface is real, the content isn’t the client’s.

02

One hierarchy holds shared structure, local variation and evidence together

Four product principles kept the platform useful without erasing the detail that makes a journey credible.

Shared foundation

Universal journeys establish a reusable structure and common language across teams.

Local adaptation

Local teams can adapt the foundation to a country, audience and healthcare context without starting again.

Layered evidence

Interactions, emotions, pain points, insights, outcomes and sources remain attached to the episode they explain.

Controlled evolution

Draft, review and publishing states let a journey develop over time while preserving ownership and structure.

03

The hierarchy, and what a shared model has to pay back

A common structure is a cost for every local team, so it has to return something they can’t get on their own. Five levels carry the structure; three consequences are what it buys back.

Journeythe whole experience
Meta journeya goal or phase
Stagea meaningful period
Episodean evidence-rich moment
Stepan action and touchpoint

Journey hierarchyAbstracted model · not a client export

How deep can a shared structure go before it stops matching a real journey?

Each level narrows the frame by one step, and only the two deepest levels carry evidence. That is the boundary: above the episode the model is shared and enforced, at and below it every local team decides what is true for its own market. The client’s terminology, screens and journey content are not shown.

5 structural levels
3 perspectives
2 authoring modes
2 evidence-bearing levels

Abstracted model - shown for presentation purposes only

Reuse becomes explicit

A local journey starts from a universal one, so a team can see what already exists instead of recreating a map from zero.

Evidence stays where it was gathered

Interactions, emotions, pain points and sources stay attached to the episode they explain, so a shared structure never flattens a local finding.

Ownership survives the edit

Draft, review and published states let a journey evolve while it stays clear who owns it and which version is authoritative.

04

Four product paths turn a complex map into manageable decisions

The paths come from the platform design record. The views below are my 2026 redesign of the interface, built on fictional content, not client exports.

Discoverreuse before duplication

Find the right journey before creating another one

Owners and viewers search existing journeys, filter by customer type, specialty and scientific area, and open a journey in view or edit mode.

Redesigned screen with fictional content. No client UI or data is shown.

Redesigned journey library with search, filters and journey cards, shown with fictional content

Create universalstructure before canvas

Define a reusable foundation for a journey

A creator selected HCP, Patient or Caregiver, supplied classification and ownership data, then created a journey from scratch or from a template. The documented flow accounts for cancel, success and existing-journey conflict states.

Redesigned universal journey creation step with classification fields, shown with fictional content

Adapt localpreserve the local context

Start local work from a universal journey

A local journey began with an existing universal foundation, then added country and local context, required elements and a draft or publish decision. This made reuse explicit rather than leaving teams to recreate maps from zero.

Redesigned local journey adaptation step built from a universal journey, shown with fictional content

Build and enrichevidence stays in context

Keep the detail with the episode it explains

Editors move through meta journeys, stages and episodes and attach what they learn: interactions, channels, people, emotions, pain points, insights, quotes, outcomes, metrics, opportunities and sources. They can save drafts, publish, zoom, and view one or two episodes at a time.

Redesigned journey editor with an episode and its evidence lanes, shown with fictional content

05

Each iteration reduced ambiguity in the model, not polish in the interface

The process moved from existing practice and shared language to cross-regional validation and delivery detail.

Discover

Map the work already happening

Benchmark tools, interview stakeholders and map how journeys were created, stored and reused.

Tool benchmarkStakeholder interviewsCurrent-practice map

Structure

Test the hierarchy before the canvas

Define the hierarchy, terminology and relationship between universal and local journeys before optimising the canvas.

Five-level hierarchyShared terminologyLow-fidelity structures

Validate

Specify states for delivery

Test navigation, authoring and regional variation with cross-regional teams, then specify states and edge cases for delivery.

Cross-regional sessionsInteraction statesHandoff library

The achievement was not a prettier journey map. It was a shared language that could hold global consistency and local truth at the same time.
Patient journey platform principle

06

UX/UI leadership from problem framing to implementation quality

I shaped the experience architecture, the interaction model and the interface system, and coordinated the design work with research, product and engineering.

Problem and scope

I turned scattered practices and what stakeholders needed into one clear problem and a direction for the experience.

Workflow and expectations

I ran workshops and interviews with stakeholders and benchmarked competing tools, to learn how teams created, stored and reused journey knowledge.

Information architecture

I defined the hierarchy, the link between global and local, and the content layers that make complex journeys easy to navigate.

UX and UI

I led flows, prototypes, interaction states and detailed interface design across creation, editing, discovery and review.

Team direction and reviews

I coordinated the design work and reviews, and kept research, UX and UI pulling in one direction.

System and quality

I aligned the work with the design system, accessibility and developer handoff, and supported implementation reviews and QA.

07

The design record shows the system and the depth of delivery

What the design record covers: scope, structure and depth of delivery.

The source design documents shared and local journey creation, discovery, editing, publishing and supporting dialogs.

A dedicated handoff library covers components, states, accessibility guidance, icons and content patterns.

Client identity, original screens and operational data are left out on purpose.