13.1 Quality Improvement Methodologies and Tools

13.1 Quality Improvement Methodologies and Tools

High-Yield Exam Focus: On the ANCC CMGT-BC examination, quality improvement (QI) questions test the case manager's role as a clinical leader, systems thinker, and change agent. Candidates must master the IHI Model for Improvement and the rapid-cycle Plan-Do-Study-Act (PDSA) ramp, identify the eight forms of waste (muda) in care coordination, navigate the DMAIC lifecycle in Six Sigma, and distinguish prospective Failure Mode and Effects Analysis (FMEA) with Risk Priority Number (RPN) calculations from retrospective Root Cause Analysis (RCA / RCA2). Additionally, candidates must interpret core analytical tools: Ishikawa (fishbone) diagrams, Pareto charts (80/20 rule), run charts, and Statistical Process Control (SPC) charts.

---

Foundations of Quality Improvement in Case Management

Healthcare delivery is an intricate, highly variable sociotechnical system. Quality improvement in nursing case management is the continuous, data-driven effort to enhance patient health outcomes, improve system efficiency, ensure transition safety, and reduce uncompensated resource consumption. Case managers occupy a unique vantage point spanning the entire continuum of care—from emergency department intake to acute inpatient stabilization, post-acute placement, and community reintegration. Consequently, registered nurse case managers frequently lead or serve as essential clinical subject matter experts on interdisciplinary quality improvement committees.

┌────────────────────────────────────────────────────────────────────────┐
│               HEALTHCARE QUALITY IMPROVEMENT TAXONOMY                  │
├──────────────────┬──────────────────┬──────────────────────────────────┤
│ METHODOLOGY      │ PRIMARY FOCUS    │ CORE OPERATIONAL PHILOSOPHY      │
├──────────────────┼──────────────────┼──────────────────────────────────┤
│ IHI Model / PDSA │ Rapid Learning   │ Three questions + small-scale    │
│                  │ & Testing        │ iterative testing ramps          │
├──────────────────┼──────────────────┼──────────────────────────────────┤
│ Lean Healthcare  │ Waste (Muda)     │ Eliminating non-value-added      │
│                  │ Elimination      │ steps; optimizing flow & time    │
├──────────────────┼──────────────────┼──────────────────────────────────┤
│ Six Sigma        │ Variation        │ DMAIC framework; reducing        │
│                  │ Reduction        │ defects to < 3.4 per million     │
├──────────────────┼──────────────────┼──────────────────────────────────┤
│ Lean Six Sigma   │ Speed + Quality  │ Synergistic fusion: eliminating  │
│                  │                  │ waste while ensuring precision   │
└──────────────────┴──────────────────┴──────────────────────────────────┘

Quality improvement is fundamentally distinct from quality assurance (QA). While traditional QA focuses retrospectively on measuring compliance against static administrative minimum standards and penalizing individual outliers, modern QI operates prospectively and concurrently, focusing on systemic process redesign, continuous measurement, and eliminating unwarranted clinical variation.

---

The IHI Model for Improvement and the PDSA Cycle

Developed by Associates in Process Improvement and popularized by the Institute for Healthcare Improvement (IHI), the Model for Improvement provides a simple, structured framework for accelerating clinical and operational enhancements.

The Three Fundamental Questions

Prior to implementing any process change, the interdisciplinary case management team must achieve consensus on three foundational questions:

1. What are we trying to accomplish? (The Aim Statement):

   • The aim statement must be explicit, measurable, time-specific, and define the specific target population. It answers how much, by when, and for whom. Vague statements such as "improve post-discharge follow-up" are unacceptable.
   • Exam-Grade Example: "Increase the percentage of high-risk heart failure patients receiving a multidisciplinary bedside medication reconciliation and teach-back session prior to discharge on Unit 3E from 42% to 85% by November 30, 2026."

2. How will we know that a change is an improvement? (The Measurement System):

   • Establishing a robust, balanced family of measures prevents teams from mistaking activity for progress. QI science defines three interrelated measurement classes:
     • Outcome Measures: Reflect the ultimate clinical, financial, or operational impact on the patient or healthcare organization (e.g., 30-day all-cause readmission rate, post-acute emergency department revisits, average length of stay [ALOS]).
     • Process Measures: Quantify whether specific evidence-based clinical interventions or process steps were executed as designed (e.g., percentage of post-discharge outreach phone calls completed within 48 hours; percentage of transition packets transmitted to receiving skilled nursing facilities within 2 hours of discharge order).
     • Balancing Measures: Monitor whether improvements in one part of the healthcare system inadvertently cause dysfunction, delays, or clinical harm in another area (e.g., tracking emergency department return visits within 72 hours and patient dissatisfaction scores to verify that accelerating acute inpatient discharge throughput did not discharge patients prematurely).

3. What change can we make that will result in improvement? (Change Concepts):

   • The team identifies evidence-based concepts, clinical practice guidelines, technological innovations, or operational reorganizations (e.g., establishing a dedicated "meds-to-beds" concierge pharmacy delivery service, creating an electronic automated prior authorization tracking dashboard).

The Plan-Do-Study-Act (PDSA) Cycle

Once the three questions are defined, the team tests change concepts using rapid-cycle Plan-Do-Study-Act (PDSA) iterations (originally derived from Walter Shewhart's cycle and refined by W. Edwards Deming as the Deming Wheel or PDCA cycle).

               ┌───────────────────────────────┐
               │             PLAN              │
               │ • State test objective        │
               │ • Formulate explicit hypothesis│
               │ • Define who, what, when, where│
               │ • Establish data plan         │
               └───────────────┬───────────────┘
                               │
       ┌───────────────────────┴───────────────────────┐
       ▼                                               ▼
┌──────────────┐                               ┌──────────────┐
│     ACT      │                               │      DO      │
│ • Adopt      │    PDSA RAPID-CYCLE TESTING   │ • Execute    │
│ • Adapt      │        (RAMP CONCEPT)         │   small test │
│ • Abandon    │                               │ • Document   │
└──────────────┘                               │   problems   │
       ▲                                       └──────┬───────┘
       │                                               │
       └───────────────────────┬───────────────────────┘
                               │
               ┌───────────────┴───────────────┐
               │             STUDY             │
               │ • Analyze collected data      │
               │ • Compare data to predictions │
               │ • Synthesize key learnings    │
               └───────────────────────────────┘

The Four Iterative Phases

• Plan: Formulate the test objective, state explicit written predictions of what will happen, and outline the operational plan: who will carry out the test, what will be done, where it will take place, and when. Establish a data collection method.
• Do: Carry out the test on a small, manageable scale (e.g., testing a revised transitional care intake form with one case manager, for two patients, during one afternoon shift). Document unanticipated hurdles, software glitches, and clinician observations in real time.
• Study: Analyze the quantitative metrics and qualitative feedback. Directly compare the observed findings against the written predictions made during the Plan phase. Reflect on whether the test verified or refuted the team's working hypothesis.
• Act: Based on the empirical findings, determine the next course of action among three pathways:
  1. Adopt: The test succeeded completely without negative unintended consequences; standardize the change across the unit or scale up testing across broader patient cohorts.
  2. Adapt: The change concept demonstrated merit but revealed operational friction or design flaws; modify the intervention, adjust the workflow, and immediately launch a new PDSA cycle.
  3. Abandon: The test failed, caused unacceptable staff burden, or degraded clinical workflow; discard the concept and brainstorm alternative change strategies.

Sequential PDSA Ramps

A fundamental tenet of QI science is that sustainable improvement requires sequential PDSA ramps. A team does not launch an untested clinical protocol across an entire hospital system on Day 1. Instead, tests expand incrementally: Cycle 1 tests on 1 patient with 1 nurse; Cycle 2 tests on 5 patients with 2 nurses; Cycle 3 tests on a full nursing unit across all shifts; Cycle 4 tests across the weekend; and Cycle 5 implements hospital-wide policy standardization.

---

Lean Healthcare Methodology and Waste (Muda)

Rooted in the Toyota Production System developed by Taiichi Ohno, Lean methodology focuses on maximizing patient-defined value while relentlessly identifying and eliminating non-value-added activities, known as waste (muda).

In healthcare case management, value is defined from the perspective of the patient and family: any clinical, educational, or transitional coordination service that directly advances the patient toward their recovery goals, functional independence, and a safe, timely transition to the community. Any activity that consumes time, labor, or financial resources without adding value is waste.

The Eight Types of Waste (Muda) in Case Management (DOWNTIME Taxonomy)

Value Stream Mapping (VSM)

Value Stream Mapping (VSM) is a foundational Lean diagnostic tool that visually charts every sequential step, delay, handoff, and information flow required to guide a patient from admission through discharge.

┌────────────────────────────────────────────────────────────────────────┐
│                     VALUE STREAM MAPPING (VSM) FLOW                    │
└───────────────────┬────────────────────────────────┬───────────────────┘
                    │                                │
┌───────────────────▼──────────────┐ ┌───────────────▼───────────────────┐
│     VALUE-ADDED STEPS (VA)       │ │   NON-VALUE-ADDED STEPS (NVA)     │
│ (Directly Advances Patient Care) │ │     (Waste / Bottlenecks / Muda)  │
├──────────────────────────────────┤ ├───────────────────────────────────┤
│ • Comprehensive clinical intake  │ │ • Waiting 36 hours for payer auth │
│ • Bedside teach-back education   │ │ • Re-faxing lost clinical packets │
│ • Multidisciplinary rounds       │ │ • Walking between wings for sigs  │
│ • Medication reconciliation      │ │ • Reworking denied referrals      │
└──────────────────────────────────┘ └───────────────────────────────────┘

In a VSM event, the team measures two key temporal parameters:

• Process Time (Touch Time / Value-Added Time): The actual time spent actively providing clinical assessment, education, or care coordination.
• Lead Time (Total Elapsed Cycle Time): The total elapsed calendar time from the initiation of the process to its completion, including all waiting, queuing, and administrative delays.
• Process Cycle Efficiency (PCE): Calculated as PCE (%) = (Value-Added Time / Total Lead Time) × 100. In traditional fragmented hospital discharge workflows, PCE is frequently under 10%, indicating that over 90% of the patient's transition timeline is consumed by waiting and waste.

The VSM process charts the Current State Map, identifies root causes of stagnation, and designs an optimized Future State Map that eliminates non-value-added bottlenecks.

The 5S Workplace Organization System

The 5S methodology standardizes physical and digital work environments to minimize motion, stress, and cognitive errors:

1. Sort (Seiri): Separate necessary tools and documents from unnecessary clutter; discard outdated paper forms and archive obsolete digital files.
2. Set in Order (Seiton): Organize essential resources logically with clear visual labeling so that any team member can locate intake sheets, telephone directories, or DME forms within 30 seconds.
3. Shine (Seiso): Clean and inspect the physical workspace, ensuring computers, printers, and workstations are operational and clutter-free.
4. Standardize (Seiketsu): Establish uniform visual controls, color-coded files, and standardized EHR templates across the entire department.
5. Sustain (Shitsuke): Perform regular departmental audits and maintain operational discipline so that standards do not degrade over time.

---

Six Sigma Methodology and the DMAIC Framework

Pioneered by Motorola in the 1980s and widely integrated into healthcare operations, Six Sigma is a disciplined, data-driven methodology focused on reducing process variation and eliminating defects. Statistically, achieving Six Sigma quality equates to fewer than 3.4 defects per million opportunities (DPMO), representing a 99.99966% defect-free process.

While Lean focuses on improving velocity and eliminating waste, Six Sigma focuses on improving precision, consistency, and statistical reliability. Together, Lean Six Sigma provides healthcare organizations with the tools to achieve both rapid operational throughput and zero preventable harm.

The DMAIC Lifecycle

Six Sigma executes quality improvement projects through the structured, five-phase DMAIC framework:

┌─────────┐      ┌─────────┐      ┌─────────┐      ┌─────────┐      ┌─────────┐
│ DEFINE  │ ───> │ MEASURE │ ───> │ ANALYZE │ ───> │ IMPROVE │ ───> │ CONTROL │
└─────────┘      └─────────┘      └─────────┘      └─────────┘      └─────────┘
 • Project        • Baseline data  • Isolate root   • Pilot targeted • Standardize
   charter        • Process maps    causes           solutions        procedures
 • Identify CTQ   • Defect rates   • Verify with    • Eliminate      • SPC control
   parameters     • Sampling plan   data analytics   variation        charts & audits

1. Define:

   • Articulate the clinical problem, outline the business case, establish the project scope, and construct a formal Project Charter with executive sponsorship.
   • Identify the Voice of the Customer (VOC)—encompassing both patients and receiving post-acute providers—and translate VOC feedback into quantifiable Critical to Quality (CTQ) parameters (e.g., "Post-acute discharge documentation must be transmitted to receiving skilled nursing facilities within 60 minutes of the physician discharge order").

2. Measure:

   • Establish operational definitions for what constitutes a "defect" (e.g., any transfer packet transmitted >60 minutes post-order, or any packet missing the active medication administration record).
   • Construct a detailed data collection plan, validate measurement system reliability, and gather baseline empirical data over 30 to 90 days.
   • Calculate the baseline process capability, defect rate (DPMO), and baseline Sigma level.

3. Analyze:

   • Scrutinize the collected data using statistical and process visualization tools to identify the fundamental root causes of process defects and variation.
   • Differentiate process bottlenecks from statistical noise, utilizing scatter plots, regression analysis, and stratification by clinical unit, shift, or payer type to isolate why performance varies.

4. Improve:

   • Formulate innovative, evidence-based solutions directly aimed at eliminating the verified root causes of variation.
   • Pilot targeted interventions using small-scale rapid testing to evaluate efficacy.
   • Implement mistake-proofing (poka-yoke) mechanisms (e.g., electronic hard stops in the EHR that prevent discharge closure if the after-visit summary lacks medication reconciliation verification).

5. Control:

   • Institutionalize the improvements to ensure gains are sustained longitudinally.
   • Develop standardized clinical operating procedures (SOPs), educate all rotating staff, and establish visual monitoring dashboards.
   • Deploy Statistical Process Control (SPC) charts to continuously track performance and alert leadership immediately if the process drifts out of statistical control.

---

Prospective vs. Retrospective Risk Assessment: RCA vs. FMEA

A critical competence evaluated on the CMGT-BC exam is the distinction between retrospective investigations (Root Cause Analysis) and proactive risk assessments (Failure Mode and Effects Analysis).

Root Cause Analysis (RCA and RCA2)

When a serious clinical breakdown or sentinel event occurs (e.g., a patient discharged without home oxygen therapy who suffers fatal hypoxic arrest within 6 hours), an interdisciplinary team conducts a Root Cause Analysis (RCA).

Endorsed by the National Patient Safety Foundation (NPSF) and IHI, modern RCA2 (Root Cause Analysis and Action: Improving Safety after Harm) emphasizes that discovering causes is worthless unless paired with strong, sustainable corrective actions.

The Hierarchy of Action Strength in RCA2

Corrective actions are categorized into three tiers based on their systemic reliability:

1. Strong Actions (Architectural & Systemic Redesign):
   • Eliminate reliance on human memory, alertness, or vigilance.
   • Examples: Physical interlocks (e.g., ENFit enteral connectors that physically cannot connect to intravenous lines); automated electronic EHR hard stops that lock discharge dispatch until durable medical equipment delivery confirmation is received; removing high-risk concentrated electrolyte solutions from floor stock.
2. Intermediate Actions (Cognitive Supports & Standardization):
   • Reduce cognitive load and increase uniformity, but still require human active participation.
   • Examples: Standardized discharge checklists; standardized handoff mnemonics (SBAR, I-PASS); automated EHR clinical decision support alerts; dual independent verification.
3. Weak Actions (Administrative Exhortations & Retraining):
   • Rely entirely on human memory, vigilance, and behavioral compliance under high-stress conditions.
   • Examples: Distributing an educational email memo; revising a written hospital policy; holding a mandatory lecture; posting warning posters; instructing staff to "pay closer attention."

The ANCC Exam Gold Standard: On the CMGT-BC examination, when evaluating proposed RCA corrective action plans, never choose a weak action (retraining, policy revision, educational memo) if a strong action (forcing function, architectural automation, physical interlock) is available.

Failure Mode and Effects Analysis (FMEA)

Failure Mode and Effects Analysis (FMEA) is an engineering methodology adapted for healthcare to systematically evaluate a process prospectively to identify where and how it might fail, and to assess the relative impact of different failures.

The FMEA Step-by-Step Workflow

1. Select a high-risk clinical process (e.g., implementing an automated electronic referral system for post-acute home infusion therapy) and assemble an interdisciplinary team (case manager, bedside nurse, pharmacist, informatics specialist, risk manager).
2. Flowchart the proposed process in granular detail.
3. Brainstorm potential Failure Modes for each process step (What could go wrong?).
4. Identify potential Failure Effects (What would happen to the patient if this failure occurred?).
5. Identify potential Root Causes of each failure mode.

Calculating the Risk Priority Number (RPN)

The team evaluates each failure mode across three dimensions, scoring each on a 1 to 10 scale:

Risk Priority Number (RPN) = Severity (S) × Occurrence (O) × Detection (D)

┌────────────────────────────────────────────────────────────────────────┐
│                     RPN RATING SCALES (1 TO 10)                        │
├─────────────────┬──────────────────────────────────────────────────────┤
│ Severity (S)    │ Seriousness of the clinical outcome if failure occurs│
│                 │ (1 = Negligible / No harm; 10 = Catastrophic / Death)│
├─────────────────┼──────────────────────────────────────────────────────┤
│ Occurrence (O)  │ Likelihood / Frequency that failure mode will happen │
│                 │ (1 = Extremely remote / Rare; 10 = Inevitable / High)│
├─────────────────┼──────────────────────────────────────────────────────┤
│ Detection (D)   │ Likelihood failure will NOT be detected before harm  │
│                 │ (1 = Certain detection; 10 = Undetectable / Hidden)  │
└─────────────────┴──────────────────────────────────────────────────────┘

• RPN Interpretation: RPN scores range from 1 to 1,000. The failure modes with the highest RPNs are prioritized for immediate redesign.
• The Critical Severity Override Rule: In healthcare FMEA, any failure mode with a Severity score of 9 or 10 (indicating severe harm or death) must be redesigned with robust preventive controls, regardless of how low the calculated Occurrence or Detection scores may be.

---

Core Quality Improvement Diagnostic Tools

Nurse case managers must possess analytical fluency with core visual and statistical diagnostic tools to lead care coordination quality task forces.

1. Ishikawa (Fishbone) Cause-and-Effect Diagram

Developed by Kaoru Ishikawa, the fishbone diagram is a structured graphical brainstorming tool used to categorize and display all potential root causes of a specific quality problem or clinical defect. The problem statement (the effect) is placed at the "head" of the fish, and major causal categories form the "spine" and "ribs."

In healthcare delivery, teams utilize the 6Ms framework adapted for clinical environments:

• Manpower / Personnel: Staffing ratios, clinical training, fatigue, reliance on rotating agency staff, lack of post-acute resource awareness.
• Methods / Processes: Ambiguous discharge guidelines, lack of standardized weekend handoffs, uncoordinated multidisciplinary rounding.
• Machines / Technology: EHR software freezes, incompatible post-acute referral portals, malfunctioning fax lines, lack of mobile devices.
• Materials / Supplies: Shortages of specialized wound care dressings, unverified durable medical equipment delivery, missing discharge medication prescriptions.
• Measurement / Metrics: Conflicting definitions of avoidable delay days, lack of real-time length of stay dashboard tracking.
• Milieu / Environment: High noise levels, chaotic emergency department boarding, physical geographic dispersion of inpatient units.

2. The 5 Whys Interrogation Technique

An iterative interrogative technique designed to drill down through superficial symptoms of human error to uncover latent systemic design flaws. By asking "Why?" successive times (typically five), the team moves beyond individual blame to identify actionable organizational root causes.

3. Pareto Charts and the 80/20 Rule

Named after economist Vilfredo Pareto, a Pareto chart is a dual-axis graph combining a descending bar chart with a cumulative percentage line. It visually demonstrates the Pareto Principle (the 80/20 rule): approximately 80% of process problems or transition delays arise from roughly 20% of root causes (termed the "vital few" versus the "useful many").

Frequency of Avoidable Days
   ▲
100│ ██                                                  100% ── Cumulative %
 80│ ██      ██                                           80%  ▲ (80% Cutoff)
 60│ ██      ██                                           60%  │
 40│ ██      ██      ██                                   40%  │
 20│ ██      ██      ██      ██      ██                   20%  │
  0└──┴───────┴───────┴───────┴───────┴────────────────────0%  │
     Payer   SNF Bed Dialysis Transp  Other                    │
     Auth    Shortage Vendor  Delay   Causes                   │
     ◄────── Vital Few ──────► ◄── Useful Many ──►             │

Case Management Application: A case management department tracking avoidable delay days might identify twelve distinct reasons for delayed discharge. A Pareto chart reveals that two causes—payer prior authorization turnaround and post-acute skilled nursing bariatric bed shortages—account for 82% of all avoidable inpatient days. By focusing improvement resources on these "vital few" drivers, the department achieves maximum operational impact.

4. Run Charts: Detecting Non-Random Variation

A run chart is a visual line graph plotting clinical or operational data in chronological order over time, with a mathematically determined median line serving as the centerline. Run charts allow teams to evaluate whether changes are resulting in genuine improvement without complex statistical computations.

To determine whether variation is non-random (indicating an authentic process change rather than random chance), teams apply four standard probability-based run chart rules:

1. Shift: Six (6) or more consecutive data points falling entirely above or entirely below the median (data points falling directly on the median are ignored).
2. Trend: Five (5) or more consecutive data points continuously increasing or continuously decreasing (ties between consecutive points do not count).
3. Runs Count: A "run" is a succession of consecutive data points on one side of the median. If the total number of runs across the chart is statistically too few or too many (based on published run table thresholds for sample size n), non-random variation is present.
4. Astronomical Data Point: A blatant, obvious outlier that is dramatically different from all other data points on the chart.

5. Control Charts (Statistical Process Control / SPC)

Developed by Walter Shewhart, Statistical Process Control (SPC) control charts elevate run charts to rigorous statistical tools. A control chart plots chronological data around a central line representing the process mean (average), flanked by an Upper Control Limit (UCL) and a Lower Control Limit (LCL), mathematically calculated at three standard deviations (±3 sigma) from the mean:

• UCL = Process Mean + 3 Sigma
• LCL = Process Mean - 3 Sigma

Inpatient Length of Stay (Days)
   ▲
 8 │────────────────────────────────────────── Upper Control Limit (UCL = Mean + 3 Sigma)
 7 │          *                               
 6 │    *   *   *   *                         
 5 │────────────────*──────────────────────── Process Mean (Centerline)
 4 │  *               *   *                   
 3 │                        *   *   *         
 2 │────────────────────────────────────────── Lower Control Limit (LCL = Mean - 3 Sigma)
   └─────────────────────────────────────────► Time (Consecutive Discharge Weeks)

Differentiating Common Cause vs. Special Cause Variation

The fundamental purpose of an SPC chart is to distinguish between two types of process variation:

• Common Cause Variation (Inherent System Noise):
  • Random variation that is naturally inherent in the system's design, technology, and operating environment.
  • Data points fluctuate unpredictably within the UCL and LCL boundaries.
  • Management Rule: A process exhibiting only common cause variation is stable and predictable. To improve performance, leadership must redesign the entire underlying system. Attempting to react to individual data points within control limits is known as tampering, which actually increases process variation and destabilizes performance.
• Special Cause Variation (Extrinsic, Assignable Causes):
  • Non-random variation caused by specific, identifiable, external factors outside the normal system design (e.g., an electronic referral server crash, a sudden blizzard closing post-acute transit, an acute staffing crisis).
  • Detected when a data point breaches the UCL or LCL, or when specific non-random patterns appear (such as 8 consecutive points on one side of the mean).
  • Management Rule: Demands immediate investigation to identify, isolate, and remove the assignable root cause (if detrimental) or standardize it (if beneficial).

---

Clinical Application Scenario: Deploying Lean Six Sigma in Inpatient Transitions

Clinical Context

A 450-bed urban teaching hospital experiences an average length of stay (ALOS) for heart failure patients of 5.8 days against a CMS Geometric Mean Length of Stay (GMLOS) benchmark of 3.4 days, accompanied by a 30-day all-cause readmission rate of 23.8%. The Chief Medical Officer tasks the Department of Nursing Case Management with leading a Lean Six Sigma DMAIC project.

Project Execution

1. Define: The team constructs a project charter aiming to reduce heart failure ALOS from 5.8 days to 3.6 days and 30-day readmissions to <17.0% within six months. The Voice of the Customer survey reveals patients are confused by conflicting discharge medication instructions and post-acute facilities report missing clinical handoffs.
2. Measure: The team establishes an operational data plan. Value Stream Mapping reveals that total patient stay (Lead Time = 139.2 hours) contains only 11.5 hours of active clinical care (Touch Time), yielding a dismal Process Cycle Efficiency of 8.2%. The remaining 127.7 hours represent non-value-added waste (waiting for lab results, waiting for cardiology consultations, waiting for prior authorization).
3. Analyze: Constructing an Ishikawa fishbone diagram across the 6Ms identifies multiple failure modes. The team logs all avoidable delay days and plots them on a Pareto chart. The Pareto analysis demonstrates that 84% of avoidable days stem from two factors: delays in obtaining commercial insurance prior authorization for home health physical therapy, and patients lacking transportation to attend follow-up cardiology visits.
4. Improve:
   • Countermeasure 1: The team partners with clinical informatics to build an automated electronic prior authorization queue in the EHR, submitting clinical packets 48 hours prior to anticipated discharge.
   • Countermeasure 2: The case management department partners with an outpatient clinic to establish a bedside concierge "meds-to-beds" delivery program paired with dedicated ride-share transit vouchers for all follow-up appointments scheduled within 7 days of discharge.
   • Testing: The team utilizes a rapid-cycle PDSA ramp, testing the meds-to-beds protocol on 2 patients on Monday (PDSA 1), adapting the medication delivery workflow, testing on 8 patients on Wednesday (PDSA 2), and scaling across the entire medical unit by Friday (PDSA 3).
5. Control: The team standardizes the workflow into departmental SOPs and tracks weekly ALOS and 30-day readmissions on an SPC control chart. When a point shifts downward below the lower control limit, the team confirms sustainable special cause improvement rather than random noise.

---

Common Exam Traps & High-Yield Takeaways

• Exam Trap 1: Confusing FMEA with RCA. Remember: FMEA is prospective (conducted before a new workflow or technology is launched to prevent harm); RCA is retrospective (conducted after an adverse event or sentinel event has occurred).
• Exam Trap 2: Selecting Weak Actions in RCA Corrections. When presented with RCA corrective options, never select revising policies, sending staff reminder emails, or scheduling mandatory educational inservices. Always choose strong actions featuring forcing functions, architectural barriers, or automated EHR hard stops.
• Exam Trap 3: Tampering with Common Cause Variation. When an SPC control chart shows data fluctuating normally between the upper and lower control limits, reacting to a single high point by reprimanding staff is known as tampering. Common cause variation requires fundamental systemic redesign, not ad-hoc punitive reactions.
• Exam Trap 4: Rolling Out Organization-Wide Changes Immediately. In PDSA questions, correct answers start with small-scale tests (one nurse, one patient, one shift) before expanding. Immediate enterprise-wide rollouts violate core quality improvement principles.