ASCA accredits the lab, not the 510(k) pathway

A submission plan that files ASCA next to Traditional, Special, and Abbreviated as a fourth 510(k) pathway option has misread what FDA actually built. The Accreditation Scheme for Conformity Assessment doesn't choose a pathway, and it doesn't compete with the declaration-of-conformity option inside an Abbreviated 510(k), even though both use the phrase “declaration of conformity.” ASCA answers a narrower and completely different question: which laboratory ran a given test, and against which FDA-recognized method. Section 514(d) of the Food, Drug, and Cosmetic Act, as amended by the FDA User Fee Reauthorization Act of 2022, moved ASCA from a multi-year pilot to a permanent, ongoing program — but a permanent accreditation scheme for laboratories is still not a submission type, and treating it as one misplaces where the actual decision lives.

What gets accredited is the lab, not the device

ASCA doesn't touch a device file directly. FDA recognizes accreditation bodies, which in turn accredit testing laboratories against a specific, FDA-defined scope: a named standard, and within it, the particular test methods FDA has agreed are suitable for the program. A laboratory earns ASCA accreditation for running specific tests to specific methods — not a general reputation for competent testing, and not a blanket credential that automatically covers every standard the lab happens to test against. A device manufacturer never applies to ASCA at all; the manufacturer's only choice is whether to send testing to a lab that already holds the accreditation for that particular method.

Two testing domains today, not a general seal

The program's scope is deliberately narrow. FDA built ASCA around biocompatibility testing — a defined set of the most common ISO 10993 test methods — and basic safety and essential performance testing under IEC 60601-1 and IEC 61010-1, expanding the electrical safety and EMC scope for in vitro diagnostic instruments in 2025 to add IEC 61326-2-6. A device whose testing sits outside those specific standards and methods gets nothing from ASCA yet, no matter how rigorous the lab that ran it. That scope grows by FDA rulemaking and standards-specific guidance, the same way FDA recognizes a standard's edition, not its title when a manufacturer cites conformity elsewhere — a method has to be named on FDA's own current list, not merely close to one that is.

What changes in the submission itself

Where testing does fall inside ASCA's scope and an accredited lab performed it, the submission carries three specific pieces FDA built the program around: an ASCA Declaration of Conformity, an ASCA Summary Test Report in FDA's own standardized format, and a cover letter identifying the ASCA content. That's a narrower, deeper substitution than the Abbreviated 510(k)'s ordinary declaration-of-conformity option, which lets a submission cite conformity to any recognized standard through any competent testing arrangement, accredited or not. ASCA trades that generality for a specific lab and a specific method, in exchange for a review FDA has pre-built its own summary format to move through faster — and the trade only pays off where the specific test actually sits inside the program's current scope.

Voluntary on both sides, and still supervised

Neither a laboratory's nor a manufacturer's participation in ASCA is mandatory, and using an ASCA-accredited lab doesn't stop FDA from asking for the underlying raw data behind a specific result if a reviewer has reason to. The accreditation itself stays under watch after it's granted, not treated as a one-time credential: FDA has withdrawn ASCA accreditation from laboratories that subsequently lost their underlying ISO/IEC 17025 accreditation, and publishes that withdrawal status on its own accredited-laboratory listing rather than leaving a stale accreditation shown as current. A submission plan that checks a lab's ASCA status once, at the time testing is ordered, and never revisits it is trusting a status FDA itself keeps live.

Where this meets the file

A test-planning tracker built around ASCA needs a field for the specific method within a standard — not just the standard's name, since ASCA's scope runs method by method — sitting next to the lab's current accreditation status, kept as a separate decision from whichever 510(k), De Novo, or PMA pathway the device is otherwise following. An ASCA eligibility worksheet built around the program's own recognized-method list is previewed in the launch catalog. If your lab-intake process checks this differently, the shelf takes that correction directly.