The 510(k) is the FDA premarket notification pathway used for most Class II medical devices entering the United States. The core analytical move is demonstrating substantial equivalence: showing that the new device has the same intended use as a legally marketed predicate device and either the same technological characteristics, or different characteristics that do not raise different questions of safety and effectiveness. A 510(k) clearance is not an FDA approval and it is not a CE mark. It is a specific US regulatory outcome under a specific US legal framework, and for EU founders it is usually the first FDA pathway worth understanding because it is where most of the US device market actually lives.

By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.

TL;DR

  • A 510(k) is an FDA premarket notification, not an approval. The FDA issues a clearance letter when it agrees the device is substantially equivalent to a legally marketed predicate.
  • Substantial equivalence is the engine of the pathway. It rests on two pillars: same intended use as the predicate, and same or comparable technological characteristics that do not raise different safety or effectiveness questions.
  • Predicate selection is the most consequential strategic decision in a 510(k). The wrong predicate produces rework, delay, and in the worst case a Not Substantially Equivalent finding.
  • A 510(k) submission is organised around a structured set of sections covering device description, intended use, predicate comparison, performance testing, software where applicable, labelling, and sometimes clinical data.
  • Timelines and costs depend on the device, the quality of the submission, and the review division. Neither is reliably predictable from a primer. Both reward clean, complete, internally consistent submissions disproportionately over rushed ones.
  • The 510(k) is not a fit for every EU startup. It is the right pathway when a valid predicate exists and the device sits within the Class II risk range. It is the wrong pathway when the device is genuinely novel, when the intended use diverges materially from anything on the US market, or when the risk profile pushes into PMA territory.

Why this pathway matters for EU founders

Most EU founders encounter the 510(k) as a name long before they understand what it does. It shows up in pitch decks as "we will do a 510(k)." It shows up in investor questions as "what is your 510(k) timeline." It shows up in consultant conversations as the default US pathway, mentioned casually, as if everyone already agreed what it means. Very few founders, in Tibor's experience, can actually describe the process when asked to slow down and explain it.

That is a problem. The 510(k) is the single most common route to the US device market, and the founders who treat it as a black box end up making three kinds of avoidable mistakes. They pick the wrong predicate because they have not thought carefully about intended use. They underestimate the submission content because they assume it is lighter than it actually is. Or they assume an EU technical documentation package can be translated into a 510(k) like a document is translated between languages, rather than rebuilt for a different reviewer with a different logic.

This post is the orientation layer. It is deliberately written at a general framing level. For the specific predicate, the specific product code, the specific review division, the specific content of your submission, and the specific current FDA expectations in your device category, work with a US regulatory specialist who practices inside the FDA system daily. Tibor does not hold himself out as an FDA expert, and this blog stays honest about that boundary.

What a 510(k) is, at a high level

A 510(k) is a premarket notification filed with the FDA before a device is marketed in the United States. The name comes from the section of the US Food, Drug, and Cosmetic Act that established the premarket notification requirement. In practice, a 510(k) is a structured submission to the FDA's Center for Devices and Radiological Health (CDRH) that asks the agency to agree that the new device is substantially equivalent to a legally marketed predicate device.

If the FDA agrees, it issues a clearance letter. The device can then be placed on the US market under the intended use described in the submission, produced under a quality system that meets the FDA's Quality System Regulation at 21 CFR Part 820, and subjected to the ongoing FDA post-market obligations that apply to cleared devices.

A few things the 510(k) is not, because the vocabulary is consistently misused:

  • It is not an FDA approval. Approval is the outcome of a Premarket Approval (PMA) application, which is a different, more stringent pathway used for most Class III devices.
  • It is not a finding that the device is safe and effective in the absolute sense. It is a finding that the device is as safe and as effective as a legally marketed predicate. A comparative judgement, not an absolute one.
  • It is not a marketing authorisation issued as a favour or a formality. The FDA reviews the submission, can and does ask for more information, and can issue a Not Substantially Equivalent finding when the argument does not hold.

For the higher-level framing of where 510(k) sits among the FDA pathways, see FDA regulation of medical devices: a primer for EU startups. For the side-by-side against CE marking, see FDA 510(k) vs. MDR CE marking: a side-by-side comparison for startups.

Substantial equivalence: the engine of the pathway

Substantial equivalence is the analytical core of every 510(k). It rests on a comparison between the new device and a legally marketed predicate along two dimensions.

The first dimension is intended use. The new device must have the same intended use as the predicate. Not similar. Not overlapping. The same. Intended use on the FDA side plays a role comparable to intended purpose under MDR Article 2(12): it is the anchor that defines what the device is, what it is for, and who it is meant to be used by. Drift in intended use between the new device and the predicate is the single most common reason a 510(k) runs into trouble.

The second dimension is technological characteristics. Either the new device has the same technological characteristics as the predicate, or it has different characteristics that do not raise different questions of safety and effectiveness compared with the predicate. The second option is where most real 510(k) submissions live, because in practice almost every new device differs from its predicate in some technical way. The question is whether those differences matter for safety and effectiveness, and the answer is built through performance testing and a structured comparison.

A 510(k) that tries to paper over a material difference in intended use or in risk-relevant technology is a 510(k) that invites questions from the review division and, in the worst cases, a Not Substantially Equivalent finding. A Not Substantially Equivalent finding does not end the device's US prospects. It can push the project into the De Novo pathway. But it is a costly detour and it usually reflects a weakness in the original predicate strategy.

Predicate device strategy

Picking the predicate is the most consequential single decision in a 510(k) and the one EU founders most often get wrong when they try to run the pathway without US-specific help.

A valid predicate is a device that has been legally marketed in the United States and that the applicant can compare their new device against credibly along the two substantial equivalence dimensions. A strong predicate strategy considers at least the following:

  • Intended use fit. The predicate's cleared intended use is close enough to the new device's intended use that the comparison is not forced.
  • Technological proximity. The predicate is built on a technology that is close enough to the new device that the performance testing required to bridge the differences is feasible with a reasonable budget.
  • Review history. The predicate's own clearance history, post-market performance, and any related FDA communications do not signal that the technology is under increased scrutiny.
  • Product code alignment. The device falls within the same FDA product code as the predicate, or there is a defensible argument for the product code the submission will use.
  • Currency. The predicate is still on the market and has not been withdrawn, recalled, or otherwise compromised in a way that would weaken the comparison.

Founders sometimes assume that any cleared device in a vaguely similar space is a valid predicate. It is not. A US regulatory specialist will typically screen several candidate predicates, rank them, and pick the one that produces the cleanest comparison with the lowest testing burden. Doing this well is the difference between a 510(k) that moves through review in a predictable window and one that spins through multiple rounds of additional information requests.

For a deeper discussion of classification logic on the US side, see FDA device classification for EU startups.

Submission structure at the general framing level

A 510(k) submission is organised around a structured set of sections. Described at the general framing level, the content typically includes:

  • Administrative and cover information. Contact details, submitter identity, device name, establishment registration information, and the US Agent designation for foreign manufacturers.
  • Device description. What the device is, what it is made of, how it works, and how it is used.
  • Indications for use statement. The FDA-facing articulation of the intended use, drafted with unusual care because it becomes the cleared label language.
  • Substantial equivalence discussion. The comparison with the chosen predicate across intended use and technological characteristics, usually including a comparison table and a narrative.
  • Performance data. Bench testing, biocompatibility where relevant, electrical safety and electromagnetic compatibility for electrical devices, sterility and shelf life where relevant, software verification and validation for software-containing devices.
  • Clinical data when required. Many 510(k)s do not include clinical data. Some do, either because the device category routinely requires it or because bench and performance data are insufficient to resolve the substantial equivalence question.
  • Labelling. The proposed labelling, including the instructions for use and any patient-facing information, drafted in line with FDA labelling expectations.
  • Quality system information. The submission is not a full QMS audit, but it connects to the manufacturer's quality system, which must meet 21 CFR Part 820.

Two administrative layers matter from day one for EU manufacturers. First, foreign manufacturers are required to designate a US Agent who serves as the FDA's point of contact in the United States. Second, FDA establishment registration and device listing obligations apply in parallel with the premarket notification and are not optional. Your US regulatory specialist will walk through both on the first structured call.

At the content level, the submission must be internally consistent across sections. Inconsistencies between the device description, the indications for use, the predicate comparison, and the performance data are one of the most common drivers of additional information requests from the review division.

Timeline reality

Founders want a single number for 510(k) timeline. There is no honest single number. The actual elapsed time between submission and clearance depends on the device, the review division, the quality of the submission, whether the FDA issues additional information requests, and how quickly the applicant responds when they do. A clean, well-prepared submission with a strong predicate and a review division that is comfortable with the technology can move through review in a relatively predictable window. A weak submission, an unusual device, or a review division that is currently dealing with higher volume can stretch the timeline significantly.

What is predictable is the shape of the timeline. The work before submission. Predicate research, testing, QMS alignment, draft preparation, internal review. Is itself months of activity and is often longer than the review phase. The review phase includes an administrative acceptance check, a substantive review, and one or more rounds of interactive review or formal additional information requests. Each round of additional information pauses the review clock and can add weeks or months depending on the complexity of the question and the applicant's response time.

The practical planning rule: treat the 510(k) as a multi-quarter programme from "we have locked the intended use" to "we have the clearance letter." Shorter plans tend to be wish-casting rather than planning. Longer plans are sometimes justified, particularly for devices with novel elements that push at the edges of the predicate.

Cost framing

Cost for a 510(k) breaks into buckets that need to be budgeted separately.

  • FDA user fee. Every 510(k) submission carries a user fee set by the FDA under its user fee programme. The fee is published by the agency and updated periodically. Small businesses can qualify for a reduced fee under FDA rules. Current amounts belong on the FDA website, not in a primer that will outlive the fee schedule.
  • US regulatory consulting. Predicate strategy, submission drafting, FDA interaction, and response to additional information requests. This is usually the single largest cost bucket and is also where the investment produces the most leverage.
  • Testing. Bench performance, biocompatibility, electrical safety and EMC for electrical devices, software verification and validation, sterility and shelf life where relevant. Testing is often reusable across EU and US submissions when the test plans were written with both regulators in mind.
  • QMS implementation. Part 820 alignment, inspection readiness, and any gap closure from an existing ISO 13485 base.
  • Clinical data when required. When clinical data is needed, it becomes the dominant cost bucket and pushes timelines out significantly.
  • Labelling and regulatory operations. US Agent, establishment registration, device listing, labelling review, and associated administrative work.

The frame that works for founders is not "what does a 510(k) cost" but "what do the buckets for my specific device look like, and which of them overlap with the CE marking work I am already doing or have already done." For a dual-market cost discussion, see The Subtract to Ship framework for MDR and the dual-market sections of FDA 510(k) vs. MDR CE marking.

When a 510(k) makes sense for an EU startup

The 510(k) is a good fit when:

  • The United States is a real, budgeted part of the business plan with a target launch window.
  • The device sits in the Class II risk range under US logic, confirmed by a US regulatory specialist rather than inferred from MDR classification.
  • A valid predicate exists, and the intended use and technological characteristics of the new device allow a credible substantial equivalence argument.
  • The performance testing needed to bridge the differences from the predicate is feasible within the startup's budget and timeline.
  • The team has, or can plausibly acquire, a QMS that satisfies 21 CFR Part 820 at implementation level. Not just on paper.

When these conditions line up, the 510(k) is often the fastest honest route into the US market, and the underlying work overlaps meaningfully with the CE marking programme: risk management, bench testing, biocompatibility, EMC and electrical safety, software verification, and the broader QMS foundation.

When a 510(k) does not make sense

The 510(k) is the wrong pathway when:

  • No valid predicate exists. A forced predicate produces a weak substantial equivalence argument and invites a Not Substantially Equivalent finding. The De Novo pathway is the correct route for genuinely novel low-to-moderate risk devices.
  • The device's risk profile pushes it into Class III territory under US logic. A PMA, not a 510(k), is the right pathway. Trying to 510(k) a PMA-class device is not a creative interpretation. It is a dead end.
  • The intended use diverges materially from anything on the US market in ways that cannot be resolved by testing. Intended use drift is the primary reason 510(k) submissions fail on substantial equivalence.
  • The United States is not actually in the plan. A speculative 510(k) run "because investors want to hear it" burns cash that should be going to the markets the company is actually serving.

The honest conversation about fit belongs at the start of the project, not after three months of draft submission work. A single structured meeting with a US regulatory specialist, held early, resolves the fit question reliably and prevents the larger, more expensive mistakes further downstream.

The Subtract to Ship angle on the 510(k)

The Subtract to Ship framework. Strip every activity that does not trace to a specific regulatory obligation. Applies to 510(k) work the same way it applies to MDR work. The discipline is to remove the speculative effort and keep the required effort. On the 510(k) side, the most common waste to subtract is:

  • Speculative drafting against a predicate that has not been validated by a specialist.
  • Performance testing designed only to "look thorough" rather than to resolve a specific substantial equivalence question.
  • QMS rebuilds driven by fear rather than by a real gap analysis between the existing ISO 13485 implementation and Part 820 expectations.
  • Clinical investigation work added because "the FDA might want it" rather than because the specific device category requires it.

The underlying work. Predicate strategy, intended use clarity, performance data, QMS alignment, submission drafting. Still has to happen. Subtract to Ship does not cut regulatory work. It cuts regulatory theatre that is disguised as regulatory work. See The Subtract to Ship framework for MDR for the foundational methodology.

Reality Check. Is a 510(k) actually your pathway?

  1. Is the United States in your business plan with a target launch window and a revenue assumption, or is it a vague future item?
  2. Have you identified candidate predicate devices for your intended use, or are you assuming a predicate exists because the technology is common?
  3. Is the intended use for the US submission drafted and locked, consistent with the intended purpose under MDR Article 2(12)?
  4. Do you have a US regulatory specialist identified and scoped, or are you planning to self-navigate the pathway question?
  5. Have you mapped the performance testing you will need for a 510(k) against the testing you already plan to do for CE marking, to find the overlaps?
  6. Do you know whether your device category routinely requires clinical data on the US side, or are you assuming it will not?
  7. Is your QMS being built with 21 CFR Part 820 in mind from the start, or only against ISO 13485?
  8. If an FDA reviewer asked you tomorrow why your predicate is the right predicate, could you answer in two clear sentences?

If you cannot answer more than four of these eight clearly, the 510(k) is a name in your deck, not a plan. That is fine if you own it and fix it. It is dangerous if you are telling investors otherwise.

Frequently Asked Questions

Is a 510(k) clearance the same as FDA approval? No. A 510(k) clearance is a finding that a device is substantially equivalent to a legally marketed predicate. FDA approval is the outcome of a Premarket Approval (PMA) application, which is a different, more stringent pathway used for most Class III devices. The two are often conflated in casual conversation, but the distinction matters legally and practically.

Can any cleared device serve as a predicate for my 510(k)? No. A valid predicate is a legally marketed device whose intended use matches your device's intended use and whose technological characteristics allow a credible substantial equivalence comparison. Predicate selection is a strategic decision that benefits from US specialist input. A weak predicate choice is the most common cause of delayed or failed 510(k) submissions.

Do I need clinical data for a 510(k)? Often not. The 510(k) pathway is built on substantial equivalence to a predicate, and for many device categories the performance data needed to support the comparison is bench testing, biocompatibility, electrical safety and EMC, and software verification. The FDA can and does request clinical data when these are insufficient, and certain device categories routinely require it. A US regulatory specialist can answer the clinical data question for your specific device and product code.

How long does a 510(k) take from submission to clearance? It depends on the device, the review division, the strength of the submission, and whether the FDA issues additional information requests. A clean submission with a strong predicate and a receptive review division can move through review in a relatively predictable window. A weak submission or an unusual device can stretch significantly. Plan in quarters, not weeks, and budget contingency for additional information rounds.

Does an ISO 13485 QMS satisfy the FDA's quality system requirements for a 510(k)? It is a strong base, but it is not automatically sufficient. The FDA's Quality System Regulation at 21 CFR Part 820 has specific requirements and inspection expectations. The FDA is moving Part 820 closer to ISO 13485 through its QMSR harmonisation initiative, but EU manufacturers should still plan for a gap analysis and close any Part 820-specific gaps before FDA inspection. The current status of the harmonisation timeline belongs on the FDA's own guidance pages, not in this primer.

Can I use my MDR technical documentation as a 510(k) submission? No, but you can reuse a lot of the underlying work. Risk management files, bench testing, biocompatibility, electrical safety and EMC, software verification, and parts of the clinical evidence can often be reused as supporting data. The submission itself is organised around substantial equivalence to a predicate and must be rebuilt for the FDA reviewer. Treat the two as different documents sharing common inputs.

Where should a first-time EU founder start with 510(k) work? Start with a single structured meeting with a US regulatory specialist once your intended use is locked. The meeting should answer three questions: is a 510(k) the right pathway for your device, what are the candidate predicates, and what is the realistic timeline and cost profile for your specific case. These answers will shape every downstream decision and prevent most of the expensive mistakes first-time founders make on the US side.

Sources

  1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices (MDR), in particular Article 2(12) (intended purpose), Article 52 (conformity assessment procedures), Article 61 (clinical evaluation), Annex VIII (classification rules), and Annex XIV (clinical evaluation and PMCF). Official Journal L 117, 5.5.2017, as amended, including Regulation (EU) 2023/607.
  2. U.S. Food and Drug Administration. Center for Devices and Radiological Health (CDRH), public guidance on the 510(k) premarket notification pathway, substantial equivalence, predicate devices, and device classification. Referenced at the general framework level. For current user fees, current guidance documents, review division assignments, and current timelines, consult the FDA directly at https://www.fda.gov/medical-devices. Note on verification: any specific claim about current 510(k) user fees, current FDA guidance versions, current review performance, or the current status of the FDA's QMSR harmonisation initiative must be verified against live FDA sources before it is used in a business plan or an investor conversation. This primer intentionally does not publish numbers that will move faster than a static blog post can track.
  3. U.S. Code of Federal Regulations, Title 21, Part 807, Subpart E. Premarket notification procedures (including 21 CFR 807.87 on information required in a premarket notification submission). Referenced at the general framework level.
  4. U.S. Code of Federal Regulations, Title 21, Part 820. Quality System Regulation for medical devices, with the FDA's Quality Management System Regulation (QMSR) harmonisation initiative. Referenced at the general framework level.
  5. EN ISO 13485:2016 + A11:2021. Medical devices. Quality management systems. Requirements for regulatory purposes.

This post is part of the FDA & International Market Access series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. A note on the limits of our expertise, stated once and clearly: Tibor's authority is in the EU MDR and the Notified Body system, and the FDA framing in this post stays deliberately at the general level. For specific 510(k) questions on your device. Predicate selection, product code and classification lookup, submission drafting, interactions with FDA review divisions, 21 CFR Part 807 and Part 820 implementation detail, current user fees, and the current status of the FDA's QMSR harmonisation timeline. Work with a US regulatory specialist who practices inside the FDA system daily. This post is the orientation. The specialist is the execution.