An accessory carries its own classification

A delivery catheter for a replacement heart valve is not, on its own, a device anyone would call Class III. It has no valve, makes no seal, replaces nothing. For a long stretch of FDA history it was regulated as one anyway — PMA review, full case — for exactly one reason: it was the accessory, and the device it accessorized was Class III.

The default this replaced

FDA’s longstanding working rule was administrative, not risk-based: an accessory took on the classification of the device it was meant to be used with, unless a regulation already classified that accessory distinctly. It was a simple rule and a blunt one — it put a genuinely low-risk accessory through the review burden of a high-risk device solely because of what the accessory plugged into, with no route to argue the accessory’s own risk profile said otherwise.

What the 2017 law changed

The FDA Reauthorization Act of 2017 added a new provision to Section 513 of the FD&C Act, codified at 21 U.S.C. § 360c(f)(6): FDA “shall classify an accessory…based on the risks of the accessory when used as intended and the level of regulatory controls necessary to provide a reasonable assurance of safety and effectiveness of the accessory, notwithstanding the classification of any other device with which such accessory is intended to be used.” The parent device’s class stopped being the default answer for its accessories. FDA finalized guidance on the new pathway in December 2017, building on a 2015 draft that had already been describing the same policy before Congress made it a statutory requirement.

The list this produced

FDA used the new authority on the existing inventory of accessories almost immediately: a 2018 Federal Register notice proposed a list of accessory types already on the market that were suitable for a distinct Class I classification, and a 2019 notice finalized it — each entry moving one specific accessory type out from under its parent device’s class and onto a classification, and a product code, of its own. A manufacturer with a genuinely new accessory type — one nothing in the classification database covers yet — requests one directly under 513(f)(6) itself, the same statute, rather than accepting the parent’s class by default.

The device on the label and the accessory beside it can now be two separate regulatory histories, filed under two separate product codes — and only one of them is the code a portfolio watch was built around.

The practice

A watch built on product codes only sees what that code touches. FDA Radar’s own matching works the same way — a product profile keys to one product code, plus whatever regulation number, application number, and firm are known for it — and nothing about watching a device’s own code extends automatically to an accessory that has since been given a distinct classification of its own. Whether a specific accessory has been reclassified, and what that means for a specific portfolio, is a question for a regulatory professional checking the classification database directly, entry by entry — this is regulatory intelligence and method, never regulatory advice about a specific device or its accessories.

FDA Radar derives a product’s profile from the classification database at signup and matches new items against the product code on file; see what we monitor and how often for the rest of the pipeline. An accessory reclassified under its own code is, to that profile, simply a code it was never given.