The FDA LDT Rule Was Vacated: What Labs Need to Know in 2026

In March 2025 a federal court vacated the FDA's final rule on laboratory developed tests, and in September 2025 the agency rescinded it. For genetic and molecular labs, the practical headline is simple: CLIA is the operative compliance framework again, and the work of validating and documenting your tests now lives squarely under CLIA and CAP rather than the FDA's medical device regime.

What actually happened, and when

In May 2024 the FDA published a final rule asserting that laboratory developed tests (LDTs) are medical devices subop to FDA oversight, with a multi-stage phaseout intended to layer device requirements onto lab-developed assays over roughly four years. The American Clinical Laboratory Association and others challenged it in court.

On March 31, 2025, the U.S. District Court for the Eastern District of Texas vacated the rule in its entirety, holding that the FDA had exceeded its statutory authority. Rather than appeal, the FDA rescinded the rule through notice-and-comment, with the action taking effect September 19, 2025. The net result for 2026: the phaseout deadlines, the device classifications, and the registration-and-listing obligations the rule would have imposed are gone.

Why CLIA being "operative again" is the real story

Vacatur did not create a regulatory vacuum. It returned LDT oversight to where it sat before May 2024: the Clinical Laboratory Improvement Amendments (CLIA), administered by CMS, and the deemed accreditation programs that enforce CLIA in practice, chiefly CAP. CLIA never stopped applying; the FDA rule would have added a second, parallel layer on top of it. Removing that layer means labs plan around one framework, not two.

This matters for how a lab presents itself. A CLIA certificate and, where applicable, CAP accreditation are once again the current, sufficient credentials for offering an LDT, not a placeholder while waiting on FDA clearance. Labrynix is built by the team behind Gene Matrix AI, a CLIA-certified genetic lab, which is part of why the platform is designed around CLIA and CAP workflows rather than device-submission paperwork.

What this changes for your validation obligations

Here is the part that gets misread: the vacatur removed an oversight layer, not the duty to validate. Under CLIA, before a laboratory reports patient results from a non-waived LDT, it must establish performance specifications for the test and verify them. For a lab-developed assay that typically means documenting:

• Accuracy and precision
• Analytical sensitivity and specificity, including known interferents
• Reportable range and, where relevant, the limit of detection
• Reference intervals or reportable ranges appropriate to the patient population
• Any other performance characteristic required for the test to be used safely

CAP-accredited laboratories document these against the applicable checklist requirements and keep the evidence available for inspection. None of that changed in 2025. If anything, the vacatur makes CLIA and CAP documentation the single source of truth for whether a test is fit for clinical use, so the quality of that documentation carries more weight, not less.

Reimbursement is a separate track, and it did not move

It is easy to conflate "can I offer this test" with "will I get paid for it." They run on different rails. The vacatur addressed the first question. The second is governed by coverage and coding rules that the court case did not touch. For molecular tests, that means MolDX and the DEX registry: Medicare and major commercial payers continue to require a Z-code to adjudicate molecular claims, and claims submitted without the correct Z-code, CPT mapping, and an aligned Technical Assessment are routinely denied.

So a lab can be fully compliant under CLIA to run a molecular LDT and still leave revenue on the table if its Z-code and prior-authorization workflow is not tight. If denials are a live problem for you, the mechanics of CPT-in-DEX mapping and Z-code submission are worth a closer look at how Labrynix billing handles MolDX Z-codes and denials, because the regulatory change does nothing to ease the coding burden.

What to look for in software now: documentation that survives inspection

With CLIA and CAP as the operative framework, the most useful question to ask of any lab system is unglamorous: does it help you produce and defend an audit trail? An inspector does not want a marketing claim that a test is validated; they want the records. That puts a few concrete capabilities on the checklist when you evaluate a genetic and molecular LIS/LIMS:

• Validation and verification records that live with the test. Performance specifications, validation studies, and approvals should be attached to the assay and retrievable, not scattered across shared drives and email.
• Immutable audit trails. Who changed what, when, and why, including result edits and report amendments, captured automatically rather than reconstructed after the fact.
• Version control on tests, reagents, and reports. When an assay or report template changes, the system should show what the configuration was on the date any given patient result was reported.
• Documented sign-out and human review. CLIA and CAP expect qualified personnel to review and release results. Software should record that a credentialed human approved each report, not paper over it.
• Access controls and security evidence. Role-based permissions, authentication, and an access log you can show an auditor.

That last point is where compliance and data protection overlap. CAP checklists and HIPAA both expect demonstrable controls over who can reach patient data, which is why it is worth reviewing a vendor's security and compliance posture alongside its feature list. The capabilities that make an inspection go smoothly are largely the same ones that keep protected health information protected.

Where AI fits without crossing a line

None of this changes the rule that matters most for clinical AI: software assists, qualified lab staff validate, approve, and sign out, and the AI never makes the clinical decision. The regulatory shift to CLIA actually sharpens that boundary, because CLIA and CAP are explicit that named, qualified personnel are accountable for released results. A well-designed platform uses a lab-trained AI layer on leading models to draft, flag, and accelerate, while routing every report through human review and recording that review in the audit trail.

If you want to see how the documentation, sign-out, and audit pieces fit together across the LIS, reporting, and billing modules, the full Labrynix platform overview walks through it end to end. The regulatory picture in 2026 is clearer than it has been in years: validate under CLIA, document for CAP, code correctly for MolDX, and choose software that makes all three provable.

Frequently asked questions

Is the FDA LDT rule still in effect in 2026?

No. The U.S. District Court for the Eastern District of Texas vacated the FDA's laboratory developed test (LDT) final rule on March 31, 2025, and the FDA formally rescinded the rule on September 19, 2025. As of 2026, the rule's phaseout timeline and device requirements no longer apply, and laboratory developed tests are once again regulated primarily under CLIA rather than the FDA's medical device framework.

What framework regulates laboratory developed tests now?

CLIA, administered by CMS, is the operative federal framework for laboratory developed tests again, and accreditation bodies such as CAP enforce it through detailed checklists. Labs validate each LDT for analytical performance (accuracy, precision, reportable range, reference intervals, and other characteristics) before clinical use and maintain that documentation for inspection. Reimbursement is a separate matter: Medicare and major commercial payers still require MolDX/DEX Z-codes for molecular claims.

Does the vacatur mean labs no longer need to validate their LDTs?

No. Validation obligations did not disappear; they reverted to CLIA and accreditation requirements. Under CLIA, a laboratory that introduces a non-waived LDT must establish performance specifications and verify them before reporting patient results, and CAP-accredited labs document this against the relevant checklist requirements. The vacatur removed the FDA device layer, not the underlying duty to prove a test performs as intended and to keep the records that show it.