Measurement For Quality Improvement
Measurement For Quality Improvement
This workbook is the result of the efforts of the Health Quality Ontario (HQO) For additional information about other
resources, contact: Health Quality Ontario www.hqontario.ca
Individuals may reproduce these materials for their use provided that proper attribution is given to the appropriate
source. The recommended citation for this resource guide is: Health Quality Ontario (April 2013).
HQO is funded by the Ontario Ministry of Health and Long-Term Care (MOHLTC).
Plan-Do-Study-Act (PDSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Sample Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Of the many types of measurement, two are typically utilized in health care:
measurement for research and measurement for improvement. Traditionally,
health care providers are trained to look at research; however, measurement
for research is very different from measurement for improvement. The
differences are outlined in the table below.
1. Name of measure
2. Type of measure (outcome, process or balancing, see below)
3. Why the measure is needed for the project
> Examples of outcome measures:
PDSA Measures are those that are collected with each test of change
(PDSA) that is carried out. These measures provide information about the
effect of each change attempt.
For example, assessment of residents in long-term care for falls (process) will
typically serve to prevent falls (outcome), as actions are taken in response to
what is learned in the assessment. If the quality improvement team focused
on the level of completion of these assessments over time and discovered
that the rate of completion declined, it would be a fairly good predictor
Rates, ratios and percentages help you standardize your data so that it is
expressed in a meaningful way that can be readily compared with other
data. Ratios and rates may be expressed as percentages. How you choose
to present your data will depend on the nature of your data and how you
plan to use it.
Ratios (percentages) may be used to adjust for the impact of natural changes
in your system, such as volume. The numerator is the key measure (e.g.,
costs, patients waiting) and the denominator is the unit of production or
volume (e.g., total costs, total patients waiting). For example, if the number
of patients waiting for more than one hour increased dramatically, you might
draw one conclusion. If you knew that overall volume had also increased
(which would show up in the ratio), you would mostly likely draw another,
more accurate, conclusion.
Try to build data collection into the daily routine instead of making it a
separate project. This not only ensures that data is timely but also reduces
stress by making measurement something that is simple to do. Create data
collection forms that include only the information you need and that are
easy to fill out. When integrating measurement into a staff member’s role,
be sure to build in a contingency plan for ongoing collection should that
person be unavailable.
The best way to collect and display data is to use run charts and statistical
control charts –graphical records of a measure plotted over time (often
months). Charts annotated with changes and events provide even more
information and can help you more accurately make connections between
interventions/events and outcomes.
SAMPLE MEASURES
When collecting measures for a quality improvement project, teams often ask
how much they should collect. Should every patient chart be examined and
recorded? Should every element that touches the outcome be measured?
The very simple answer is to measure enough to create knowledge and
understanding about the system. Each system is different, so whether
examining five charts is enough or it takes ten, it is important not to overwhelm
the improvement team by creating so much work that it cannot get the
measurements done. It is, however, crucial to ask whether what is being
measured gives enough information to understand how the system is performing
and how it will react to planned changes. Once “how much” has been
determined, it is necessary to determine “how often,” still keeping in mind the
availability of the information and of the team to carry out the measurement.
OR OR
Time was measured from the “decision to admit” to the arrival of the patient
in the inpatient room. The destination could not be a “holding area” but had
to be a real inpatient bed. The sample collection was done in real time. So, a
data collection process had to be created by members of the team that were
collecting the data. In this example, the collections had to be done weekly
and summarized as the percentage of patients in the sample that achieved
the goal for that week. Six weeks of data had to be collected and six data
points placed on a run chart.
> Figure 1 is an example of work
by an improvement team formed in
response to complaints from staff
MEASUREMENT: RUN CHARTS about delays in processing test
Why Use Run Charts? results. This chart demonstrates the
There are many ways that data can be presented to tell the story of a project length of time (in hours) that it took
or improvement. Whether you use histograms, pie charts or run charts, the for test results to be completed
intention is the same: to gain new knowledge and to engage the audience, and received by staff. The graph
whether they are leaders, staff or customers. However, some graphical demonstrates the changes
representations can be misleading. measured at Week 4 and Week 11.
During Week 4 (that is, four weeks
after the team was formed), the
team collected data to confirm
or deny the complaints they were
hearing. The data show that the
turnaround time was eight hours,
unacceptable by any standard. At
Week 7, after the solution design
process, the team tested a change.
Measuring again during Week 11,
they found that the turnaround time
was now three hours. The reduction
in cycle time from eight hours
Figure 1 to three hours is significant and
represents a 62.5% improvement.
2
Scenario Three – It appears that
the process steadily improved over 0
the 14-week period. However, the 1 2 3 4 5 6 7 8 9 10 11 12 13 14
rate of improvement did not change Week
when the change was introduced Week
in Week 7. Although the cycle time
10
for the process certainly improved,
Daily Time (Hours)
0
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Week
10
Daily Time (Hours)
4
12 2 Measurement for Quality Improvement | Health Quality Ontario
0
0
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Week
experience. For example, your Common Cause variation is inherent in a system (process or product) over
daily commute can take between time, affecting everyone working in the system and affecting all outcomes
45 minutes and 60 minutes. There of the system. A system that has only common cause variation is said to be
is 15 minutes variability for extra stable, implying that the process is predictable within statistically established
traffic or having to stop at all the limits. Differences over time are due to chance rather than predictable
stoplights along the route. This is influences on the system. Common cause does not mean good variation—it
common cause variation. Special only means that the process is stable and predictable. For example, if a
cause variation is that snowstorm patient’s systolic blood pressure is usually around 165 mmHg and is between
that causes our normal commute to 160 and 170 mmHg, this might be considered stable and predictable but it is
take 120 minutes also completely unacceptable.
In the same way that common cause variation cannot be regarded as ‘good’
variation, special cause variation should not be viewed as ‘bad’ variation.
You could have a special cause that represents a very good result (e.g., a low
turnaround time), which you would want to emulate. Special cause merely
means that the process is unstable and unpredictable.7
A system that has both common and special causes is called an unstable
system. The variation may not be large but the variation from one time
period to the next is unpredictable. Understanding the distinction between
common and special causes of variation is essential to developing effective
improvement strategies. When you become aware that there are special
causes affecting a process or outcome measure, it is appropriate and usually
economical to identify, learn from and take action based on the special
cause. Often this action is to remove the special cause and make it difficult
for it to occur again. Other times, the special cause produces a favourable
outcome, in which case the appropriate action is to make it a permanent part
of a process.
There are three signals of non-random change or special cause that you
should look for on run charts. If you don’t see evidence of one of these
signals, then your data is exhibiting common cause variation. Finding one
or more of these signals suggests that further analysis and interpretation by
the team members is required in order to understand the causes or factors
influencing the change. Keep in mind that not all common cause variation is
good, and not all special cause variation is bad.
Signal 1: Shift
A shift signaling change is six or more consecutive points above or below the
median. Values that fall directly on the median are not included in this count
and neither break nor add to a shift.
35
30
25
to Specialist
# of Days
20
15
10
0
13
20
27
03
10
17
01
08
15
22
29
05
12
19
26
03
10
17
31
24
24
3-
3-
3-
4-
4-
4-
5-
5-
5-
5-
5-
6-
6-
6-
6-
7-
7-
7-
7-
4-
7-
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
Week referred
# Days to Specialist Median
35
30
25
to Specialist
# of Days
20
15
10
0
13
20
27
03
10
17
01
08
15
22
29
05
12
19
26
03
10
17
31
24
24
3-
3-
3-
4-
4-
4-
5-
5-
5-
5-
5-
6-
6-
6-
6-
7-
7-
7-
7-
4-
7-
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
Week referred
# Days to Specialist Median
120
100
80
Days to PC visit
Average #
60
40
20
0
02
09
16
23
30
06
13
20
27
06
13
20
27
03
10
17
01
08
15
22
24
1-
1-
1-
1-
1-
2-
2-
2-
2-
3-
3-
3-
3-
4-
4-
4-
5-
5-
5-
5-
4-
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
-0
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
Date (week)
Days from discharge to primary provider Median
The effect of changes in the process can be measured with greater speed
and reliability.
2 Ibid.
3 Kaplan, R.S. and Norton, P. (1997). Balanced Scorecard: Translating Strategy into Action.
Boston: Harvard Business School Press, p. 28.
4 Provost, L.P. & Murray, S. (2011). The Health Care Data Guide: Learning from Data for
Improvement. San Francisco: Jossey-Bass, pp. 10-12
6 Ibid.
7 Ibid.
8 Deming, W.E. (1986) Out of the Crisis. Cambridge: MIT Press, p. 340
www.hqontario.ca