Lesson objective
Produce a workflow map of a practice process as it is really performed, capturing undocumented steps, workarounds, the exception that is really the rule, and the person everybody asks.
Plain-language explanation
Why this matters now
Every practice has two versions of every process. There is the written version, which lives in a binder or a shared drive and was last edited when the practice changed its phone system. Then there is the real version, which lives in the hands of the people who do the work, and which nobody has ever written down because nobody had to.
Automation is applied to the written version and then runs against the real one. That is the whole failure in a sentence. A tool built to the binder will handle the path the binder describes and will meet, on its first day in production, a dozen conditions the binder never mentioned: the referring office that faxes at 5.40pm, the payer portal that logs staff out after ten minutes, the patient whose guardian is recorded only in a note on the appointment, the insurance card photographed at an angle.
Professional guidance (voluntary framework): NIST's AI Risk Management Framework (AI RMF 1.0, NIST AI 100-1, released January 26, 2023) places MAP before MEASURE and MANAGE, and says that after instituting GOVERN outcomes "most users of the AI RMF would start with the MAP function". It is voluntary and binds no practice. The ordering is the useful part. You cannot measure or control a process you have not described, and describing it honestly is harder than it sounds because the people who know it best stopped noticing it years ago.
There is a second reason to map first. Professional guidance (vendor research, not about medical practices): the Thomson Reuters Institute 2026 AI in Professional Services Report, published February 9, 2026 with more than 1,500 respondents across legal, tax and accounting, corporate functions and government in 27 countries, found that "only 18% of respondents said they knew their organization was tracking return-on-investment (ROI) of AI tools in some manner." Those figures are for professional services generally and are not figures for physician practices, and the report is produced by a company that sells AI products. Read it narrowly: it is common for organisations to deploy these tools without knowing what the work looked like before. A map is the first half of the cure.
A question to sit with
Take the one process your practice is most confident about. If the two people who run it were both away for a fortnight, how much of what they do could a temporary hire reconstruct from your written procedure, and what would they get wrong on the first morning?
What goes wrong
The map records the policy, not the work. Someone writes the process from memory at a desk instead of watching it happen, and produces an idealised version in which nothing is ever missing, late or ambiguous.
Workarounds are invisible because they are embarrassing. The staff member who keeps a private spreadsheet of payer quirks, the coordinator who calls a friend at the referring office rather than waiting on the portal, the biller who holds certain claims back until Thursday: all rational, all undocumented, all load-bearing.
The exception is really the rule. The procedure describes the standard path and adds "exceptions are handled case by case". Count them and the exceptions are 40% of the volume. A tool built for the standard path therefore covers the minority of the work.
One person is the process. There is a name everybody says when something is unclear. That person is a dependency, not a resource, and no map that omits them is complete.
Invisible rework never gets counted. Work that goes back a step, a claim that returns, a form re-sent, a message reopened. Staff rarely think of rework as work, so it does not appear in anyone's description of the process.
The map stops at the practice walls. Half the delay in a referral or a prior authorization sits with someone else, and a map that ends at your own outbox cannot show where the time actually goes.
The practical answer
Map by watching, not by asking. Best practice: sit beside the person doing the work for a full cycle, take the notes yourself, and say plainly that you are mapping the process rather than reviewing the person. Staff who think they are being appraised will describe the binder version, which is exactly the version you already have.
Record each step in one row:
| Column | What goes in it |
|---|---|
| Step | What is actually done, as a verb and an object |
| Who | The role, and whether anyone else can do it |
| System | The system or paper the step touches |
| Input | What has to exist before the step can start |
| Wait | Time spent waiting on someone outside the step |
| Exception | What happens when the input is missing, late or wrong |
| Undocumented | Yes if the written procedure does not mention it |
Then walk the four areas separately, because they fail differently.
| Area | The steps people forget to record |
|---|---|
| Front desk and scheduling | Verifying identity, checking coverage, capturing a card image, noting a guardian or interpreter need, deciding whether a request is urgent |
| Clinical inbox | Sorting messages that arrive under the wrong subject, deciding what is clinical, finding the right clinician, closing the loop when nobody replies |
| Documentation | Gathering what the clinician needs before the encounter, drafting, correcting, routing for signature, addenda after the fact |
| Billing office | Reading the note, querying the clinician, assembling the claim, working a denial, deciding whether to resubmit or appeal |
Hunt for the four things a map usually misses. These are this programme's recommendation.
- The private spreadsheet. Ask directly: what do you keep outside the practice systems to do this job? There is almost always something, and it is usually the knowledge a tool would most need.
- The unwritten routing rule. How does someone decide who gets this next? The answer is frequently a judgement nobody has ever articulated.
- The exception rate. Count exceptions over two weeks and express them as a percentage of volume. If it is above a quarter, stop calling them exceptions.
- The person everybody asks. Name them on the map, count how many steps route through them, and treat that count as a risk.
Draw the swim lanes, not a straight line. A process drawn as one line implies one path. Draw a lane per role and the handoffs appear as arrows crossing lanes, which is where most of the delay and nearly all of the lost context lives. Lesson 2 takes those crossings apart.
Mark what the map is for. A map made to justify a purchase will be shaped by the purchase. AI Coalition Network recommendation: write at the top of the map that its purpose is to describe the work, and finish the map before any tool is shortlisted. A named person owns the map, dates it, and records who was observed and over what period, so the next reader knows how much to trust it.
Remember this
- Map the work by watching a full cycle, not by asking someone to describe it.
- Record undocumented steps, workarounds, waits and exceptions as first-class parts of the process.
- Count exceptions; if they exceed a quarter of volume they are the process, not exceptions to it.
- Name the person everybody asks and count the steps that depend on them.
- Date the map, name its owner, and finish it before any tool is shortlisted.
Medical practice example
Cedar Hollow Family Medicine, a fictional four-clinician practice, decides to look at how new-patient registration really works before considering any intake tool. The practice manager, Wren Castellano, sits at the front desk for three mornings and writes down every step as it happens, telling the two coordinators plainly that she is mapping the process and not reviewing them. The written procedure has five steps: greet, confirm identity, collect forms, scan the insurance card, seat the patient. The map she produces has nineteen. Among the fourteen the binder never mentions: the coordinator checks the appointment note for an interpreter request because the scheduling field for it was retired two years ago and nobody removed the habit; she re-photographs about one card in six because the laminate reflects the overhead light; she keeps a personal note listing which of four plans need a separate referral number, updated whenever she is told something on a call; she walks a paper form to the nurse station for any patient over a certain age because the form never made it into the portal; and she asks the other coordinator, Dolores, whenever a plan name is unfamiliar. Wren counts: registrations that deviate from the binder path run at 31 of 96 over the three mornings, which is 32.3%, so the exception is not an exception. Six of the nineteen steps route through Dolores, who has worked at Cedar Hollow for eleven years and is the only person who knows two of the payer quirks by heart. Wren writes the map with a date, her own name as owner, and a line recording that it covers three weekday mornings and no Friday or month-end. She shortlists no product. Her first conclusion is that the interpreter request needs a real field again, which is not an AI project at all.
Responsible-use warning
Do not build a workflow map from a meeting. A room full of experienced staff describing a process will produce the version they believe they follow, edited for how it ought to work and for who is listening. The steps that matter most to automation are exactly the ones nobody mentions in a meeting: the private spreadsheet, the re-photographed card, the phone call that bypasses the portal, the form walked down the corridor. Those appear only when someone sits beside the work for a full cycle and writes down what actually happens.
Human-review requirement
The practice manager or named administrative owner owns the workflow map, dates it and records who was observed and over what period. Where the mapped process touches clinical work, the physician or advanced practice lead who owns documentation and the clinical inbox reviews the map and confirms that the clinical steps are described correctly, particularly any point where a clinical judgement is being made by someone who is not a clinician. The privacy official reviews the map for the points where patient information moves, which Lesson 2 marks explicitly. A map nobody has signed and dated is a draft.
Practical exercise
Use fictional or fully anonymised material only. No real patient information.
- Choose one process in one of the four areas: front desk and scheduling, clinical inbox, documentation, or the billing office. Pick one you believe is well understood.
- Read whatever written procedure exists and count its steps. Write the number down before you observe anything.
- Sit beside the work for at least one full cycle, telling the staff member plainly that you are mapping the process and not reviewing them. Record each step using the seven columns in this lesson.
- After the observation, ask the person one question directly: what do you keep outside the practice systems in order to do this job? Record whatever they name, including private notes, spreadsheets, phone contacts and habits.
- Count how many of your observed steps the written procedure does not mention, and calculate that as a percentage of the total.
- Over a two-week window, count cases that deviated from the standard path and express them as a percentage of volume. If the result exceeds 25%, rewrite the map so the deviation becomes a named path rather than an exception.
- Redraw the map with one lane per role, so every handoff appears as an arrow crossing a lane. Mark every wait where the process is held up by someone outside the practice.
- Name the person the most steps depend on, count those steps, and write one paragraph on what the process would do next week if that person were unavailable. Date the map, put your name on it as owner, and record the observation period.
Knowledge check
-
Why is a workflow map built from a meeting usually the wrong map?
Answer guidance: A room of experienced staff describes the process they believe they follow, edited for how it ought to work and for who is listening. The steps that matter most to automation are the ones nobody mentions: the private spreadsheet, the re-photographed insurance card, the phone call that bypasses the portal, the form carried down the corridor. Those appear only when someone observes a full cycle and writes down what actually happens.
-
What should a practice conclude if exceptions run at a third of the volume in a mapped process?
Answer guidance: That the so-called exception is really a second normal path, and that a tool designed only for the standard path would cover the minority of cases. The map should be rewritten so the deviation becomes a named path with its own steps and its own review, rather than being left to case-by-case handling that nobody has described.
-
What does the NIST AI RMF say about the order of the MAP function, and what is its status?
Answer guidance: NIST says that after instituting GOVERN outcomes, most users of the framework would start with the MAP function and continue to MEASURE or MANAGE, iteratively. AI RMF 1.0 was released January 26, 2023 and is intended to be voluntary, rights-preserving, non-sector-specific and use-case agnostic. It binds no physician practice and no regulator requires its adoption.
-
Why should the map record the person everybody asks, and what does that count mean?
Answer guidance: That person carries knowledge the written procedure does not hold, so the number of steps routing through them measures how much of the process would stop or degrade if they were unavailable. It is a dependency to be recorded and reduced, not a resource to be relied on, and it identifies exactly the knowledge a procedure or a tool would need to capture.
Sources and further reading
- National Institute of Standards and Technology — Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1 (2023-01-26). Accessed 2026-09-15.
- Thomson Reuters Institute — 2026 AI in Professional Services Report (2026-02-09). Accessed 2026-09-15.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.