A point-of-care analyzer that powers on and prints a number is not the same as a point-of-care analyzer that can be trusted. Between those two states sits a quality management discipline that rarely makes it into procurement conversations: point-of-care analyzer quality control, the routine of internal checks and external verification that catches a drifting result before it reaches a clinical decision. For a field program running handheld chemistry, hematology, or immunoassay devices away from a central laboratory, this discipline is not optional paperwork — it is the difference between a device that is field-suitable and one that is quietly producing wrong answers.
Why a Working Analyzer Can Still Be Wrong
Instrument failure is rarely dramatic in point-of-care testing. A cartridge lot can shift, a reagent can degrade faster than its expiry date implies, an optical or electrochemical sensor can drift with heat and humidity, and an operator new to a device can introduce technique variation that a bench-trained laboratorian would never make. None of these failure modes stop the analyzer from producing a result. They just make that result wrong in a way that looks ordinary. A quality control program exists precisely to surface that kind of failure before it is mistaken for a clinical finding.
Internal Quality Control: The Daily Discipline
Internal quality control (IQC) is the layer a field team runs itself, on its own schedule, using control materials with known analyte concentrations rather than patient samples. Good practice runs those materials at more than one concentration level — low, normal, and high — so that drift is caught across the range the device is actually expected to report, not just at one point on the curve.
Frequency matters more than most field programs assume. General practice for non-waived testing calls for at least two levels of control material analyzed roughly once every 24 hours for chemistry analytes, and more often — about once every 8 hours — for blood gas, hematology, and coagulation testing, categories where instability shows up faster. A newer complement to scheduled IQC is patient-based quality control, which watches the statistical pattern of real patient results in the background for the same kind of drift, catching problems between scheduled control runs rather than only at them. Every run, scheduled or background, needs to be documented; an undocumented control run is functionally the same as one that was never run.
External Quality Assurance: The Blind Check
Internal quality control tells a team whether its own process looks stable. It cannot tell a team whether its results agree with anyone else’s. That is the job of external quality assurance (EQA), also called proficiency testing: a scheme sends blind, patient-like samples to a testing site, the site runs them exactly as it would run a real patient sample, and the result is compared against a peer group or a reference method.
The credibility of an EQA program rests on a few practical rules. Samples should be handled by the same personnel who run real patient testing, not a specialist brought in for the exercise. The feedback report needs to be detailed enough that a point-of-care coordinator can actually act on it — identifying a specific device, site, or operator whose results are drifting, not just an aggregate pass or fail. And EQA is meant to cover the whole testing process, not only the analytical step: how a sample was collected and how a result was interpreted matter as much as what the instrument displayed.
Comparing the Two Layers
| Aspect | Internal Quality Control (IQC) | External Quality Assurance (EQA) |
|---|---|---|
| Who runs it | The field site itself, on its own schedule | An outside program; the site is a blinded participant |
| What it checks | Day-to-day stability of the analytical process | Whether results agree with a peer group or reference method |
| Typical frequency | Roughly every 24h (chemistry) to every 8h (blood gas, hematology, coagulation) | Periodic rounds set by the scheme, usually a few times a year |
| What it catches | Reagent degradation, sensor drift, operator technique | Systematic bias the site’s own controls would not reveal |
The Standards Behind the Practice
None of this is invented ad hoc by individual field programs; it is anchored to a small set of standards bodies. ISO 22870 sets requirements specific to point-of-care testing and is meant to be applied alongside ISO 15189, the broader standard for quality and competence in medical laboratories — and ISO 22870 is explicit that participation in an external quality assurance scheme is expected of point-of-care devices, not merely encouraged. In the United States, the Clinical Laboratory Improvement Amendments (CLIA) set the regulatory floor: many point-of-care tests are CLIA-waived and carry lighter requirements, but any site running moderate- or high-complexity point-of-care testing is held to the same proficiency-testing and quality-control obligations as a central laboratory. The College of American Pathologists applies a parallel standard regardless of where the testing physically happens.
For low-resource and field settings specifically, the World Health Organization’s ASSURED criteria — introduced in 2006 for point-of-care diagnostics — frame the design goal a quality program is protecting: Affordable, Sensitive, Specific, User-friendly, Rapid and robust, Equipment-free, and Deliverable to the people who need the result. A device can meet every one of those design criteria on paper and still fail in practice if the quality program around it is thin.
What This Means for a Field Program
Procurement conversations about point-of-care analyzers tend to focus on throughput, footprint, and battery life — the visible specifications. The quality control program is less visible and easy to underbudget: control materials at multiple levels, a documented run schedule, and a route into an external proficiency scheme all cost money and staff time that a device’s spec sheet does not mention. A field-suitable analyzer is one where that budget line exists from the start, not one added after a result is questioned in the field. Building that expectation into how a program evaluates point-of-care analyzers — alongside durability and cold-chain independence — is what turns a capable instrument into one that a clinical decision can actually rely on.