Category: Basic QC Concepts | Estimated reading time: 9 minutes
A Frequently Misinterpreted Signal
A new operator sees a warning signal appear on the screen. The QC point has crossed the ±2SD line. First reflex: hold patient results, repeat QC, call the supervisor.
A veteran operator who has seen the same signal for years just shrugs. They make a note, then continue working.
Both are wrong—but in different ways.
The 1₂s rule is one of the most misunderstood points in the Westgard QC system. It is not a rejection rule, but it is also not something to be ignored. This article explains what Westgard actually intended when designing this rule, and what medical laboratory scientists (ATLM) should do when that signal appears.
What Is 1₂s, and Where Does It Come From
The notation 1₂s is read as: one control point crosses the ±2SD limit.
This rule is not a new invention. It appeared in the paper by Westgard et al. (1981) in Clinical Chemistry, which introduced the multi-rule Shewhart system for clinical laboratory QC. In that paper, 1₂s was explicitly established as a warning rule—not a rejection rule.
Westgard designed the system as a series of tiered rules. When 1₂s is met, the analyst does not immediately reject the run—they check whether any rejection rule is also met. If no rejection rule is triggered, the run is accepted, with a notation.
The logic behind this is simple: in a truly controlled process with a normal distribution, about 4.5% of points will naturally fall outside ±2SD simply due to random variation. If every point outside ±2SD immediately caused a rejection, about 1 in 22 runs would be rejected without any real problem. In daily practice, this results in chaos—patient results are held, QC is repeated constantly, and eventually, the rules begin to be ignored because they are considered too sensitive.
Westgard designed 1₂s as an early signal, not a verdict.
What Should Happen When 1₂s Appears
When one point crosses ±2SD, the correct step is to initiate an evaluation, not to act immediately.
First, check for rejection rules.
Check if any of the following rules are met in the same run or previous runs:
- 1₃s: has the same point crossed ±3SD? If so, this is a rejection rule.
- 2₂s: have two consecutive points (of the same level or two different levels in one run) both crossed ±2SD on the same side? This is also a rejection rule.
- R₄s: does the range between two points in one run exceed 4SD? This indicates a large random error.
- 4₁s: are four consecutive points all on the same side of ±1SD?
- 10x: are ten consecutive points all on one side of the mean?
If not a single rejection rule is met, the run is not rejected.
Second, look at the pattern.
A single point outside ±2SD that stands alone is different from one that appears after four consecutive points show an upward trend. Context is important. Observe whether a pattern is forming—points that are slowly shifting to one side, or a gradual movement that has not yet formally met the trend rule but already feels non-random.
Third, record the observation.
Even if the run is accepted, note that 1₂s occurred. This is important for two reasons: first, if a similar pattern appears in the next run, previous notes help to recognize the trend faster. Second, this documentation is proof that the QC system is actually being operated, not just formalized.
Two Opposing Errors
Error 1: Treating 1₂s as a Rejection Rule
This happens because it is intuitive—the point is outside the limit, so there must be a problem. But if every 1₂s causes a rejection:
- QC runs are repeated constantly without a valid reason
- Patient results are held longer than necessary
- Pressure to "get in" increases, and eventually leads to "repeat until pass" practices, which ignore real signals
- ATLM lose confidence in the QC system because it is perceived as too sensitive
Westgard designed the multi-rule system specifically to avoid this: high sensitivity (ability to detect real errors) combined with high specificity (low false alarms).
Error 2: Ignoring 1₂s Because It’s "Just a Warning"
This is the opposite—and just as dangerous.
A 1₂s that is consistently ignored can hide an emerging pattern. For example: run 1 has a 1₂s at the low level, no rejection rule, accepted. Run 2 has another 1₂s at the low level, no rejection rule, accepted. Run 3 is the same. If no one records it, no one sees that three consecutive runs at the low level are above ±2SD—which is already a strong signal that something is shifting.
An ignored 1₂s is wasted data.
Context That Changes Interpretation
Not all 1₂s are created equal. Several factors change the level of vigilance:
Is this an isolate or part of a pattern? A single point outside ±2SD after dozens of stable points is different from the same point appearing after several runs that felt like they were "moving." The former is more likely to be random variation; the latter is more likely to be the beginning of a systematic error.
Which level is affected? If only one level crosses ±2SD while others are stable, the problem is likely with the control material itself (contaminated vial, degraded material, improper mixing) or the measurement area specific to that concentration. If two levels move together in the same direction, it is more likely there is a change in the entire measurement system—reagents, calibrators, or the instrument.
When was the last change in the lab? Reagent lot changes, recalibration, maintenance—all of these can shift control values. If 1₂s appears right after one of these events, it is likely related. Check lab records before drawing conclusions.
How far is the point? A point falling exactly at 2.05 SD is different from one at 2.9 SD. Both are formally 1₂s, but the one approaching ±3SD is much more worthy of attention, as it is only a small difference from the 1₃s rejection rule.
When 1₂s Needs Escalation
There are situations where 1₂s—even if it does not meet a rejection rule—should not be resolved alone:
- The point is approaching ±3SD (e.g., above 2.7 SD) and there is no clear explanation
- 1₂s appears simultaneously with unusual clinical findings in patients at the same time
- A 1₂s pattern repeats over the last few runs, even if it hasn't met the formal trend rule
- The lab has just changed reagent lots or performed calibration, and this is the first QC run after
In these situations, the wisdom of consulting a supervisor or QC lead is safer than deciding alone.
Relationship of 1₂s with Other Rules in a Multi-Rule System
The most appropriate way to understand 1₂s is as an entry point to a multi-rule evaluation, not as a standalone rule.
In the classic Westgard flow:
- If no point is outside ±2SD → run is accepted, proceed
- If there is a point outside ±2SD (1₂s met) → evaluate rejection rules
- If a rejection rule is met → run is rejected, investigate
- If no rejection rule is met → run is accepted, but note and watch the pattern
Without 1₂s as a trigger, the multi-rule system does not work—because there is nothing to initiate the evaluation. This is what makes 1₂s structurally important: not because it decides a rejection itself, but because it activates a more complete assessment system.
Notes for QC Software
Some QC software displays 1₂s as a yellow or orange flag, distinct from red for rejection rules. This is the correct design and aligns with Westgard's intent.
Problems arise when:
- Software does not visually distinguish between warning and rejection—all flags look the same
- Lab SOPs do not explain this difference, causing ATLM to interpret all flags as rejections
- Software configures 1₂s as a rejection rule because that is the default setting
If this happens in your lab, this is not a technical problem—it is a configuration and SOP issue that needs to be fixed. Check whether the QC software used allows the separation of warning rules and rejection rules, then ensure the configuration aligns with the guidelines written in the SOP.
Summary
- 1₂s is a warning rule, not a rejection rule—this is not a configuration error; it is a design intentionally created by Westgard (1981).
- When 1₂s appears, the correct step is to check other rejection rules, not immediately hold patient results.
- If no rejection rule is met, the run is accepted—but the observation is recorded.
- Ignoring 1₂s is just as dangerous as panicking: emerging patterns can be missed if no one records them.
- Context is important: a single point outside ±2SD that stands alone is different from one that appears as part of a moving pattern.
- Escalation is still required if the point is nearing ±3SD, a 1₂s pattern repeats, or there are recent changes in the lab that have not been evaluated.
- Ensure SOPs and software configurations are consistent: 1₂s should be recorded as a warning, not a rejection.
Closing
- 1₂s is not a fire alarm—it is more like an indicator light on a dashboard. It asks you to look more closely, not to immediately pull over and turn off the engine. An operator who is accustomed to reading this signal proportionately—without panicking, without ignoring—is an operator whose QC system truly functions as a system, not just a formality.