Section 4.2: Quality Improvement & Systems-Based Practice

Plan-Do-Study-Act (PDSA) Cycles

The Plan-Do-Study-Act (PDSA) cycle is an iterative, four-stage problem-solving model used for continuous quality improvement (QI) in healthcare. It allows organizations to test changes on a small scale, observe the results, and refine the intervention before wide-scale implementation. This rapid-cycle testing minimizes risk and resource expenditure.

1. Plan: In this phase, the QI team identifies a specific problem, defines the objective of the intervention, formulates a hypothesis (predictions), and designs the test of change. The plan must detail who will implement the change, what will be done, where, and when, as well as how data will be collected to measure success.
2. Do: The team carries out the planned change on a small test scale (e.g., testing a new protocol on a single ward for one shift). During this phase, staff document observations, unexpected problems, and collect baseline qualitative and quantitative data.
3. Study: The team analyzes the collected data and compares the outcomes against the predictions made in the planning phase. Lessons learned, success rates, and any unintended consequences are summarized.
4. Act: Based on the findings from the study phase, the team decides on the next step. They can adopt the change (if it was highly successful, scaling it up to other departments), adapt the change (modify the protocol based on feedback and run a new PDSA cycle), or abandon the change (if the intervention failed or caused unexpected harm, starting over with a different strategy).

Lean and Six Sigma Principles

Lean and Six Sigma are two distinct but highly complementary systems-based methodologies utilized to optimize healthcare operations and improve patient safety:

• Lean Methodology: Originally derived from manufacturing (Toyota Production System), Lean focuses on the elimination of "waste" (muda)—defined as any activity that consumes resources but adds no value to the patient. The goal is to maximize efficiency and value. Lean identifies seven types of waste: transport, inventory, motion, waiting, over-processing, over-production, and defects. In healthcare, waste includes long patient wait times in the emergency department, redundant paperwork, searching for missing equipment, and unnecessary transportation of patients between departments. Lean tools include value stream mapping (visualizing every step of a process to identify waste) and the 5S system (Sort, Straighten, Shine, Standardize, Sustain) for workplace organization.
• Six Sigma: Developed by Motorola, Six Sigma is a data-driven methodology that focuses on reducing variation and minimizing defects in a process. A defect is defined as any outcome outside of customer expectations (e.g., a medication error or surgical infection). Six Sigma aims for near-perfection: a statistical target of less than 3.4 defects per million opportunities. It follows the DMAIC framework: Define the problem, Measure key aspects of the current process, Analyze the data to find root causes of defects, Improve the process by eliminating these causes, and Control the future state process to prevent deviations.

Handoff Protocols and the I-PASS Framework

Communication failure during patient handoffs is one of the most common causes of preventable adverse events in healthcare. Handoffs occur during shift changes, when patients are transferred between units (e.g., emergency department to intensive care unit), or when patients are transferred to different facilities. To mitigate this risk, healthcare organizations require standardized handoff protocols.

The I-PASS framework is an evidence-based communication tool that has been shown to reduce medical errors and improve patient safety:

• I - Illness Severity: Categorizes the patient as "stable," "watcher" (at risk for deterioration), or "unstable."
• P - Patient Summary: A concise narrative of the patient's admission diagnosis, hospital course, current treatment plan, and active issues.
• A - Action List: A specific list of "to-do" items that the receiving team needs to perform (e.g., check lab results, follow up on imaging), marked with clear priority and ownership.
• S - Situation Awareness & Contingency Planning: Detailed instructions on what could go wrong (e.g., "if the patient becomes hypotensive, give a 500 mL fluid bolus and call the fellow") to prevent rescue delays.
• S - Synthesis by Receiver: The receiving provider summarizes what they heard, asks clarifying questions, and verbally confirms key actions and contingency plans, ensuring closed-loop communication.

Medication Reconciliation

Medication reconciliation is the formal, structured process of creating the most accurate list possible of all medications a patient is taking—including drug name, dosage, frequency, and route—and comparing it against admission, transfer, and discharge orders. This process is essential at all transition points of care to prevent medication discrepancies, which are a major source of adverse drug events (ADEs).

The process consists of four key steps:

1. Verification: Compiling a comprehensive list of the patient's current medications using multiple sources (patient interview, pill bottles, pharmacy records, prior EHR data).
2. Clarification: Ensuring that the doses, frequencies, and indications are correct and active.
3. Reconciliation: Comparing the verified list against new clinical orders, identifying discrepancies (e.g., omitted drugs, duplicate therapies, incorrect dosages), and making clinical decisions to resolve them.
4. Transmission: Communicating the updated, reconciled medication list to the patient, their family, and subsequent healthcare providers (such as the outpatient primary care physician) at the time of discharge.

Failure Mode and Effects Analysis (FMEA)

While Root Cause Analysis is retrospective, Failure Mode and Effects Analysis (FMEA) is a systematic, prospective method used to identify potential failure points in a process before they occur. The team maps out every step of a proposed process (e.g., introducing a new electronic health record module), identifies potential failure modes (what could go wrong), determines the effects of those failures, and calculates a Risk Priority Number (RPN) based on the severity, frequency of occurrence, and probability of detection. Process steps with the highest RPNs are targeted for immediate redesign and the addition of safety safeguards before the system is launched, allowing institutions to proactively design safety into their clinical workflows.