EU MDR vs FDA 510(k): A Deep Comparison for Medical Device Manufacturers
A detailed comparison of the EU Medical Devices Regulation and the US FDA 510(k) pathway — covering risk classification, clinical evidence requirements, and global compliance strategies for medical device makers.
The European Union and the United States are the two largest medical device markets in the world. Together they account for roughly 65% of global medical device revenue. If you're a manufacturer with any ambition beyond your home market, you'll need to deal with both regulatory systems eventually.
Here's the problem: these two systems think about medical devices in fundamentally different ways. The EU's Medical Devices Regulation (MDR 2017/745) and the US FDA's 510(k) clearance pathway share the same goal — keeping patients safe — but they take very different roads to get there.
This article breaks down those differences so you can plan your regulatory strategy without nasty surprises.
Two Philosophies, One Goal
Before diving into specifics, it helps to understand the core philosophy behind each system.
EU MDR: "Prove It's Safe and Effective"
The EU MDR, which fully replaced the older Medical Devices Directive (MDD) after a transition period, takes a risk-and-evidence-based approach. The regulation asks: what is the clinical evidence that this device is safe and performs as intended?
Every device needs a clinical evaluation — a systematic review of clinical data demonstrating safety and performance. For higher-risk devices, this often means clinical investigations (trials). The burden of proof sits squarely on the manufacturer, and it's ongoing. You don't just prove safety once; you keep proving it through post-market surveillance for the device's entire lifecycle.
MDR also introduced the concept of Notified Bodies — independent organizations authorized by EU member states to assess device conformity. For anything above the lowest risk class, a Notified Body must review and approve your documentation before you can place a CE Mark on your device. (If you're new to CE marking, our beginner's guide to CE marking covers the general process.)
FDA 510(k): "Prove It's Substantially Equivalent"
The FDA's 510(k) pathway takes a different approach. Instead of asking "is this device safe and effective from scratch?", it asks: is this device substantially equivalent to something already legally on the market?
That "something already on the market" is called a predicate device. If you can demonstrate that your device has the same intended use and either the same technological characteristics — or different characteristics that don't raise new safety questions — then the FDA clears your device based on that comparison.
This doesn't mean the 510(k) is easy or rubber-stamped. The FDA reviews thousands of 510(k) submissions each year and rejects a significant portion. But the conceptual starting point is comparison rather than standalone evidence.
It's worth noting that the 510(k) is just one FDA pathway. The Pre-Market Approval (PMA) pathway for high-risk devices does require full clinical evidence, similar to the MDR approach. But the 510(k) covers the vast majority of devices entering the US market, so that's our focus here.
Risk Classification: Mapping the Two Systems
Both systems classify devices by risk level, but they use different structures.
EU MDR Classification
The EU MDR uses four risk classes, determined by a set of 22 classification rules in Annex VIII:
| EU Class | Risk Level | Examples | Notified Body Required? |
|---|---|---|---|
| Class I | Lowest risk | Bandages, tongue depressors, wheelchairs | No (self-declaration) — except for sterile Class I, Class I with measuring function, and reusable surgical instruments |
| Class IIa | Low-moderate risk | Hearing aids, blood pressure monitors, surgical clamps | Yes |
| Class IIb | Moderate-high risk | Ventilators, orthopedic implants, surgical lasers | Yes |
| Class III | Highest risk | Heart valves, hip implants, coronary stents | Yes (plus consultation with expert panels for certain devices) |
MDR significantly upclassified many devices compared to the old MDD. Software as a Medical Device (SaMD), for instance, can now be classified as high as Class III if it influences treatment decisions for life-threatening conditions. Reprocessed single-use devices got stricter rules too.
FDA Classification
The FDA uses three classes:
| FDA Class | Risk Level | Examples | Regulatory Pathway |
|---|---|---|---|
| Class I | Lowest risk | Bandages, tongue depressors, manual stethoscopes | Most are exempt from 510(k); general controls apply |
| Class II | Moderate risk | Powered wheelchairs, pregnancy tests, infusion pumps, surgical drapes | 510(k) clearance required; general + special controls |
| Class III | Highest risk | Heart valves, implantable defibrillators, coronary stents | PMA required (not 510(k)) |
Cross-Mapping: EU vs FDA Classification
Here's where it gets tricky. The two systems don't map 1:1. A device might be Class II in the US but Class IIb or even Class III in the EU.
| Device Type | FDA Classification | EU MDR Classification | Notes |
|---|---|---|---|
| Powered wheelchair | Class II | Class I | Less regulated in EU |
| Software that aids diagnosis (non-life-threatening) | Class II | Class IIa | Similar level |
| Software that aids diagnosis (life-threatening) | Class II | Class III | Much stricter in EU |
| Active implantable device | Class III (PMA) | Class III | Both require highest scrutiny |
| Surgical mesh | Class II | Class III (MDR upclassified) | Much stricter in EU under MDR |
| Non-invasive blood pressure monitor | Class II | Class IIa | Similar level |
Key takeaway: Don't assume your US classification tells you anything about your EU classification. Run the MDR classification rules independently.
Technical Documentation Requirements
Both systems require detailed technical documentation, but the structure and depth differ.
EU MDR Technical Documentation
MDR Annex II and Annex III spell out exactly what your technical file must contain:
Annex II — Technical Documentation:
- Device description and specification (including all variants and accessories)
- Information supplied by the manufacturer (labeling, IFU)
- Design and manufacturing information
- General safety and performance requirements (GSPR) checklist — mapping each requirement in Annex I to the evidence that demonstrates compliance
- Benefit-risk analysis
- Product verification and validation (bench testing, biocompatibility, electrical safety, software validation, usability)
- Clinical evaluation report (more on this below)
Annex III — Post-Market Surveillance Documentation:
- Post-market surveillance plan
- Post-market surveillance report (Class I) or Periodic Safety Update Report/PSUR (Class IIa, IIb, III)
- Post-market clinical follow-up (PMCF) plan and report
The GSPR checklist is a big deal. Annex I of the MDR lists roughly 23 general safety and performance requirements. For each one, you must demonstrate compliance with specific evidence. It's methodical and thorough.
FDA 510(k) Submission
A typical 510(k) submission includes:
- Cover letter and CDRH premarket review submission cover sheet
- Indications for use statement
- Substantial equivalence comparison to the predicate device
- Device description
- Performance testing data (bench testing, biocompatibility as applicable)
- Software documentation (if applicable, per FDA guidance)
- Labeling (proposed labels, instructions for use)
- Sterilization information (if applicable)
- Biocompatibility information (per ISO 10993)
- Electromagnetic compatibility data (if applicable)
What you won't typically see in a 510(k): A full clinical evaluation report. For most 510(k) submissions, bench testing and performance data are sufficient. Clinical data is sometimes needed — particularly for higher-risk Class II devices or when technological differences from the predicate raise clinical questions — but it's the exception rather than the rule.
Side-by-Side Comparison
| Documentation Element | EU MDR | FDA 510(k) |
|---|---|---|
| Device description | Required (detailed) | Required |
| Risk analysis | Required (ISO 14971) | Required (ISO 14971) |
| Performance testing | Required | Required |
| Biocompatibility | Required (ISO 10993) | Required (ISO 10993) |
| Clinical evaluation | Always required | Typically not required (performance testing usually sufficient) |
| Predicate comparison | Not applicable | Core requirement |
| Post-market surveillance plan | Required in submission | Not part of 510(k) (separate FDA requirements apply) |
| Software documentation | Required (IEC 62304) | Required for software devices (FDA guidance) |
| Labeling review | Required | Required |
| Quality system evidence | ISO 13485 certificate often expected | FDA inspects QSR (21 CFR 820) separately |
Clinical Evidence: The Biggest Difference
This is where the gap between MDR and 510(k) is widest, and where most manufacturers feel the pain.
MDR Clinical Evidence Requirements
Under MDR Article 61, every device must have a clinical evaluation. No exceptions. The depth of clinical evidence required scales with risk:
Class I: A clinical evaluation is still required, but it can often be based on a literature review and equivalence to similar devices on the market. Clinical investigations are rarely needed.
Class IIa/IIb: A clinical evaluation report based on literature review and clinical experience data may be sufficient for well-established technologies. For newer technologies, clinical investigations may be necessary. Class IIb implantable devices and Class III devices face the strictest requirements.
Class III and implantable devices: Clinical investigations are generally expected unless the manufacturer can demonstrate equivalence to an existing device with sufficient clinical data AND has a contract with that device's manufacturer to access their technical documentation. (This equivalence route was deliberately made harder under MDR compared to MDD.)
The clinical evaluation isn't a one-time exercise. MDR requires Post-Market Clinical Follow-up (PMCF) — an ongoing, proactive collection of clinical data throughout the device's market life. PMCF plans and reports must be updated regularly.
FDA 510(k) Clinical Evidence
For most 510(k) submissions, clinical data is not required. The substantial equivalence comparison focuses on:
- Bench testing (performance data)
- Biocompatibility testing
- Software verification and validation
- Usability/human factors testing
Clinical data becomes relevant when:
- There's no suitable predicate device
- Technological differences from the predicate raise safety or effectiveness questions
- FDA guidance for the specific device type calls for clinical data
- The device makes clinical claims that can't be supported by bench testing alone
When clinical data is required for a 510(k), it's typically less extensive than what MDR demands — often a focused clinical study rather than a full clinical evaluation spanning all available literature.
What This Means in Practice
| Scenario | MDR Approach | 510(k) Approach |
|---|---|---|
| Well-established device, identical technology to existing products | Clinical evaluation via literature review + equivalence | Substantial equivalence comparison with performance testing |
| Novel device, new technology | Clinical investigation likely required | May need clinical data; depends on risk questions |
| Software as medical device | Clinical evaluation required; complexity depends on classification | Performance testing usually sufficient for Class II |
| Incremental improvement to existing device | Clinical evaluation update; may leverage existing data | 510(k) with updated performance testing |
The bottom line: if you've only budgeted for 510(k)-level evidence, you are probably underbudgeting for MDR. The clinical evaluation alone can add months and significant cost to your EU submission.
Post-Market Surveillance
Both regulators require manufacturers to monitor their devices after they reach the market, but MDR goes further.
MDR Post-Market Requirements
MDR created a structured post-market surveillance framework:
- Post-Market Surveillance (PMS) Plan: Required for all devices. Must describe how you'll proactively collect and evaluate data.
- PMS Report: Required for Class I devices. Summarizes PMS activities and findings; updated as needed.
- Periodic Safety Update Report (PSUR): Required for Class IIa, IIb, and III devices. Must be updated at least annually for Class III and Class IIb, and at least every two years for Class IIa.
- Post-Market Clinical Follow-up (PMCF): Proactive clinical data collection throughout the device's lifecycle. PMCF plan and evaluation report required.
- Vigilance reporting: Serious incidents must be reported to authorities. Trend reporting is required.
- Unique Device Identification (UDI): Mandatory. Each device must carry a UDI, and the data must be registered in EUDAMED (the European database for medical devices).
FDA Post-Market Requirements
The FDA also has post-market obligations, but they're less prescriptive:
- Medical Device Reporting (MDR — confusingly the same acronym): Report deaths, serious injuries, and malfunctions to FDA.
- Corrections and removals: Report recalls and field actions.
- Post-market studies: FDA can require post-market studies as a condition of clearance, but this is relatively uncommon for 510(k) devices.
- UDI: Required, with data submitted to GUDID (Global Unique Device Identification Database).
Comparison
| Post-Market Element | EU MDR | FDA |
|---|---|---|
| Surveillance plan | Mandatory, detailed | Required as part of QMS |
| Regular safety reports | PSUR required (annually for Class IIb/III) | Not required for most 510(k) devices |
| Ongoing clinical follow-up | PMCF mandatory | Rare for 510(k) devices |
| Incident reporting | Yes, with trend reporting | Yes (MDR — Medical Device Reporting) |
| UDI | Mandatory, EUDAMED registration | Mandatory, GUDID registration |
| Proactive data collection | Explicitly required | Expected through QMS but less prescriptive |
Timeline and Cost Comparison
Let's talk money and time. These are rough estimates — actual figures vary widely by device complexity, risk class, and whether things go smoothly.
EU MDR (CE Marking via Notified Body)
| Phase | Timeline | Cost Estimate |
|---|---|---|
| Regulatory strategy and classification | 1-2 months | $10,000 - $30,000 |
| Technical documentation preparation | 3-8 months | $30,000 - $150,000 |
| Clinical evaluation report | 2-6 months | $20,000 - $100,000+ |
| Clinical investigation (if required) | 12-24 months | $200,000 - $2,000,000+ |
| Performance testing (bench, biocompatibility, etc.) | 3-6 months | $30,000 - $150,000 |
| Notified Body review | 3-12 months | $15,000 - $50,000 (NB fees) |
| Total (without clinical investigation) | 9-24 months | $100,000 - $500,000 |
| Total (with clinical investigation) | 18-36+ months | $300,000 - $2,500,000+ |
A major bottleneck: Notified Body availability. After MDR took effect, many Notified Bodies lost their designation or reduced capacity. The remaining ones have significant backlogs. Wait times of 6-12 months just to start the review process are common.
FDA 510(k)
| Phase | Timeline | Cost Estimate |
|---|---|---|
| Regulatory strategy and predicate research | 1-2 months | $5,000 - $20,000 |
| Performance testing | 2-4 months | $20,000 - $100,000 |
| 510(k) submission preparation | 2-4 months | $15,000 - $60,000 |
| FDA review (MDUFA goal: 90 days) | 3-6 months | $21,760 (standard 510(k) user fee, FY2025) |
| Additional information requests | 1-3 months (if applicable) | Variable |
| Total | 6-12 months | $60,000 - $200,000 |
The FDA's user fee for a standard 510(k) review is fixed and published annually. Small businesses may qualify for reduced fees.
Head-to-Head
| Factor | EU MDR | FDA 510(k) |
|---|---|---|
| Typical timeline | 9-24 months | 6-12 months |
| Typical cost | $100K-$500K | $60K-$200K |
| Clinical evidence burden | High | Low-moderate |
| Third-party review | Always (Notified Body, except Class I) | FDA internal review |
| Post-market obligations | Extensive | Moderate |
| Renewal required? | CE certificate valid 5 years, then renewal | 510(k) clearance doesn't expire |
A Decision Framework for Manufacturers Targeting Both Markets
If you're building a device for both the US and EU markets, here's how to think about your strategy.
Option A: EU First, Then US
When this makes sense:
- Your primary market is Europe
- You're already working with a Notified Body
- You have strong clinical data or can generate it efficiently
Advantages: MDR documentation is more extensive, so your 510(k) submission will be straightforward by comparison. Clinical data generated for MDR can support FDA submissions if needed.
Disadvantages: Longer time to first market entry. Notified Body backlogs can delay your entire timeline.
Option B: US First, Then EU
When this makes sense:
- Your primary market is the US
- You want faster initial market entry
- You need revenue to fund the more expensive EU submission
Advantages: Faster to market. Revenue from US sales can fund EU clinical evaluation and Notified Body costs.
Disadvantages: You'll likely need to generate significant additional documentation and clinical evidence for MDR that wasn't required for 510(k). Planning for this upfront saves rework later.
Option C: Parallel Submissions
When this makes sense:
- You have the budget and resources for simultaneous submissions
- Speed to market in both regions is critical
- You can run testing programs that satisfy both sets of requirements
Advantages: Fastest overall time to both markets.
Disadvantages: Highest upfront cost. Requires regulatory expertise in both systems simultaneously.
Practical Tip: Build for MDR First
Regardless of which market you enter first, design your documentation and testing program to satisfy MDR requirements. It's far easier to extract a 510(k) submission from MDR-level documentation than to upgrade 510(k)-level documentation to meet MDR.
This means:
- Write a clinical evaluation report even if the 510(k) doesn't require it
- Implement a full post-market surveillance system from day one
- Follow ISO 13485 for your quality management system (required for MDR, strongly expected by FDA)
- Design your risk management per ISO 14971 (accepted by both systems)
Frequently Asked Questions
Q: Can I use the same test data for both MDR and 510(k)?
A: In many cases, yes. Biocompatibility testing per ISO 10993, electrical safety testing per IEC 60601, and software lifecycle documentation per IEC 62304 are accepted by both systems. Performance bench testing may need slight modifications to address system-specific requirements. The key difference is clinical evidence — MDR almost always requires more.
Q: My device is cleared via 510(k) in the US. Does that help with MDR?
A: Having 510(k) clearance demonstrates a baseline level of safety and performance review, but it does not substitute for MDR conformity assessment. You still need a full MDR technical file, clinical evaluation, and Notified Body review (for Class IIa and above). However, the test data and documentation you generated for the 510(k) can be reused and expanded.
Q: What about the UK post-Brexit?
A: The UK now has its own regulatory framework (UKCA marking) under the Medicines and Healthcare products Regulatory Agency (MHRA). As of early 2026, the UK is still recognizing CE marking for medical devices during a transition period, but manufacturers should plan for separate UKCA conformity assessment. The UKCA requirements are largely based on the EU MDR framework.
Q: How does the EU MDR handle software as a medical device (SaMD)?
A: MDR classifies SaMD based on its intended purpose and the severity of the condition it addresses. Software that provides information used to make treatment decisions can be classified as Class IIa, IIb, or even Class III. This is a significant change from the old MDD, which generally classified most software as Class I. By contrast, most diagnostic software falls under FDA Class II and follows the 510(k) pathway.
Q: Do I need an Authorized Representative for the EU?
A: If your company is not established in the EU, yes. Under MDR Article 11, non-EU manufacturers must designate an Authorized Representative in the EU before placing a device on the market. This is separate from your Notified Body. Your EU Authorized Representative takes on specific legal obligations, so choose carefully.
Q: What is EUDAMED and do I need to register?
A: EUDAMED is the European Database on Medical Devices. Under MDR, manufacturers must register themselves and their devices in EUDAMED. The database will eventually include UDI data, certificates, clinical investigations, vigilance reports, and post-market surveillance information. Full EUDAMED functionality has been delayed multiple times, but modules are progressively coming online. Registration is already required.
Conclusion
The EU MDR and FDA 510(k) serve the same fundamental purpose — ensuring medical devices are safe for patients. But their approaches are different enough that you can't treat one as a slightly modified version of the other.
MDR demands more clinical evidence, more post-market work, and longer timelines. The 510(k) is faster and more focused but limited to devices that can demonstrate substantial equivalence to a predicate.
The smartest strategy for manufacturers targeting both markets: plan your regulatory and testing program around MDR requirements from the start. You'll generate everything you need for the 510(k) along the way, while avoiding expensive rework when it's time to enter the European market.
Whatever your approach, start early, budget realistically, and get regulatory expertise involved before you've locked in your design. Regulatory surprises late in development are the most expensive kind.
For detailed requirements on European medical device compliance, visit our EU MDR standard page. For quality management system requirements, see our ISO 13485 guide.