| Literature DB >> 24025320 |
Michael J Taylor1, Chris McNicholas, Chris Nicolay, Ara Darzi, Derek Bell, Julie E Reed.
Abstract
BACKGROUND: Plan-do-study-act (PDSA) cycles provide a structure for iterative testing of changes to improve quality of systems. The method is widely accepted in healthcare improvement; however there is little overarching evaluation of how the method is applied. This paper proposes a theoretical framework for assessing the quality of application of PDSA cycles and explores the consistency with which the method has been applied in peer-reviewed literature against this framework.Entities:
Keywords: Implementation science; PDSA; Quality improvement; Quality improvement methodologies
Mesh:
Year: 2013 PMID: 24025320 PMCID: PMC3963536 DOI: 10.1136/bmjqs-2013-001862
Source DB: PubMed Journal: BMJ Qual Saf ISSN: 2044-5415 Impact factor: 7.035
Figure 1The Model for Improvement; FOCUS.
Description of the plan–do–study–act (PDSA) cycle method according to developers and commentators
| Deming (1986) | Langley (1996) | Speroff and O'Connor (2004) | |
|---|---|---|---|
| Plan | Plan a change or test aimed at improvement |
Identify objective Identify questions and predictions Plan to carry out the cycle (who, when, where, when) | Formation of a hypothesis for improvement |
| Do | Carry out the change or test (preferably on a small scale) |
Execute the plan Document problems and unexpected observations Begin data analysis | Conduct study protocol with collection of data |
| Study | Examine the results. What did we learn? What went wrong? |
Complete the data analysis Compare data to predictions Summarise what was learnt | Analysis and interpretation of the results |
| Act | Adopt the change, abandon it or run through cycle again |
What changes are to be made? What will the next cycle entail? | Iteration for what to do next |
Theoretical framework based on key features of the plan–do–study–act (PDSA) cycle method
| Feature of PDSA | Description of feature | How this was measured |
|---|---|---|
| Iterative cycles | To achieve an iterative approach, multiple PDSA cycles must occur. Lessons learned from one cycle link and inform cycles that follow. Depending on the knowledge gained from a PDSA cycle, the following cycle may seek to modify, expand, adopt or abandon a change that was tested |
Were multiple cycles used? Were multiple cycles linked to one another (ie, does the ‘act’ stage of one cycle inform the ‘plan’ stage of the cycle that follows)? When isolated cycles were used were future actions postulated in the ‘act’ stage? |
| Prediction-based test of change | A prediction of the outcome of a change is developed in the ‘plan’ stage of a cycle. This change is then tested and examined by comparison of results with the prediction |
Was a change tested? Was an explicit prediction articulated? |
| Small-scale testing | As certainty of success of a test of change is not guaranteed, PDSAs start small in scale and build in scale as confidence grows. This allows the change to be adapted according to feedback, minimises risk and facilitates rapid change and learning |
Sample size per cycle? Temporal duration of cycles? Number of changes tested per cycle? Did sequential cycles increase scale of testing? |
| Use of data over time | Data over time increases understanding regarding the variation inherent in a complex healthcare system. Use of data over time is necessary to understand the impact of a change on the process or outcome of interest |
Was data collected over time? Were statistics used to test the effect of changes and/or understand variation? |
| Documentation | Documentation is crucial to support local learning and transferability of learning to other settings |
How thoroughly was the application of the PDSA method detailed in the reports? Was each stage of the PDSA cycles documented? |
Figure 2PRISMA diagram.
Figure 3Iterative nature of cycles for all articles and split by plan–do–check–act and plan–do–study–act terminology.