Map your clinic’s patient journey: a practical before-and-after worksheet
Find the handoff that keeps breaking before you buy software to fix it. Start with one visit type and the people who do the work.
Ask a practice owner how a new patient books, and the answer may be simple: they call, they get an appointment, they complete intake.
Ask the receptionist to show you, and the picture changes. There is a voicemail queue, a question about visit type, a second call about a form and a spreadsheet used when the schedule gets complicated. Both people are describing the same practice. Only one version shows the work.
A patient-journey map makes that work visible. You do not need a large consulting exercise. You need a defined journey, the people who carry it out and enough honesty to draw the detours.
Choose a journey small enough to observe
Start with a specific visit: a routine new-patient appointment at one location, for example. Pick a clear beginning and end. An enquiry-to-arrival map is different from an entire episode of care, and both can be useful.
Invite someone from reception, an assistant involved in rooming and a clinician or clinical lead. Include billing or another team when the selected journey reaches their work. Name a person to maintain the map after the meeting.
Trace the process through approved records or direct observation without copying personal details into the worksheet. Record the kinds of information and actions that move between systems. A process map does not need a patient’s name, date of birth or medical history.
AHRQ’s ambulatory health IT workflow toolkit treats workflow assessment as part of planning, implementation and use. The worksheet here is an original, simplified operating tool—not a validated clinical assessment.
Draw what happens today, including the waiting
For each stage, ask four questions: what starts it, who acts, where they work and how the next person knows it is done. Add the time spent waiting for an answer separately from the time spent actively working.
A patient may spend a day waiting for a callback that takes a staff member two minutes. Those are different problems. Faster typing will not necessarily shorten a queue nobody owns.
| Stage | Current process | What can get lost |
|---|---|---|
| Send intake | Reception sends the standard link after booking. | No agreed check that it reached the right patient. |
| Complete answers | Patient finishes some questions and stops. | Missing answers look like a completed packet. |
| Prepare summary | An assistant reads and retypes responses. | Uncertainty or changes may lose their context. |
| Clinical handoff | A summary is available in a separate workspace. | Nobody has confirmed the reviewer received it. |
Do not label a staff member as the problem. “Reception forgot” is less useful than “the reminder existed only in one person’s memory.” The second description gives you something to redesign.
Mark the handoffs before proposing automation
Look for repeated entry, a task that crosses systems, unclear ownership and a “done” label that means different things to different people. Mark where a patient must repeat information already provided.
Then choose one change. Perhaps it is a shared enquiry queue rather than a new phone agent. Perhaps it is a reviewable intake summary with a receiving owner rather than another reminder message. The map should help you decide what is worth automating.
Before
Completion is assumed
- A form link is sent.
- Some answers arrive.
- A staff member retypes them.
- A clinician searches for the result.
Proposed workflow
Each handoff has evidence
- Intake is attached to the booked visit.
- Missing and uncertain answers remain visible.
- A structured summary reaches the agreed destination.
- A named reviewer checks it and records the next step.
The proposed side is a design target, not a claim that a particular product completes every step automatically. Keep software capabilities, staff actions and clinical decisions explicit.
Give every proposed step an owner and an exception path
“The AI handles it” is not enough for the owner column. Identify the person accountable for the workflow and the person or team that receives exceptions. Software can perform a supported task; a practice still needs to decide what happens when it cannot.
Write the failure path next to the normal path. If booking fails, does the patient get an accurate message and staff get a task? If intake is incomplete, who checks it? If an EHR handoff cannot finish, where does the work appear?
Separate administrative completion from clinical approval. A collected medication history is patient-reported information until the appropriate clinician reconciles it. A patient arriving at reception does not establish that they are clinically ready for the visit.
Use this detail to brief a supplier. Instead of “we need AI intake,” ask them to show how an incomplete answer stays visible and how the resulting summary reaches the person who reviews it.
Choose a measure that answers the original problem
If the problem is repeated entry, sample the staff touches required for the handoff. If the problem is lost enquiries, count requests with no owner or next action. If the problem is intake readiness, define the required items for that visit type and check readiness at a consistent point before the visit.
Keep a short measure definition beside the map: what is counted, which visits are included, the observation period and where the result comes from. Mark unknown data as unknown. Avoid comparing a quiet afternoon with the busiest morning and calling the difference a software result.
Include a balancing check. A quicker check-in that shifts more corrections to the clinical team may not improve the whole journey. Ask the next person in the chain whether the change actually helped.
Keep the map useful after the workshop
Test the proposed process on the selected workflow, review exceptions and update the map with what staff actually do. Remove obsolete shadow lists only after the team has a dependable replacement and agrees who owns it.
Moxcares has two adoption paths: keep your EHR and connect the patient-engagement workflow, or use the full practice platform. The map can help you decide which scope fits. Optional clinical and financial modules should be evaluated against their own handoffs, rather than added because they appear in a bundle.
Practice consultants, educators and clinic teams may adapt the worksheet for workshops and internal work. If you publish a version, link to this article so readers can find the instructions and current blank template. Keep patient information out of publicly shared examples.
Keep reading
Start with the handoff you want to change
Use your patient-journey map to explore what can move around your existing EHR, and where your team stays in control.
Explore the keep-your-EHR solution