Study guide
3.4 QI Models: Model for Improvement and PDSA
Certified Professional in Patient Safety Exam
Track your progress as you read
Finished sections get a check mark.
1 1. Patient Safety Risks & Solutions (Part A)
1.1 Risk Identification and Hazard Reporting 1.2 Reactive Analysis: Root Cause Analysis 1.3 Proactive Analysis: Failure Modes and Effects Analysis 1.4 Evidence-Based Safety Solutions 1.5 Structured Communication and Team Training 1.6 Healthcare Technology Safety and Risk 1.7 Second Victim Support and Workplace Violence
2 Chapter 2: Systems Thinking & Design / Human Factors
2.1 Systems Theory and Complex Adaptive Systems 2.2 Swiss Cheese Model and Error Classification 2.3 Just Culture and Accountability Framework 2.4 Normalized Deviance and Drift 2.5 High Reliability Organizations and Resilience 2.6 Human Factors Engineering and Ergonomics 2.7 The SEIPS Model and Interactions
3 Chapter 3: Measuring & Improving Performance
3.1 Patient Safety Data Sources 3.2 Statistical Process Control and Run Charts 3.3 Control Chart Types and Uses 3.4 QI Models: Model for Improvement and PDSA 3.5 Patient Safety Metrics and Measurement 3.6 QI Project Management and Facilitation 3.7 Reporting and Communicating Safety Metrics
4 Chapter 4: Culture
4.1 Assessing Safety Culture 4.2 Cultivating a Culture of Safety 4.3 Disclosure of Adverse Events and Errors 4.4 Patient and Family Engagement 4.5 Fostering Collaboration and Psychological Safety
5 Chapter 5: Leadership
5.1 Leadership Commitment and Aligning Strategy 5.2 Leadership WalkRounds and Executive Sponsorship 5.3 Accountability Frameworks and Transparency 5.4 Storytelling and Patient-Centered Narratives 5.5 Regulatory Compliance and Patient Safety Standards
6 Chapter 6: Recognizing & Preventing Specific Patient Harms
6.1 Diagnostic Error and Patient Deterioration 6.2 Medication Safety and High-Alert Medications 6.3 Procedural, Surgical, and Environmental Hazards 6.4 Healthcare-Associated Infections and Conditions 6.5 Health Equity and Sociodemographic Risk 6.6 Care Transitions, Resource Barriers, and Emergency Preparedness
3.4 QI Models: Model for Improvement and PDSA
Key Takeaways Explain This Topic AI
The Model for Improvement asks three fundamental questions before testing changes: (1) What are we trying to accomplish? (2) How will we know that a change is an improvement? (3) What change can we make that will result in improvement?
A PDSA (Plan-Do-Study-Act) cycle is a structured, iterative method for testing a change on a small scale (e.g., one patient, one nurse, one day) to minimize risk and build stakeholder buy-in.
Plan involves defining the objective and predicting outcomes; Do is the small-scale test; Study is the analysis of data against predictions; Act determines whether to adopt, adapt, or abandon the change.
Successive PDSA cycles are designed to build cumulative confidence over time, moving from small, low-risk tests to larger implementation phases.
Last updated: July 2026
3.4 QI Models: Model for Improvement and PDSA
To effectively translate patient safety data into clinical practice changes, healthcare organizations rely on structured quality improvement (QI) frameworks. The most widely adopted framework in patient safety is the Model for Improvement , developed by the Associates in Process Improvement (API) and heavily promoted by the Institute for Healthcare Improvement (IHI). This model consists of two parts: three core questions that guide the design of an improvement project, and the Plan-Do-Study-Act (PDSA) cycle for testing changes on a small, iterative scale.
The Three Questions of the Model for Improvement
Before launching a quality improvement effort, teams must answer three fundamental questions to establish clear goals, measures, and change strategies:
Question 1: What are we trying to accomplish?
This question requires the team to write a clear, specific, and measurable Aim Statement . An effective aim statement must define the target population, the specific goal, the amount of improvement desired, and a realistic timeframe. A typical aim statement might read: "We will reduce hospital-acquired catheter-associated urinary tract infections (CAUTIs) in the intensive care unit by 40% by December 31, 2026."
Question 2: How will we know that a change is an improvement?
To answer this question, the team must identify a balanced family of measures to monitor process changes and ensure no unintended negative consequences occur. This family includes:
Outcome Measures : Track the high-level goals of the project (e.g., the rate of CAUTIs per 1,000 device-days).
Process Measures : Monitor whether the specific components of the intervention are being executed as planned (e.g., the percentage of staff adhering to the daily catheter-maintenance checklist).
Balancing Measures : Assess whether changes in one part of the system are causing problems elsewhere (e.g., monitoring whether the new catheter checklist causes delays in emergency department throughput).
Question 3: What change can we make that will result in improvement?
This question focuses on developing actionable change ideas . Quality teams source change ideas from clinical guidelines, human factors engineering principles, benchmarking other successful organizations, and frontline staff recommendations. Ideas might include introducing an electronic health record hard stop to prompt catheter removal, or implementing a standardized nurse-led review process.
The PDSA Cycle: Iterative Testing on a Small Scale
Once the team has defined their aim, measures, and change ideas, they use the PDSA cycle to test their ideas. The key principle of PDSA is testing on a small scale (e.g., testing a new tool with 1 patient, 1 nurse, on 1 shift) to minimize risk, reduce resistance from staff, and learn quickly from failures. +-------------------+
- | PLAN |
- | Define Objective |
- | Predict Outcomes |
- +---------+---------+
- |
- v
- +-------------------+ +-------------------+
- | ACT | | DO |
- | Adopt, Adapt, or | | Run Small Pilot |
- | Abandon Change | | Observe & Record |
- +---------^---------+ +---------+---------+
- | |
- +-----------------+----------------+
- |
- v
- +---------+---------+
- | STUDY |
- | Analyze Results |
- | Compare to Preds |
- +-------------------+
- 1. Plan
In the Plan phase, the team defines the objective of the specific test, details the steps of the test (who, what, where, when), and plans for data collection. Crucially, the team must document their predictions about what will happen and why. Making predictions forces the team to clarify their assumptions and learn more deeply when actual results differ from expectations.
2. Do
During the Do phase, the team executes the test on a small, controlled scale. Staff carry out the pilot, and the team documents all observations, unexpected problems, and qualitative feedback from the participants.
3. Study
In the Study phase, the team analyzes the data collected during the test. They directly compare the actual results to the predictions documented during the Plan phase. The team summarizes what went well, what failed, and what key lessons were learned.
4. Act
Based on the lessons learned in the Study phase, the team makes one of three decisions:
Adopt : If the test was successful, the team standardizes the change and implements it on a larger scale (e.g., rolling the checklist out to the entire unit).
Adapt : If the test was partially successful but revealed issues, the team modifies the change idea based on feedback and runs a new PDSA cycle (e.g., tweaking the checklist layout and testing it with a different nurse).
Abandon : If the test was a complete failure and did not result in improvement, the team discards the idea and chooses a different change idea to test.
Building Cumulative Confidence through Ramps
Quality improvement is not a single-step event. It requires sequential PDSA cycles, often referred to as a PDSA Ramp . A team starts with very small, low-risk tests. As they learn and adapt the process, they increase the scale of the tests (e.g., moving from 1 patient, to 5 patients, to the entire unit) and test under different environmental conditions (e.g., testing on the night shift, on weekends, or during high-volume periods). This iterative scaling builds cumulative confidence and ensures that the change is robust and sustainable before it is fully implemented across the entire organization.