Autor: adminarya

FDA 510(k) medical device clearance is the route most manufacturers use to legally place a device on the US market, and it hinges on one argument: that your device is substantially equivalent to a device already being sold legally. That single word — equivalence — decides whether your submission moves through FDA’s review in a matter of months or comes back with an Additional Information request that resets the clock. A 510(k) is not a rubber stamp and it is not a formality bolted onto product launch; it is a technical and legal argument that has to be built correctly from the predicate up.

What a 510(k) actually is

A premarket notification, commonly called a 510(k) after Section 510(k) of the Federal Food, Drug, and Cosmetic Act, is the submission a manufacturer files with FDA to demonstrate that a device is as safe and effective as — substantially equivalent to — a legally marketed predicate device that does not require premarket approval (PMA). The procedural requirements sit in 21 CFR Part 807, Subpart E, which sets out when a submission is required (§ 807.81), what must be included (§ 807.87), the required format (§ 807.90) and how FDA acts on it (§ 807.100). Most manufacturers required to register their establishment under Part 807 must also submit a 510(k) at least 90 days before introducing the device into commercial distribution, unless a specific exemption applies.

Substantial equivalence, under FDA’s own framework, means the device has the same intended use as the predicate and either the same technological characteristics, or different technological characteristics that do not raise different questions of safety and effectiveness — provided the performance data submitted demonstrates the device is as safe and effective as the predicate. It does not mean identical. It means the differences, if any, do not introduce new questions FDA has to resolve from scratch.

Which devices need one

Device classification drives the pathway. Class I devices are largely exempt from 510(k) in practice, though not automatically — exemption status has to be verified against the specific product code, not assumed from the class alone. Class II is where the 510(k) does most of its work: it is the standard premarket pathway for the majority of Class II device types, alongside device-specific exemptions that also need to be checked individually. Class III devices, which sustain or support life, are implanted, or present a potential unreasonable risk, generally require Premarket Approval (PMA) rather than a 510(k) — with a narrowing set of legacy exceptions still working through 510(k). In our experience, the single most common strategic error we see from manufacturers arriving from outside the US is treating device classification as self-evident from how the product is classified in the EU under the MDR. It rarely maps cleanly, and getting the US product code wrong early cascades into every decision that follows — predicate search, testing scope, even which submission type applies.

The three types of 510(k), and when each one applies

Not every 510(k) is built the same way, and choosing the wrong type is a common source of avoidable delay.

The Traditional 510(k) is the default and the most heavily used pathway. It requires a full substantial equivalence comparison against the predicate, complete performance data, and the most comprehensive documentation package of the three. Use it when the device is genuinely new to your company’s portfolio, the predicate relationship is not a simple modification, or the device does not cleanly qualify for either of the other two routes.

The Special 510(k) exists for a narrower case: a manufacturer modifying its own already-cleared device, where the change can be evaluated using the manufacturer’s own design control procedures under 21 CFR Part 820. It is the fastest of the three routes, but it is only available when the modification does not alter the fundamental scientific technology of the device and the existing risk analysis and verification/validation methods can support the change. A manufacturer discovering mid-review that its “minor modification” is not eligible for Special 510(k) treatment loses time it did not need to lose.

The Abbreviated 510(k) relies on FDA guidance documents, special controls, or recognized consensus standards instead of a full head-to-head predicate comparison. Instead of reproducing extensive predicate data, the submitter provides summary reports and declarations of conformity to recognized standards. It works well for device types where FDA has already published clear special controls or a device-specific guidance document, and it can meaningfully shorten what has to be written and reviewed — but only if the device genuinely fits within the guidance’s scope.

Picking among the three is a strategic decision, not an administrative one. Get it wrong and FDA does not gently redirect you; it stops the clock and asks you to justify the choice, or rejects the submission at acceptance review before substantive review even starts.

Refuse to Accept: where most avoidable delay happens

Before FDA reviewers ever evaluate whether your device is substantially equivalent, the submission goes through an acceptance review against the Refuse to Accept (RTA) checklist. This is a binary administrative-completeness gate, not a scientific judgment: FDA checks the submission against the applicable checklist — Traditional, Abbreviated or Special each has its own — covering administrative information, device description, the substantial equivalence discussion, proposed labeling, and, where relevant, sterilization, shelf-life, biocompatibility, software, cybersecurity, electrical safety/EMC and performance data. FDA notifies the submitter within the first calendar days after receipt whether the submission is administratively complete or which specific elements are missing.

Is this a technicality or a real risk? It is both, and that is exactly the problem. A submission bounced at RTA has not failed on the merits — it has failed on completeness, often over something as mechanical as a missing labeling section or an incomplete substantial equivalence table. But the practical effect is identical to a substantive rejection: the review clock has not started, and the manufacturer is back at the start of the queue. We have seen manufacturers with genuinely strong technical files lose months to RTA issues that had nothing to do with whether their device actually worked.

Timelines and user fees

FDA’s stated performance goal under the current Medical Device User Fee Amendments (MDUFA) framework is to reach a decision on the large majority of Traditional 510(k) submissions within roughly 90 FDA days — calendar days net of any time the submission sits on hold while FDA waits for an Additional Information response. That clock-stopping mechanic matters more than the headline number: every Additional Information request pauses the countdown, so a submission that generates two or three rounds of FDA questions can take substantially longer in real time than the stated goal suggests, even though the “FDA days” figure looks compliant on paper. Special 510(k)s are reviewed on a materially shorter track; Abbreviated 510(k)s sit closer to Traditional in practice, depending on how much the guidance-based summary approach actually reduces review burden for that device type.

Submissions are also subject to a Medical Device User Fee, reassessed annually by FDA, with a reduced fee available to businesses that qualify through FDA’s Small Business Determination (SBD) program. Qualification has its own filing deadline ahead of the fiscal year it applies to, and missing that window means paying the standard fee regardless of company size — a detail that catches manufacturers who assume small-business status is automatic.

No predicate? The De Novo pathway

Not every innovative device has a fair predicate to point to, and forcing an equivalence argument onto a device that is not truly equivalent to anything on the market is a losing strategy. For low-to-moderate-risk devices with no legally marketed predicate, FDA’s De Novo classification request lets the agency evaluate the device on its own merits rather than by comparison. If FDA agrees that general and special controls are sufficient to reasonably assure safety and effectiveness, it grants the De Novo request and creates a new device classification and product code — which then becomes a predicate that later devices, including your own next generation, can cite in a standard 510(k). A De Novo request can be filed directly, or after FDA issues a Not Substantially Equivalent (NSE) decision on a prior 510(k) attempt. Recognizing early that De Novo, not a forced 510(k), is the right pathway saves a manufacturer an entire review cycle it did not need to spend.

Practical checklist before you file

• Confirm the device classification and product code against FDA’s own classification database — not against the EU MDR classification, which does not map directly.
• Identify and justify one or more predicates that share intended use and, where technology differs, show the difference raises no new safety or effectiveness questions.
• Decide the submission type — Traditional, Special or Abbreviated — based on what the modification and available guidance actually support, not on which is fastest to write.
• Run the submission against the applicable RTA checklist before filing, section by section, including labeling, biocompatibility, software and cybersecurity where relevant.
• Build the substantial equivalence comparison as a structured, side-by-side technical argument, not a narrative summary.
• Confirm Small Business Determination eligibility and file it ahead of the FDA deadline if it applies to you.
• Plan for at least one round of Additional Information requests in your commercial timeline — and have the technical team ready to respond inside FDA’s response window.

How ASC Services gets your device cleared

Knowing what FDA requires is the easy part; it is published. What decides whether a 510(k) clears on the first cycle or drags through two or three rounds of Additional Information is the work behind it — and that is where we operate. We run the predicate search and build the equivalence strategy before a single test is commissioned, so the technical program is built around a defensible comparison rather than retrofitted to one. We run a gap analysis of your existing technical file against what the chosen predicate and submission type demand, so testing gaps surface before FDA finds them. We prepare the full submission package — device description, substantial equivalence comparison, labeling, performance data — screened against the same RTA checklist FDA itself uses, and we draft the response when FDA comes back with questions, because how that response is framed often determines whether it closes the issue or opens a second one.

Every submission we prepare is validated and signed off by a qualified ASC regulatory professional before it goes to FDA — not generated and shipped by a tool with no one accountable for it. That is the same standard we apply across two decades and hundreds of approved regulatory dossiers on both sides of the Atlantic: for manufacturers already navigating the EU technical file requirements under the MDR, our guide on why notified bodies reject MDR technical documentation covers the equivalent pressure points on the European side. If you are preparing to bring a device to the US market, talk to us through our contact page, or see the full scope of what we handle for regulated manufacturers on our consultancy services page.

Frequently Asked Questions

How long does FDA 510(k) clearance actually take?

FDA’s stated performance goal for a Traditional 510(k) is a decision within roughly 90 FDA days, but that clock stops every time FDA places the submission on hold for an Additional Information request. A clean submission with no Additional Information rounds can land close to the goal; a submission that generates two or three rounds of questions can run well beyond it in real calendar time, even though it stays within the technical FDA-days goal.

Can I use a predicate device that is not exactly like mine?

Yes — substantial equivalence does not require an identical device. It requires the same intended use and either matching technological characteristics or differences that do not raise new questions of safety and effectiveness, supported by data. A predicate chosen for commercial similarity rather than genuine regulatory alignment is one of the most common reasons submissions stall.

What happens if my 510(k) gets a Refuse to Accept notice?

The submission is administratively incomplete against the applicable RTA checklist and has not entered substantive review. FDA identifies the missing elements; you correct and resubmit. The review clock has not started, so an RTA bounce, while not a rejection on the merits, still costs real time.

What if there is no predicate for my device at all?

That is exactly the case the De Novo classification pathway exists for: FDA evaluates the device on its own merits rather than by comparison, and a successful request creates a new device classification that later submissions, including your own, can then use as a predicate.