CLIA and CAP: What Your Records Actually Have to Show
What CLIA and CAP require your laboratory records to show, which body applies to you, and the evidence an inspection expects your system to produce.
Vendors sell "CLIA-compliant software", which is not a thing that exists. CLIA certificates are held by laboratories, not by applications. What software can do is make the records an inspector asks for easy to produce — or make them impossible.
The quick answer
CLIA is the US federal regulatory standard covering testing on human specimens; a certificate is required to report patient results at all. CAP accreditation is a separate voluntary programme with detailed checklists that can satisfy CLIA requirements through deemed status. One is the licence to operate; the other is a quality credential you choose.
| CLIA | CAP | |
|---|---|---|
| Nature | Federal regulation | Voluntary accreditation |
| Required to report results | Yes | No |
| Held by | The laboratory | The laboratory |
| Can satisfy the other | n/a | Yes, via deemed status |
| Examines | Personnel, QC, records | The same, by detailed checklist |
What an inspector actually asks for
Strip away the checklist language and the questions are consistent, and every one of them is a records question rather than an opinion about your software.
- Who performed this test, and were they qualified to perform it on that date?
- Was quality control in range for the run this patient result came from?
- Who released the result, and when?
- This result was corrected — what was the original value, who changed it, and why?
- Show me this patient's report exactly as the clinician received it.
- How do you know this specimen is the one the order was placed for?
A laboratory system that cannot answer the fourth question is the common failure. Software that lets a verified result be edited in place produces a record that says what the value is now, and says nothing about what the clinician saw last Tuesday.
That is why a result revision history matters more than it sounds: a verified value should lock, and an amendment should keep the original alongside the reason. The mechanics of how a result gets from the instrument to that locked state are covered under analyzer interfacing, and what is and is not claimed about data handling is set out on the security page.
Where laboratory software genuinely helps
- Barcoded specimen traceability, so specimen identity is a scan rather than a recollection.
- IQC stored per analyte and per instrument, so "was QC in range for this run" is a lookup.
- An audit log that records who did what and when, without anyone having to remember to write it down.
- Report templates that produce the same output for every operator, so the report an inspector sees is the report that went out.
- A revision history where a verified result locks and an amendment is visible as an amendment.
Where it does not
No system supplies personnel competency assessment, a procedure manual, proficiency testing enrolment, or the judgement of a laboratory director. Those are the parts that take a laboratory time, and a vendor implying otherwise has told you something you will discover is untrue at the worst moment.
Be equally careful with the phrase "audit-ready". It means the system holds records; it does not mean anyone has audited it. Ask any vendor plainly whether they hold ISO 27001 or SOC 2, and whether they sign a BAA — and take a clear no over a vague yes.
Frequently asked questions
Is any laboratory software CLIA certified?+
No. CLIA certificates are issued to laboratories, not to software, so "CLIA-certified software" describes something that does not exist. What a laboratory system can do is produce and retain the records a CLIA survey examines — personnel attribution, quality control per run, verification, and a traceable amendment history.
What is the difference between CLIA and CAP?+
CLIA is US federal regulation and a certificate is required before you can report patient results at all. CAP accreditation is voluntary, checklist-driven and inspected on a cycle, and it can satisfy CLIA requirements through deemed status. One is permission to operate; the other is a quality credential a laboratory chooses to pursue.
Does my LIS need to store quality control results?+
It needs to make them retrievable against the run they belong to, because the question asked at inspection is whether QC was in range for the run that produced a specific patient result. Storing controls in a separate spreadsheet technically satisfies "we keep them" and fails the question actually asked.
Keep reading
- NABL Report Format: Every Field, and Why Each One Is There
A NABL report is not a design problem. It is a list of facts an assessor expects to find, laid out so a clinician can read it quickly.
- LIMS Software in India: What Labs Search vs What They Need
Most Indian labs typing "LIMS" are running a diagnostic lab, and a diagnostic lab wants a LIS. Buying the wrong category is expensive in a specific way.
- ASTM, HL7 and LIS2-A2: How Analyzers Talk to Software
Analyzer integration sounds like magic and is mostly two standards, a cable and a field map. Knowing which is which makes vendor conversations much shorter.