The Workbench · Craft

CLIA complexity decides who runs a test, not who sells it

A device team that gets an IVD cleared or approved has answered exactly one question: that the test can be marketed, for a stated intended use, on the evidence FDA reviewed under the 510(k), De Novo, or PMA track — the same evidence this blog has already covered for an IVD's post-market follow-up plan. Whether a laboratory is actually allowed to run that test once it ships is a second, separate question, decided under a different statute by a different part of the same agency: the Clinical Laboratory Improvement Amendments of 1988, implemented at 42 CFR Part 493. A launch checklist that stops at the clearance letter has cleared the test to exist. It hasn't cleared anyone to run it.

Two statutes, two questions

CLIA gives FDA a role most premarket teams don't otherwise deal with: categorizing every cleared or approved test system by how complex it is to perform correctly, a determination that sits on top of the marketing decision rather than inside it. The Food, Drug, and Cosmetic Act's clearance and approval pathways decide whether a device can be sold. CLIA's own categorization, run under a statute Congress passed to regulate laboratory testing quality rather than device marketing, decides which laboratories are legally permitted to perform it once it can be. A regulatory file that treats the clearance letter as the end of the story has closed the file one statute early.

One score, three categories

42 CFR 493.17 scores a test system against a fixed set of criteria — covering things like the knowledge and training the test demands, how much preparation its reagents and materials require, and how much independent judgment its interpretation calls for — and totals that score into one of three complexity categories: waived, moderate complexity, or high complexity. For a commercially available test going through FDA clearance or approval, FDA scores the test against these criteria as part of that same premarket review, and the category the score produces travels with the test from that point forward, attached to the cleared device rather than decided case-by-case by each lab that later buys it.

Waived by rule, or waived by asking

A test doesn't have to earn its way to the waived category through the scoring process every time. 42 CFR 493.15(c) waives specific tests by name in the regulation itself, and a test cleared or approved for home use or over-the-counter use is automatically categorized as waived on that basis alone. Everything else that scores as moderate complexity has one more route available: a manufacturer can file a CLIA Waiver by Application, asking FDA to reclassify a moderate-complexity test as waived by showing the statutory criteria Congress added in 2012 — that the test is simple to use, and that it poses an insignificant risk of an erroneous result in the hands of an untrained user. That's a second, separate FDA submission from the clearance itself, built around a different set of criteria than substantial equivalence or safety and effectiveness.

The category travels with the test; the certificate travels with the lab

A cleared test's complexity category only matters in practice once it meets the other half of CLIA's structure: the certificate a laboratory itself holds. A Certificate of Waiver covers only tests categorized as waived — a lab holding one can't add a moderate or high complexity test to its menu just because it purchased the instrument, no matter how straightforward the manufacturer's own instructions make the test look. Moderate and high complexity testing requires a different certificate type, with its own personnel qualification, quality control, and proficiency testing obligations attached. A go-to-market plan for a new IVD that only checks whether target customers can buy the device has skipped the question of whether their existing CLIA certificate actually covers running it.

Where this meets the file

A launch file for a new in vitro diagnostic has to carry the CLIA categorization letter as its own artifact, next to the clearance or approval order rather than folded into it — because the performance evidence a clearance decision rests on and the complexity score a categorization decision rests on answer to two different reviews inside FDA, on two different timelines, and a commercial rollout that assumes one letter covers both questions will find out the difference at the customer's own lab, not at FDA's desk. A launch checklist built around both letters, and the certificate types they imply for a target lab, is previewed in the launch catalog. If your program tracks this differently, the shelf takes that correction directly.

The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.

All Workbench notes