10.4 Process Maps, Flow Diagrams, and Gap Analysis
Key Takeaways
- Map work-as-done, not work-as-imagined. A conference-room happy path from the policy manual is not a current-state map.
- Current state comes before future state. Drawing only the future EHR screen hides the handoffs, waits, and night-shift exceptions you must close.
- Swimlanes show who does what; delays and defects cluster at handoffs between ED, hospitalist, pharmacy, nursing, and HIM.
- Spaghetti diagrams show physical motion (printers, pharmacies, tube stations). Value-stream thinking separates value-added time from wait and rework.
- A real gap names a missing capability or break in flow. “Users need more training” is not a gap if the admitting screen cannot show the outpatient medication list.
10.4 Process Maps, Flow Diagrams, and Gap Analysis
Quick Answer: Task A.4 is seeing the work. Map current state (work-as-done) before future state. Use swimlanes for handoffs, spaghetti for physical motion, and value-stream thinking for wait versus value. A gap is a break in capability or flow—not a slogan that staff need more training.
Sections 10.2 and 10.3 gave you requirements and methods. Task A.4 is the picture those artifacts sit on. If the picture is a policy happy path drawn in a conference room, every later decision is fiction. CPHIMS wants you to choose the visual that matches the problem—emergency-department throughput, medication reconciliation across admission and discharge, pharmacy walking patterns—and to tell a real gap from a motivational poster.
Why visualization is an analysis skill
People describe the process they wish they ran. Night-shift nurses describe the process they actually run: a hallway bed that is not on the tracker, a home-medication bag in a plastic sack, a printer two units away, a pharmacist who retypes a list because the outpatient feed is blank. If you do not draw work-as-done, you will design for work-as-imagined and then blame users in hypercare.
Visualization is not decoration for a steering slide. It is how you find:
- Handoffs where orders, meds, or status disappear
- Loops and rework (re-entering home medications, reprinting labels)
- Decision points that differ by role or time of day
- Physical motion that no screen change will fix by itself
- Waits that dominate elapsed time while “touch time” is short
Current state before future state
Current state (as-is) is observed. Walk the route. Shadow a nurse, a clerk, a pharmacist, and a hospitalist on a weekday and a night or weekend. Include exceptions: isolation rooms, language line, trauma arrivals, downtime, a patient who cannot name their medications.
Future state (to-be) is designed after the current map and the gap are honest. It shows how work should flow with the new rule, screen, or layout. It is not a vendor screenshot pasted into a slide. It must still name roles, handoffs, waits you are willing to keep, and the downtime path.
Rules:
- Do not draw only the future state “to stay positive.” You will miss the break you came to close.
- Do not map only the happy path. The exam’s patient is the one who arrives at 02:00 with a paper bag of bottles and no outpatient record.
- Do not let a manager narrate the current state unchallenged. Managers know work-as-imagined. Frontline staff plus timestamps know work-as-done.
- Include the information systems as actors when they hold or drop data—not as a single box labeled “EHR.”
Which picture to draw
| Visual | What it shows | Use it when | Failure if misused |
|---|---|---|---|
| Simple flowchart | Sequence, decisions, loops | A single role’s path (how a nurse generates discharge instructions) | Hides who waits on whom |
| Swimlane (cross-functional) map | Who does what, and the handoff | ED to hospitalist to pharmacy to nursing on med rec or admission | Drawn from the org chart instead of the work |
| Spaghetti diagram | Physical movement on a floor plan | Walking to printers, pharmacies, tube stations, med rooms | Used for a purely digital routing problem |
| Value-stream view | Elapsed time split into value-added, wait, and rework | Door-to-disposition, time-to-reconciled-list, time-to-first-dose | Counting every click as “value” because a clinician touched it |
| SIPOC | Suppliers, inputs, process, outputs, customers | Scoping before a detailed map | Treated as the detailed current state |
Swimlanes are the high-yield CPHIMS visual. Each lane is a role or department. The arrows that cross lanes are where time and defects hide: ED nurse to hospitalist, hospitalist to pharmacist, pharmacist to bedside nurse, HIM to clinician on a deficiency. If your map has one lane called “clinical staff,” you erased the handoff.
Spaghetti diagrams are for motion you can walk. If pharmacists leave a satellite, walk to a central printer, return to the ED, then walk to the tube station for every STAT, draw the floor. Then ask whether the future state is a closer printer, a local device, or a process that should not print at all. A data-flow diagram of the claims interface will not show that walk.
Value-stream thinking does not require a factory certificate. For a patient in the ED, ask how many minutes were evaluation and treatment versus waiting for a bed, a troponin, or a transporter. For medication reconciliation, ask how many minutes were clinical judgment versus hunting, retyping, and waiting on a missing list. Future-state design should attack wait and rework, not just redraw the value-added box in a new color.
Flowcharts still matter for decision logic: what happens if allergies are unknown, if the outpatient list is empty, if the patient is a trauma activation. Those branches belong on the current-state map. If they exist only in a policy appendix, the build will miss them.
Gap analysis on the map
Once current state is true, mark the gaps on the picture. A gap is a missing capability, a broken handoff, or a wait you intend to remove—not a personality judgment.
Good gaps on an admission medication-reconciliation map:
- The outpatient medication list is not visible in the admitting lane.
- Pharmacy cannot see the hospitalist’s in-progress list, so they start a second list.
- Night shift has no downtime kit when the feed is down.
- Discharge teaching cannot start until a note that is not clinically required is closed.
Fake gaps:
- “Nurses need more training.”
- “Hospitalists should try harder.”
- “If people followed the policy, we would not need a map.”
If the admitting screen cannot show the outpatient list, the gap is system and workflow capability. Training will not create a feed. Section 10.2 already told you that; task A.4 is where you see it as a break between lanes.
Future-state maps must close the marked gaps or explicitly accept them with a risk owner. A future-state swimlane that still has three medication lists and a prayer at the handoff is not a design. It is the current state with nicer boxes.
Clinical workflow examples the exam likes
ED throughput. Current-state swimlanes include triage, registration, ED clinician, nursing, radiology, laboratory, bed management, and inpatient receiving. Spaghetti shows hallway beds and trips to a far CT. Value-stream time is mostly boarding wait, not the physician exam. The gap is often status visibility and bed assignment, not the color of the tracker. Future state that only redraws the tracker without a bed-management lane is skipped analysis.
Medication reconciliation. Lanes include the patient and family, ED or admitting clinician, pharmacist, bedside nurse, and sometimes a portal or outpatient EHR. The current map shows retyping and a second list. The gap is a single shared list at each transition. Future state has one list, visible actions (continue/hold/stop), and a downtime branch.
EHR upgrade. Map the current path that will change—not every module. If admission reconciliation screens and lab result acknowledgment change, those lanes and decision boxes are the current state you must observe before you draw the future click path.
How to read a CPHIMS visualization stem
- Was anyone observed, including nights and exceptions?
- Is the visual the right type (handoff vs motion vs wait)?
- Is the team drawing current state or only a future screenshot?
- Is the gap a capability break or a training slogan?
- Prefer the answer that observes, maps the handoff or the walk, and names a real gap.
Scenarios and exam traps
Scenario — conference-room ED map. A future-state swimlane for throughput is drawn from the policy manual. Night shift is not observed. Hallway boarders never appear. The map is work-as-imagined. Go to the floor, include nights and exceptions, then draw current state. Future state comes after.
Scenario — STAT pharmacy walks. Pharmacists walk from a satellite to a central printer, back to the ED, then to the tube station for every STAT. Start with a spaghetti diagram of that motion and a value-stream split of walk versus verify-and-release time. An entity-relationship diagram of the medication tables will not show the walk.
Scenario — med-rec “training gap.” After mapping admission reconciliation, the only gap listed is “users need more training.” Observation showed home medications in three systems and an admitting screen that cannot display the outpatient list. The gap is capability at the handoff. The future-state map must close the information break. Training cannot.
Watch these traps:
- Mapping policy instead of observed work-as-done.
- Drawing future state first, or only a vendor screen.
- Happy-path-only maps that omit nights, downtime, and exceptions.
- One lane called “clinical staff” that hides the handoff.
- Using spaghetti for a purely digital problem, or a data model for a walking problem.
- Labeling a missing feed or a broken handoff as a training gap.
Task A.4 closes Domain 3’s analysis quartet: know the life cycle, write the need and the Must, pick the improvement method, and draw the work as it is actually done. That is what CPHIMS is scoring before you ever pick a vendor in the next chapter.
A future-state swimlane for emergency-department throughput is drawn from the policy manual in a conference room. Night shift is not observed. What is the error?
Pharmacists walk from a satellite pharmacy to a central printer, back to the emergency department, then to the tube station for every STAT medication. Which visual should informatics use first?
After mapping admission medication reconciliation, the only gap listed is “users need more training.” Observation showed home medications in three systems and an admitting screen that cannot display the outpatient list. What is the CPHIMS reading?