CAP
CAP vs CLIA Proficiency Testing: Key Differences for Clinical Labs
If you run an accredited clinical laboratory in the US, you are simultaneously under CLIA (federal regulation) and very likely under CAP (a deemed-status accreditation body that satisfies CLIA). They share a backbone — proficiency testing, recordkeeping, competency, corrective action — but the specifics around proficiency testing diverge in ways that catch labs out.
This post is the cheat sheet: where CAP and CLIA agree, where they don’t, and what that means for how you actually run your PT program day to day.
What both standards agree on
Both frameworks demand the same fundamentals:
- Enrolment in an approved proficiency testing program for every regulated analyte
- Sample handling that matches routine patient-sample handling — no preferential treatment, no inter-lab communication
- Documented results submission within the provider’s deadline
- Investigation and corrective action for unacceptable results
- Records retention sufficient for the inspection cycle
So far so good. This is where most discussion of “PT compliance” stops, and it’s also where the practical disagreements start.
Where CLIA and CAP diverge
Consecutive-failure rules
CLIA defines unsuccessful performance as two unsuccessful PT events in two of three consecutive testing events for the same analyte. Hit that pattern and you’ve triggered a regulatory event with consequences — cessation of testing for that analyte, retraining, and re-attestation among them.
CAP’s rule is similar in spirit but has its own implementation, codified across its checklists. The practical difference: CAP tracks failure patterns at a per-analyte level with its own thresholds, and the operational consequences inside a CAP-accredited lab arrive faster than the CLIA enforcement timeline, because CAP is doing the inspecting.
Review window after results-received
CAP and CLIA both expect the lab to review the provider’s evaluation report promptly. CAP makes the 30-day review window explicit: from the date the evaluation results are received, the lab has 30 days to review and act on them, with documentation of who reviewed and when.
CLIA’s regulatory text doesn’t fix the same explicit clock for every situation, but the operational expectation is essentially identical — a review with documented evidence. If you’re CAP-accredited, treat the 30-day rule as binding; if you’re CLIA-only, treat it as a defensible best practice.
PT integrity attestation
Both CAP and CLIA require the laboratory director (or designee) to attest that PT samples were handled in the same manner as patient samples. The form, the wording, and the timing vary slightly between the two; the substance does not.
The practical mistake we see: the attestation is required at submission, not retrospectively. A round closed without attestation is a finding. Worse, if the lab’s process treats attestation as something to gather later, you’ve created a window where samples could be discussed inter-lab before attestation is committed — exactly the integrity gap the rule exists to close.
Documentation of corrective action
CLIA expects corrective action for unacceptable results. CAP goes further and expects effectiveness verification — proof that the corrective action actually worked, typically by linking the action’s closure to a subsequent acceptable result on the same analyte.
This is one of the more common areas where labs have done the work but not the documentation. The technologist investigated the unacceptable result, found the root cause, and corrected it. The next round was acceptable. But nothing in the record explicitly links the two. To an auditor, that’s a corrective action without verified effectiveness.
Independent review and round closure
CAP requires that the director or designee review PT results — and the reviewer must be someone other than the person who submitted them. CLIA expects the director’s involvement but does not always require the same separation of duties in the regulatory text.
In a small lab where one person submits and another reviews, this is trivial. In a small lab where the same person does both, you’ve quietly created a deficiency that compounds over years.
A side-by-side, the short version
| Topic | CLIA | CAP |
|---|---|---|
| Consecutive-failure trigger | 2 unsuccessful in 2 of 3 consecutive events | Per-analyte CAP-defined patterns |
| Review window | Operational expectation, not always explicit | 30 days from results-received, documented |
| PT integrity attestation | Required at submission | Required at submission, audited tightly |
| Effectiveness verification | Implied by “corrective action” | Explicit; closure must link to a subsequent acceptable result |
| Independent reviewer | Director involvement expected | Reviewer must differ from submitter |
What this means for the system you use
The reason this matters: if your PT program runs on a spreadsheet and an email folder, every one of these rules is something you have to remember to do. Miss a 30-day window once, miss an effectiveness link once, miss an attestation once — and you’ve created a finding.
A purpose-built EQA system should:
- Know which accreditation standard your lab operates under and apply the right consecutive-failure rule automatically
- Track the 30-day review window from the date results are received, and remind you before it lapses
- Block round submission until PT integrity is attested
- Block corrective-action closure until an effectiveness-verification result is nominated
- Enforce that the round reviewer is different from the result submitter
None of this is exotic. It’s just expensive to do by hand, and cheap to do once it’s encoded in software.
The takeaway
CAP and CLIA agree on the destination — defensible, traceable evidence that your laboratory’s PT performance is acceptable and that unacceptable results lead to documented improvement. They differ on the route: CAP is more prescriptive, CLIA is more outcome-focused. If you’re under both, run to the stricter rule on each axis and you won’t have to keep track of which one applies where.
Related reading:
- EQA / Proficiency Testing software for clinical labs — how CalibDue encodes the rules above
- How to prepare for a CAP inspection — the broader inspection-readiness checklist
- Building a competency program that passes inspection — the other half of every PT-related finding
