QC that doesn't live in a spreadsheet
Why laboratory QC belongs on the result-release path: Westgard-style evaluation, failed/overdue gating of autoverification, and evidence supervisors can defend.
- quality control
- Westgard
- lab middleware
- QC lockout
- autoverification
- clinical laboratory
- laboratory supervisor
Definition
Release-path QC means quality-control status is evaluated in the same workflow that decides whether patient results may auto-release — not only recorded in a spreadsheet, binder, or analyzer-local screen after the fact.
Most labs do not lack QC. They lack QC that acts in time.
Audience: lab supervisors / QA (policy and accreditation) and informatics (where the gate is enforced). Applicable worldwide; formal QC program design remains the laboratory’s responsibility.
Spreadsheet QC vs release-path QC
| Spreadsheet / siloed QC | Release-path QC |
|---|---|
| Reviewed when someone remembers | Evaluated as QC results land |
| Failed run lives in a chart | Failed/overdue QC can stop patient AV for that assay |
| Evidence scattered by instrument | Central view across connected analyzers |
| Inspection story is manual assembly | Trail tied to what was (or wasn’t) released |
Accreditation still owns the program. Software owns whether the program can interrupt bad release in the moment.
What QC in the middle layer does
- Ingest QC from connected instruments alongside patient results
- Evaluate rules (e.g. Westgard multirules, lab-defined limits, overdue cadence)
- Gate release — if QC failed or overdue for an assay, do not auto-release patient results on that channel
- Show context — which rule failed, which instrument/assay, what to fix next
- Resume cleanly — after corrective action and acceptable QC, release logic turns back on
That is the difference between “we do QC” and “QC controls what leaves the lab.”
Coupling to autoverification
AV without QC gating is a trust problem. A sane rule of thumb:
| QC status (relevant level, within cadence) | Patient AV |
|---|---|
| Pass | Eligible (other AV rules still apply) |
| Fail | Off for affected assays until corrected |
| Overdue | Off until a fresh acceptable run |
Pair with analytic limits, deltas, criticals, and flags: Autoverification without the anxiety. Encode order of operations: Encode QC gates and AV.
What good looks like on the bench
- One place to see QC status across vendors
- Lockout / hold behaviour written in the SOP
- Techs are not guessing whether “someone checked the binder”
- Inspectors can follow control failure → action → resume (Audit-ready trails)
FAQ
Does middleware replace the lab’s QC program?
No. Method validation and accreditation still own the program. Middleware enforces whether failed or overdue QC can interrupt patient release in time.
Should QC lockout stop autoverification?
Yes for the affected assays. AV without QC gating is how labs lose trust in automated release.
Why not keep QC only on the analyzer screen?
Analyzer-local QC often will not stop patient results moving on a separate path. Release-path QC couples control status to what can leave the lab.
Related reading
About TransLABtor
TransLABtor can keep real-time QC gating in the middleware path with operational rules and release logic — without replacing the LIS. Site QC program design remains with the laboratory. Book a demo or see supported interfaces.