When comparing market requirements in the European Union and the United States, begin with the device’s intended purpose, claims, technology and risk. Determine classification and market access separately for each jurisdiction. This review, checked against information available on 7 October 2026, is a screening framework; EU MDR and US FDA rules are not interchangeable systems.
Download the comparison assessment (Markdown, with source links)
1. Regulatory framework and oversight model
| Assessment item | EU MDR (EU 2017/745) | US FDA medical-device framework | Notes |
|---|---|---|---|
| Regulatory roles | Member State competent authorities oversee the market. Notified Bodies (NBs) perform conformity assessment when required. | FDA regulates devices, mainly through CDRH and, for some products, CBER. Certain 510(k)s may use an accredited third-party review. | It is inaccurate to say that all EU review is done by NBs or all US review is direct CDRH review. |
| Scope | Medical devices, accessories and certain products without an intended medical purpose listed in Annex XVI; qualifying software may also be covered. | Products meeting the legal definition of a device, IVDs and qualifying software; some software functions are excluded or subject to specific policies. | IVDs in the EU are primarily governed by IVDR 2017/746 and should not be folded into an MDR comparison. |
| Legal basis | MDR articles and annexes, including Annex I General Safety and Performance Requirements (GSPR). | The FD&C Act and applicable 21 CFR provisions; Part 820 is now the QMSR. | Assess product requirements and manufacturer responsibilities together. |
Sources: EU regulations overview, FDA premarket pathways, FDA QMSR.
2. Risk classification
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Classification structure | Classes I, IIa, IIb and III, determined under the rules in Annex VIII. | Classes I, II and III, determined by the applicable classification regulation, product code and intended use. | Class levels cannot be converted directly between jurisdictions. |
| Lower risk | A Class I device can generally be self-declared by the manufacturer. NB involvement is required for relevant aspects of sterile, measuring or reusable surgical Class I devices. | Many Class I devices are exempt from 510(k), subject to limitations and other applicable obligations. | Exemption from a premarket submission does not exempt a device from all requirements. |
| Moderate risk | Class IIa and IIb generally require NB involvement in the applicable conformity-assessment route. | Class II devices commonly use 510(k), although exemptions and other routes may apply. | MDR Class IIb has no fixed FDA class equivalent. |
| Higher risk | Class III generally requires more extensive conformity assessment and clinical evidence. | Class III generally requires PMA; exceptions exist for certain legacy devices and other cases. | Do not assume every Class III device follows exactly the same route. |
Sources: MDR text and Annex VIII, FDA PMA overview.
3. Market access routes and review
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Main route | Complete the applicable conformity assessment, issue the EU Declaration of Conformity and affix the CE marking. | Depending on the device: 510(k), De Novo, PMA or an applicable exemption. | 510(k) clearance and PMA approval are different terms with different legal effects. |
| Equivalence concept | Clinical evaluation may rely on equivalence evidence only under the applicable, strict conditions. | A 510(k) evaluates substantial equivalence to a legally marketed predicate device. | MDR does not lack an equivalence concept; the concepts serve different purposes. |
| Third-party review | NB involvement depends on classification and the selected conformity-assessment route. | Certain eligible 510(k)s may receive accredited third-party review before FDA makes its decision. | The third-party program is not available for every device or submission. |
| Technical documentation | Annexes II and III cover risk management, verification and validation, clinical evaluation and post-market information. | Prepare information required for the applicable 510(k), De Novo or PMA route. | Confirm acceptance criteria before reusing evidence across markets. |
| Review time | Depends on device, dossier quality, clinical work, NB capacity and requests for additional information. | Depends on the pathway, dossier and questions. The 510(k) 90-FDA-day goal is not a guarantee of 90 calendar days. | Avoid promising generic “12–18 months” or “6–12 months” timelines. |
| Cost | Estimate NB fees, testing, clinical work, QMS, registration and maintenance separately. | Separate official user fees from testing, clinical work, consulting, QMS and maintenance costs. | Do not treat official fees as the total product-development or market-entry cost. |
Sources: MDCG clinical equivalence guidance, FDA third-party review, 510(k) review process.
FDA FY 2027 example user fees
The fee period is 1 October 2026 to 30 September 2027. These are application fees, not the full cost of market entry. Small-business qualification and reduced fees are subject to FDA rules.
| Submission | Standard fee (USD) | Small-business fee (USD) |
|---|---|---|
| 510(k) | 28,653 | 7,163 |
| De Novo | 191,020 | 47,755 |
| PMA | 636,732 | 159,183 |
Source: FDA FY 2027 medical-device user fees.
4. Clinical evidence
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Clinical evaluation | Conduct and document a clinical evaluation and Clinical Evaluation Report (CER) under Article 61 and Annex XIV. Evidence depends on the device and applicable conditions. | Clinical-data needs depend on the route and device-specific requirements; some 510(k)s can be supported by non-clinical evidence. | A clinical evaluation does not mean every device needs a new clinical trial. |
| Clinical investigation | Implantable and Class III devices generally require clinical investigations, subject to statutory exceptions and conditions for sufficient existing evidence. | A PMA requires valid scientific evidence; study design depends on the device and question, and is not automatically an RCT. | Do not conclude that one jurisdiction always requires more clinical evidence. |
| Post-market clinical follow-up | PMCF updates the clinical evaluation on an ongoing basis. If PMCF is not applicable, the manufacturer must justify this adequately. | Post-approval studies may be required as a PMA condition; Section 522 surveillance and other requirements may apply. | PMCF does not mean every device must undergo a prospective study. |
| Periodic updates | PSURs for Class IIb and III are updated at least annually; Class IIa at least every two years and when necessary; Class I uses a PMS report. | PMA annual reports and other reporting duties depend on the applicable requirements. | Distinguish the update, retention and submission procedures for PSURs. |
Sources: MDR Articles 61, 85, 86 and Annex XIV, PMCF plan guidance, FDA PMA post-approval requirements.
5. Quality management systems (QMS)
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Basis | Article 10(9) requires an appropriate QMS. Use of a harmonised standard can provide a presumption of conformity within its scope. | The Part 820 QMSR took effect on 2 February 2026, incorporates ISO 13485:2016 by reference and retains FDA-specific requirements. | EU MDR does not simply require every manufacturer to hold an ISO certificate. An ISO certificate does not replace FDA compliance or inspection. |
| Assessment and inspection | NBs assess and conduct surveillance when applicable; competent authorities also have oversight powers. | FDA inspects according to applicable procedures and risk; inspections may be announced or unannounced. | Avoid broad claims that enforcement is necessarily stricter in one region. |
| Design and risk | Design, changes, risk management and technical documentation must remain consistent. | QMSR applies design and development requirements and risk management, alongside product-specific and regulatory exceptions. | Build common processes, then address jurisdiction-specific differences. |
Sources: EU harmonised standards, FDA QMSR, FDA QMSR FAQs.
6. UDI and traceability
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| UDI applicability | The UDI system generally applies, subject to exceptions such as custom-made devices and differing labelling or direct-marking arrangements. | Labelling, packaging and GUDID duties depend on the rules; exceptions and alternatives exist. | Do not describe UDI as an exception-free requirement for every device. |
| Database | EUDAMED modules are being implemented in stages and have transition rules; check the device, operator role and applicable deadline. | GUDID stores required identification information for applicable devices; AccessGUDID supports public searches. | Not all database information is necessarily public. |
| 2026 milestone | The first four EUDAMED modules became mandatory to use from 28 May 2026; specific transition duties must be checked separately. | Follow the current FDA rules and policies applicable to the device. | Do not imply that every EUDAMED module became fully operational at once. |
Sources: EU EUDAMED announcement, FDA UDI basics, FDA UDI exceptions and alternatives.
7. Post-market surveillance (PMS)
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Event reporting | Depending on the event, serious incidents must be reported within deadlines such as 2, 10 or 15 days. Trend reporting and field safety corrective actions also apply. | Manufacturers generally report a reportable event within 30 days of becoming aware; a five-working-day report is required in specified situations. | FDA “MDR” here means Medical Device Reporting, not the EU Medical Device Regulation. |
| Periodic reports | Manage PMS reports and PSURs according to class and device-specific requirements. | PMA annual reports, approval conditions and other reports apply as relevant. | It is inaccurate to say that the US has no annual reporting. |
| Recalls and corrective actions | Manufacturers, competent authorities and, where applicable, NBs have roles in field safety corrective actions and notices. | Manufacturers and FDA follow applicable recall, correction and removal requirements. | Establish internal assessment, reporting and effectiveness-check processes. |
Sources: MDR Articles 83–92, FDA mandatory reporting, PMA post-approval requirements.
8. Certificate validity and change control
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Certificate and validity | Under Article 56, an NB certificate is generally valid for up to five years, subject to continued conformity and applicable surveillance. A self-declared Class I device does not necessarily have an NB certificate. | A 510(k) clearance is not a CE-style certificate with a fixed term. Market obligations, change control and other regulatory duties continue. | “No fixed expiry” does not mean that a device needs no ongoing maintenance. |
| Change assessment | Based on the device, QMS, certificate and assessment route, determine whether NB notification or approval and other document updates are needed. | For a 510(k) device, assess whether a change could significantly affect safety or effectiveness or alter intended use. PMA devices have separate supplement, notice and annual-report rules. | Do not force all changes into a universal minor/moderate/major three-level scheme. |
| Change records | Retain rationale, verification and validation, and updated technical and clinical documentation. | Retain the rationale for a new submission or no new submission, along with design and risk evidence. | Assess 510(k) and PMA devices under their separate change rules. |
Sources: MDR Articles 52, 56 and conformity-assessment annexes, FDA 510(k) information, FDA PMA supplements and amendments.
9. Cybersecurity and software devices
| Assessment item | EU MDR | US FDA | Notes |
|---|---|---|---|
| Design and risk | Apply Annex I software, information-security and risk requirements together with relevant MDCG guidance. | Devices qualifying as cyber devices must meet FD&C Act §524B; also consider FDA cybersecurity guidance. | Do not describe US cybersecurity requirements as guidance-only. |
| Premarket documentation | Document cybersecurity needs, threats and risks, verification and validation, and user information as appropriate to the device. | Where applicable, provide a vulnerability-management plan, update and patch processes, and a software bill of materials (SBOM). | Distinguish legal duties from recommendations in guidance. |
| Ongoing monitoring | Consider cybersecurity signals through PMS, risk management and applicable vigilance reporting, including their safety and performance effects. | Monitor vulnerabilities and patches and meet applicable incident, correction and reporting duties. | Not every cybersecurity event automatically triggers the same reporting duty. |
Sources: EU MDCG guidance, FDA medical-device cybersecurity guidance, FDA guidance and Section 524B.
Overall assessment
- Determine each market’s requirements separately, then reuse evidence where accepted. Classification, access routes and clinical requirements differ; classes and certificates cannot simply be exchanged.
- Plan post-market work before launch. QMS, clinical updates, UDI, event reporting and cybersecurity monitoring can affect long-term costs.
- Choose market order according to the device. Before pursuing FDA 510(k) first, confirm that a suitable predicate and route exist, then consider commercial priorities, evidence gaps and timing. This sequence is not appropriate for every product.
- US evidence is not automatically accepted in the EU. Check intended purpose, population, technology, clinical quality and data-access conditions before relying on it for a CER or PMCF.
This comparison is for preliminary gap assessment. Determine each device’s obligations using current legislation, official notices and competent-authority or NB input. Fee amounts and system milestones above are tied to the stated information date.