Eight Days of a Creatinine Drift and 260 Reported Results
Creatinine is measured with a two-level quality control system on the main chemistry analyzer. Level 1 (mean 0.90 mg/dL, SD 0.04) has tracked within 1 SD for two weeks. Level 2 (mean 4.20 mg/dL, SD 0.15) shows: five preceding days 4.16, 4.21, 4.19, 4.23, 4.17; Day 1 4.18; Day 2 4.22; Day 3 4.32; Day 4 4.38; Day 5 4.44; Day 6 4.61, a 1-3s rejection. The tech on the bench repeats level 2 on the same aliquot, obtains 4.30, calls it in control, and releases the day's 38 creatinine results. Day 7 is 4.35 and Day 8 is 4.31. A new reagent lot was placed on Day 1 and calibration was verified with two levels, both within 8% of the assigned values. Roughly 260 patient creatinine results have been reported since Day 1, and eGFR is auto-reported with every creatinine. The chemistry supervisor is on leave and the bench tech qualified four months ago.
1. Apply the Westgard rules to this data. When did the run actually go out of control, and was the Day 6 recovery defensible?
Read the worked answer
Convert to SD units (SD = 0.15, mean = 4.20):
- Preceding five days: -0.3, +0.1, -0.1, +0.2, -0.2 SD
- Day 1: -0.1 | Day 2: +0.1 | Day 3: +0.8 | Day 4: +1.2 | Day 5: +1.6 | Day 6: +2.7 | Day 7: +1.0 | Day 8: +0.7
Which rules fire:
- 10x (ten consecutive points on one side of the mean). Days 1 through 5 are all above the mean, and they are preceded by four days above the mean as well, giving nine consecutive positive values by Day 5. Under a 10x rule the run is out of control at Day 5 - one day before anyone acted - and the pattern is a systematic shift, not random scatter.
- 1-3s on Day 6. 4.61 is +2.7 SD, which trips a 1-3s rejection. That is an immediate rejection of the run.
Was the Day 6 repeat defensible? No, on two grounds. First, a repeat on the same aliquot is not an independent repeat; it re-measures the same cup and cannot distinguish a real shift from a pipetting or bubble problem. Second, and more important, a single in-control repeat does not override a documented multi-day shift. Once 10x has fired, the correct response is investigation and corrective action, not re-running until a value looks acceptable. Releasing 38 results on that basis converted a QC event into a patient-result event.
The bench tech is four months qualified and unsupervised; that is a training and escalation failure at least as much as an individual one.
2. Assess patient impact. Which patients are most affected, and how would you design the look-back?
Read the worked answer
Characterize the error first. Level 1 was stable while level 2 drifted, so the bias is roughly proportional - small at low creatinine, larger at high creatinine. At a mean of 4.20 the Day 5 shift is about +0.25 mg/dL (+6%) and the Day 6 value about +0.4 mg/dL (+10%). At creatinine 1.0 mg/dL, a 6-10% proportional bias is 0.06-0.10 mg/dL, well within clinical noise.
Who is most affected:
- Patients near a decision threshold at high creatinine - for example, a value of 3.9 reported as 4.2, or a 4.4 reported as 4.7. Dosing of renally cleared drugs, contrast decisions, and dialysis timing all sit on these boundaries.
- eGFR is auto-reported from creatinine, so the bias propagates into a calculated value that clinicians treat as a discrete category (CKD stage boundaries at 60, 45, 30, 15 mL/min/1.73 m2). A CKD 3b patient could be reclassified as stage 4.
Look-back design:
- Extract all creatinine results from Day 1 through the day the problem is corrected - approximately 260.
- Rank by creatinine value and flag those close to a decision threshold, then flag those with a same-patient prior result suggesting an unexplained step-up.
- Re-test a representative sample of retained specimens to estimate the actual bias at each level rather than assuming the QC drift equals the patient bias.
- Notify the medical director and the ordering clinicians for the flagged subset; do not blanket-amend 260 results without evidence of clinical significance.
Document the analysis and its limits - you cannot retest everything, and saying so is part of a defensible look-back.
3. What corrective action, documentation, and escalation are required before the bench resumes reporting?
Read the worked answer
Corrective action, in order:
- Stop reporting. Close the analyte in the LIS if the middleware allows it, and notify the laboratory medical director and the on-call supervisor - 'the supervisor is on leave' is a reason to escalate, not a reason to wait.
- Investigate the reagent change first. A new lot on Day 1 with a proportional upward drift is the leading hypothesis. Check lot-to-lot comparison data, reconstitution and storage, expiration, and whether onboard stability was exceeded. Repeat the calibration with fresh, properly handled reagent.
- Recalibrate and re-verify. Calibration verification should be repeated, and the level count and acceptance criteria must match your accreditor's checklist requirement rather than the two levels used. Verify across the reportable range, not just at two points.
- Confirm with a comparison study. Run 20 patient samples by the old and new conditions and evaluate bias against a defined acceptance limit tied to the clinical decision points, not a convenient percentage.
- Reinstate QC and document the return to control before any patient result is released, with the technologist, date, and time recorded.
Documentation: the QC charts, the rule violations and dates, the investigation notes, the corrective action, the look-back analysis, and the medical director's sign-off. Retain per your retention policy (CLIA requires at least two years for most records).
Escalation and people: brief the bench tech without blame in writing - the system failed to teach escalation. Add a rule that any 10x or 2-2s event requires supervisor notification before release, and audit compliance monthly for the next quarter.