CLIA & CAP Validation Requirements: The Complete Guide

If you've ever tried to figure out exactly what your lab is required to do before putting a new test — or a new instrument, or a modified method — into clinical use, you've probably run into three different acronyms that all seem to say slightly different things: CLIA, CAP, and CLSI. This guide untangles how they fit together, and walks through what an actual validation or verification study needs to include.

CLIA, CAP, and CLSI — who does what

These three are not interchangeable, and understanding the difference makes the rest of this guide much easier to follow.

CLIA (the Clinical Laboratory Improvement Amendments of 1988) is the federal law. It's administered by CMS and sets the legal minimum every laboratory testing human specimens in the U.S. must meet — including the requirement, at 42 CFR §493.1253, that a lab verify or establish performance specifications for accuracy, precision, and reportable range before reporting patient results.

CAP (the College of American Pathologists) is one of several organizations CMS has "deemed" to accredit laboratories on its behalf. Instead of a direct CMS/state survey, a CAP-accredited lab is inspected against CAP's own checklists — which translate CLIA's broad legal language into specific, inspectable questions your lab has to answer with documentation.

CLSI (the Clinical and Laboratory Standards Institute) isn't a regulator at all — it's a standards organization. Its "EP" (Evaluation Protocol) documents are the accepted scientific methodology for how to actually perform a validation study. When a CAP checklist question asks whether you've verified precision, CLSI EP05-A3 is what tells you how many replicates, over how many days, and how to calculate the result.

In short: CLIA says you must do it, CAP checks that you did it, and CLSI tells you how to do it correctly.

Verification vs. validation — the distinction that changes everything

This is the single most common point of confusion, and it determines how much work you actually have to do.

Verification

Required when you're using an FDA-cleared or -approved test system, unmodified, exactly per the manufacturer's instructions. You're not proving new performance claims — you're confirming, with your own instrument, reagents, and operators, that you can reproduce what the manufacturer already established. This is a smaller study: typically accuracy, precision, and reportable range, and reference intervals if you're applying them to a new patient population.

Validation

Required for laboratory-developed tests (LDTs), high-complexity modified methods, or any test system used outside its cleared/approved conditions. Here your lab has to establish — not just confirm — performance characteristics from scratch: accuracy, precision, analytical sensitivity (LoB/LoD/LoQ), analytical specificity/interference, reportable range, and reference intervals, at minimum.

The core studies, and which CLSI document governs each

Whether you're validating or verifying, these are the performance characteristics regulators expect to see documented, and the CLSI protocol most labs use to evaluate each one:

When you need to re-verify (it's not just "once and done")

A validation or verification study isn't a one-time box you check when a test goes live. CAP expects you to re-verify performance in several situations:

• At least annually, even with no changes — most CAP checklists expect ongoing confirmation that performance hasn't drifted.
• After a major instrument repair or relocation.
• When you change to a new reagent lot with a significantly different formulation (not every routine lot change — check your own lot-to-lot policy and the manufacturer's package insert).
• After a software or firmware update that could affect result calculation.
• Any time you modify the test system, the specimen type, or the intended use.

Documentation — the part that actually gets cited

A technically sound study that isn't documented correctly is, from an inspector's point of view, indistinguishable from a study that was never done. At minimum, your documentation should show:

• The raw data and the calculated statistics (mean, SD, CV%, bias, etc.) — not just a pass/fail summary.
• The acceptance criteria you used, and where they came from (manufacturer claim, CLIA limit, or your own lab-defined goal).
• Who performed the study, and the date.
• Laboratory director (or designee) review and approval, with a signature and date — this is one of the most frequently cited gaps in CAP inspections.
• A clear link back to the procedure or SOP the study supports.

A simple pre-flight checklist

1. Confirm whether this is a verification or a full validation (see the distinction above).
2. Identify which performance characteristics apply to this test type (not every study applies to every assay — qualitative tests don't need a linearity study, for example).
3. Run the study using the appropriate CLSI protocol, with enough replicates/days to meet the minimum n for that protocol.
4. Compare your results against a documented acceptance criterion.
5. Get dated director review and sign-off before reporting patient results.
6. File it somewhere it can be found in under five minutes during an inspection — ideally as part of a master validation package per instrument, not scattered across individual folders.

This guide is educational and reflects general, widely accepted CLIA/CAP/CLSI practice as of 2026. Checklists and specific citation numbers are updated periodically — always verify against your lab's current CAP checklist and your accrediting body's latest requirements before relying on any specific citation.