Plan Do Study Act (PDSA) - YouTube

Channel: MPRO

[10]
CHRISTY: Process improvement is a series of actions taken to make a process more
[14]
efficient, less costly, safer, etc.
[18]
The healthcare reimbursement model is shifting to a pay-for-performance
[21]
type system or a value-based purchasing model
[25]
and in preparation for reimbursing providers and facilities based on quality of care
[30]
that they're providing, the government's requiring providers to
[34]
adopt certified electronic health records and use them in a meaningful way.
[39]
What this means is that providers will be expected to not just
[43]
compile data or information on the patients they care for
[46]
but to actually act on that data and it's here
[49]
that quality improvement comes into play. There are many methods and quality
[54]
improvement being used today.
[55]
Some of most commonly used ones are
[59]
total quality management or TQM continuous quality improvement
[64]
or CQI. Lean. Six
[67]
Sigma and PDSA also known as
[70]
PDCA. The one that seems to be the fastest
[74]
and easiest to teach, as well as utilizes is the
[78]
trial and learn approach to quality improvement that combines three
[81]
fundamental questions with the plan do study act process.
[85]
There three fundamental questions that get asked with the PDSA model.
[90]
1. What is it that's trying to be accomplished?
[93]
2. How can one know a change is actually an improvement?
[98]
3. What changes can be made that will actually result in an improvement?
[104]
There are multiple ways to
[107]
teach process improvement. I generally gravitate towards workshops that are
[111]
are fun and that involve games other games that involve
[115]
assembling paper airplanes and flying them. There games that are
[118]
that involve assembling paper footballs and using them to shoot
[122]
goals and there also games that involve assembling potato heads and
[126]
that's when I choose to use.
[127]
The "P" segment of PDSA.
[131]
This answers the question of what is trying to be accomplished,
[135]
provides guidance for the team's specific improvement efforts,
[138]
and it ensures that the team's activities align with the strategic
[142]
goals of the practice.
[143]
It needs to be clearly stated in numerical
[146]
as well as represented challenge for the practice and provider.
[149]
An example of an effective AIM statement might be
[152]
"by June 1st 2013 our practice will be able to identify 100 percent our
[157]
patients with hypertension using electronic health record."
[160]
One needs to ask questions and make predictions.
[163]
The "Do" segment is where the actual plan gets carried out.
[167]
Unexpected observations and problems are documented as well as preliminary
[171]
analysis of the data that was collected during the "do".
[174]
The study process is where a complete data analysis gets performed.
[180]
The data collected should be compared to the predictions and a summary of what
[184]
was learned should be generated.
[186]
The "Act" portion is where it gets decided what changes should be made the next cycle
[192]
based on what was discovered in the last cycle
[195]
and the process starts all over again. In a nutshell,
[198]
the PDSA cycle should be used to predict the effectiveness of change and plan the
[203]
next steps,
[204]
revise and adapt changes to the patient's and practice's needs,
[208]
assess costs and the side effects of the change
[211]
as well as to anticipate potential implementation barriers.
[217]
It's important to implement changes on a small scale
[221]
until one is certain that they will result in improvement. It's also important
[225]
to repeat the PDSA cycle until the desired change matches the AIM statement
[230]
which means that
[231]
what was set out to be achieved has been accomplished. Strategies that will help
[235]
ensure that the change was actually for the better,
[237]
are to use a small set a patients, do it on a small scale,
[242]
to be as specific as possible, to do it over a short period of time like a few
[247]
days to a week before evaluating the results of a change.
[251]
While all improvements are the result of change, all changes are not necessarily
[255]
improvements
[256]
By testing and measuring during the PDSA cycle,
[260]
one can predict the effectiveness of the change in plan the next cycle.
[263]
It's important to collect just enough data
[267]
and not to make this part overly complicated. It works best to incorporate
[271]
the testing into the daily routine.
[273]
It's helpful to ask the following things when evaluating the test results:
[278]
Were the changes executed well?
[281]
Were the support processes adequate?
[284]
Was the original hypothesis or hunch correct?
[289]
Despite executing the change well,
[292]
did it not result in an improvement? and
[295]
did the local improvement impact access or efficiency?
[299]
You want to avoid doing the following:
[303]
The tendency to make the objective statements too broad.
[307]
Confusion between the objective
[311]
and the questions. The tendency to not anticipate in the plan step how to
[316]
analyze the data that gets collected.
[318]
The tendency to do too much
[322]
in one PDSA cycle instead of multiple cycles.
[325]
and lastly a tendency to use PSA for collecting data on a measure rather than
[331]
to test on an idea for change.