Map a patient journey across three systems
The documented care pathway and the journey a patient experiences are different objects. Mapping the second, across the systems that each hold part of it, is where the waiting actually lives.
Every service has a documented pathway: referral, triage, appointment, procedure, follow-up, discharge. It is accurate about clinical intent and it is not a map of what a patient experiences, because the patient experiences the gaps between those boxes, and the gaps are where the systems hand off to each other.
This lesson is about mapping the second thing. It is operational work, not clinical work — you are not questioning care, you are finding out where the process loses people, and it is nearly always at a boundary rather than inside a step.
One thing before you begin. Work from de-identified records and from observing the process, and agree with the information governance lead what you may look at before you look at it. You do not need identifiable data to map a journey; you need timestamps, handoffs and system boundaries. Asking first costs an email and skipping it can end the engagement.
Start with one real recent episode
Take a single episode that completed in the last month, and reconstruct it from the systems rather than from the process document. Not a typical episode — a real one, with its date stamps.
Then take a second that took much longer than the first. The comparison between one that went well and one that did not is where the map earns its keep, because the difference between them is rarely a clinical difference. It is usually a Tuesday, a missing phone number, or a letter that went to an old address.
Interview the people who handled that episode, separately, and ask each what they did and what they were waiting for. “What were you waiting for” is the highest-value question in this work. It is how queue time becomes visible, and queue time is most of the journey.
Mark every handoff and name who holds the record
Draw the episode as a line, and mark every point where responsibility changes hands: one team to another, one system to another, the service to the patient, the patient back to the service.
At each handoff, write four things. Who is responsible after it. Which system holds the authoritative record now. How the next person finds out they have work — a worklist, a letter, a phone call, an email somebody has to notice. And what happens if nobody does.
That last question finds the real failures. A handoff that depends on somebody noticing has no owner when they are on leave, and nothing in any system will report that the episode has stopped. Those are the patients who reappear months later, having been nowhere.
Count your handoffs. Three systems typically means five or six, and each one is a place where an episode can come to rest silently. That count, on its own, is often the most useful single output of the exercise.
That is the opening. The rest of the lesson — the remaining sections, the exercise and the check-your-understanding questions — is behind the gate below.
This lesson requires full access.
Create an account to explore the published free lessons. This lesson requires full access; signing up does not purchase access or enroll you in Academy.