Run charts: traditional rules for nonrandom variation

A tool for monitoring quality improvement processes

Using run charts for quality improvement

A good way to monitor the impact of changes during a quality improvement project is to create a run chart, starting with an initial median using baseline data. If the baseline data comes from a process showing no signals (shift, trend, runs, astronomical data points), extend or 'freeze' this initial median into the future. In this way, new data are not allowed to influence the initial median. Any changes in the new data stand out against the baseline median more clearly, allowing for more accurate detection of signals of improvement (the probability-based rules are relative to this median value).

The shift and run rules require more than 10 points before they are applicable. But there are many applications (e.g. patient monitoring of annual PSA tests) where the run chart is useful with just three or four data points in order to get an early indication of central tendency and trend.

Limitations

Run charts are designed for the early detection of signals of improvement or degradation in a process over time.
However, run charts are not capable of determing if a process is stable (as defined by Shewhart in relation to control charts only). Using control chart language with run charts can create confusion because the two methods include different rules for identifying non-random patterns. When using run charts, avoid the terms "special cause" and "stable" or "unstable", reserving the use for control charts.

How to construct a run chart

Goal lines and annotations of changes and other events can also be added to the run chart.

Rules to help interpret a run chart

The three probability-based rules are used to objectively analyse a run chart for evidence of non-random patterns in the data based on an α error of p<0.05.


Rule 1 — shift
six or more consecutive points either all above or all below the median. Values that fall on the median do not add to not break a shift. Skip all values that fall on the median and continue counting.
Even though the table on the right extends to n>30, if your data exceeds 24 points, it is better to consider switching to a control chart.
n Run
Length
≤10 6
≤15 7
≤20 8
≤30 9
≤40 10
≤50 11
run chart: Rule 1
Even though the table on the right extends to n>30, if your data exceeds 24 points, it is better to consider switching to a control chart.

Rule 2 — trend
Five or more consecutive points all going up or all going down.If the value of two or more consecutive points is the same, only count the first point and ignore the repeating values; like values do not make or break a trend.
Even though the table on the right extends to n>30, if your data exceeds 24 points, it is better to consider switching to a control chart.
n Run
Length
6~8 5
9~30 6
31~150 7
150~1,000 8
run chart: Rule 2
Even though the table on the right extends to n>30, if your data exceeds 24 points, it is better to consider switching to a control chart.

Rule 3 — runs
A run is a series of points in a row on one side of the median. A non-random pattern is signalled by too few or too many runs, or crossings of the median line.
  1. Count the number of times the line connecting the data points crosses the median and add one.
    • For example, in graph #3 "Rules broken [3]", the blue data line consists of 10 data points, and this data line crosses the median just once (between point 5 and point 6).
    • Add one and the "number of crossings" to test is "1+1=2".
  2. Compare with Table-1 at the bottom of this page to determine if too many or too few runs exist. Table 1 shows the number of crossings that would be expected if the data was randomly distributed; the number is shown as a range from "lower limit (LL)" to "upper limit (UL)".
    • For n = 10, the lower limit is 3 and the upper limit is 9; that is, for this data series to pass the test for random results, the number of crossings should be between LL and UL (3~9).
    • However, n=2 (outside the range 3~9), so the conclusion is that the data is not randomly distributed.
    • For our quality improvement monitoring, this indicates a change that may be a result of actions.
run chart: Rule 3
Rule 3: run
A run is a series of points in a row on one side of the median.
It is used when deciding whether data is randomly distributed.

Rule 4 — astronomical point
An astronomical data point is one that is obviously different from the rest of the points. Astronomical points should not be confused with the highest or lowest data points, which every run chart will have. While Rules 1, 2 and 3 are probability based, Rule 4 is subjective and recognises the importance of the visual display of the data in a run chart.
run chart: Rule 4

References

  1. Provost LP, Murray SK. The health care data guide. Learning from data for improvement. www.amazon.com 2011. John Wiley & Sons.
  2. Perla RJ, Provost LP, Murray SK. The run chart: a simple analytical tool for learning from variation in healthcare processes. wwwncbi.nlm.nih.gov BMJ Qual Saf 2011; 20: 46-51.
  3. Hart MK, Hart RF. Statistical process control for health care. 2000 www.amazon.com
    Translated and published in Taiwan as:
    鐘國彪審閱、陳宗泰譯:「健康照護的統計流程管制」 金名圖書有限公司 www.eslite.com

Appendix

Table 1. Checking for too many or too few runs on a run chart.
• NN = Total number of data points on the run chart that do not fall on the median
• LL = Lower limit for the number of runs (< than this number runs is 'too few')
• UL = Upper limit for the number of runs (> than this number of runs is 'too many')
NNLLUL NNLLUL NNLLUL NNLLUL NNLLUL NNLLUL
1039 20616 301121 401527 501933 602438
11310 21716 311122 411527 512033    
12311 22717 321123 421628 522034    
13411 23717 331223 431628 532134    
14412 24818 341224 441729 542135    
15512 25818 351224 451730 552235    
16513 26919 361325 461731 562235    
17513 271019 371325 471831 572336    
18614 281020 381426 481832 582337    
19615 291020 391426 491932 592438