How does EU MDR compare to FDA medical device regulations?
MDR 2017/745 · 21 CFR Part 820/QMSR · FDA CDRH guidance
The short answer
EU MDR and FDA regulations are two entirely separate frameworks. MDR compliance does not satisfy FDA requirements and vice versa. Companies targeting both markets need a parallel regulatory strategy designed from the start of development — retrofitting either framework onto a design optimised solely for the other is expensive and time-consuming.
Framework comparison
| Topic | EU MDR | FDA (21 CFR / CDRH) |
|---|---|---|
| Approval model | CE marking via conformity assessment (self-cert or NB) | 510(k) / De Novo / PMA / exempt — FDA decision |
| Regulatory body | European Commission + designated Notified Bodies | FDA Center for Devices and Radiological Health (CDRH) |
| QMS standard | ISO 13485 (referenced; NB audits QMS) | 21 CFR Part 820 / QMSR (aligned with ISO 13485 since 2024) |
| Clinical evidence | CER — continuous lifecycle process; Annex XIV | Clinical data for submission; less ongoing update requirement post-clearance |
| Software | MDSW under MDR Rule 11 + MDCG 2019-11/2025-4 | SaMD under FDA SaMD guidance + 21st Century Cures Act |
| Post-market | PSUR + PMS system; Annex III; Article 83–88 | MDR 21 CFR 803 (adverse event reporting) + 21 CFR 806 (corrections/removals) |
| Typical timeline | 12–24 months (NB-based; longer for Class III) | 3–12 months for 510(k); 12–36 months for PMA |
Where the frameworks align
- ISO 13485: Recognised by both MDR and FDA QMSR; aligning your QMS to ISO 13485 satisfies both frameworks' QMS requirements
- IEC 62304: Referenced by both MDR (via GSPR) and FDA (consensus standard); apply it once for both markets
- IEC 62366 and ISO 14971: Both are referenced by MDR and recognised by FDA; single risk management and usability file can serve both
- Cybersecurity: MDCG 2019-16 and FDA cybersecurity guidance are converging on similar principles — secure design, vulnerability management, SBOM
Dual-market strategy tips
- Align design controls early: FDA design controls (21 CFR 820.30) map closely to MDR Annex II technical documentation — build your design history to satisfy both from the start
- Use harmonised standards for both: IEC 62304, ISO 14971, IEC 62366 are referenced by both frameworks; single records serve dual purposes
- DHF / Annex II overlap: Structure your Design History File to also satisfy the Annex II section structure — document management discipline pays off here
- Clinical data strategy: FDA clinical data (from a 510k or PMA) can contribute to the CER literature body; it does not automatically replace the CER but it provides high-quality evidence
Frequently asked questions
Can I use my 510(k) clinical data for my EU MDR CER?
Yes, FDA submission data — including clinical studies, summaries of safety and effectiveness (SSE), and adverse event data — can be referenced in the CER as clinical evidence. It does not replace the CER or exempt you from Annex XIV clinical evaluation requirements, but it is useful high-quality evidence.
Can I submit to FDA and MDR simultaneously?
Yes. There is no regulatory prohibition on parallel submissions. In practice, many companies target FDA 510(k) first due to shorter timelines, then use the cleared device's clinical record as evidence in the MDR process.
What about UKCA post-Brexit?
Great Britain (England, Scotland, Wales) has its own UKCA marking regime since Brexit. Northern Ireland continues to accept CE marking under the Windsor Framework. UKCA and CE marking requirements are broadly similar but are legally separate frameworks. A CE-marked device is not automatically UKCA-compliant (though mutual recognition discussions continue).