FDA 510(k) vs EU MDR CE marking: what gaps exist?

Having FDA 510(k) clearance does not give you CE marking under EU MDR. While both pathways require a quality management system, device classification, and premarket review, the MDR demands significantly more in clinical evaluation, post-market surveillance, and technical documentation. Here are the specific gaps you need to close.

Regulatory basis compared

Gap 1: Clinical evaluation

This is the biggest gap. A 510(k) submission typically relies on bench testing and substantial equivalence to a predicate device. Clinical data are often not required unless the predicate comparison cannot demonstrate equivalence through non-clinical means.

EU MDR requires a clinical evaluation for every device class — MDR Article 61. The clinical evaluation report must:

• Systematically review published clinical literature relevant to the device
• Analyze clinical data from clinical investigations, registries, or post-market sources
• Demonstrate that the device meets the relevant General Safety and Performance Requirements
• Include a post-market clinical follow-up (PMCF) plan per MDR Annex XIV Part B

For Class III and implantable devices, clinical investigations are generally required unless the manufacturer can justify reliance on existing data under MDR Article 61(4)-(6).

MDCG 2020-5 and MDCG 2020-6 provide detailed guidance on clinical evaluation under MDR.

Gap 2: General Safety and Performance Requirements (GSPR)

A 510(k) demonstrates substantial equivalence. MDR requires demonstrating conformity with every applicable requirement in MDR Annex I — the 23 General Safety and Performance Requirements.

Manufacturers must prepare a GSPR checklist mapping each requirement to:

• The applied harmonized standard or common specification
• The evidence demonstrating conformity (test reports, risk analysis, clinical data)
• A justification for any requirement deemed not applicable

This is a structured, requirement-by-requirement demonstration — not a comparison to another device.

Gap 3: Technical documentation structure

A 510(k) submission follows the FDA's format (summary, device description, substantial equivalence comparison, performance data). MDR technical documentation follows a different, more comprehensive structure defined in MDR Annex II and Annex III:

Annex II — Technical documentation:

• Device description and specification (including all variants and accessories)
• Information supplied by the manufacturer (labels, IFU in all required languages)
• Design and manufacturing information
• GSPR checklist
• Benefit-risk analysis per EN ISO 14971:2019
• Product verification and validation
• Clinical evaluation report

Annex III — Post-market surveillance documentation:

• Post-market surveillance plan
• Post-market clinical follow-up (PMCF) plan
• Periodic Safety Update Report (PSUR) for Class IIa, IIb, and III devices

You cannot submit your 510(k) package to a Notified Body. The technical file must be restructured to the MDR Annex II/III format.

Gap 4: Post-market surveillance

FDA requires Medical Device Reports (MDRs) for deaths, serious injuries, and malfunctions under 21 CFR 803. EU MDR post-market obligations are substantially broader:

• Post-market surveillance plan (MDR Article 84) — proactive data collection plan
• Post-market clinical follow-up (PMCF) (MDR Annex XIV Part B) — ongoing clinical data collection to confirm safety and performance
• Periodic Safety Update Report (PSUR) (MDR Article 86) — periodic analysis of post-market data, required for Class IIa (every 2 years), IIb and III (annually)
• Serious incident reporting (MDR Article 87) — within 15 days (or 10/2 days for serious public health threats)
• Trend reporting (MDR Article 88) — significant increases in incident frequency

Gap 5: UDI and EUDAMED registration

FDA has its own UDI system (GUDID). The EU UDI system is separate — you need EU-specific UDI-DIs issued by a recognized entity and must register all devices in EUDAMED before placing them on the EU market (MDR Articles 27-34).

EUDAMED registration became mandatory on May 28, 2026.

Gap 6: Authorized Representative

If you are a non-EU manufacturer, you must appoint an Authorized Representative established in the EU before placing your device on the market (MDR Article 11). The AR acts on your behalf for regulatory interactions, maintains technical documentation access, and must be named on the device label.

There is no equivalent requirement for 510(k) — the FDA deals directly with the manufacturer regardless of location.

Gap 7: Labeling and language requirements

EU MDR labeling requirements (MDR Annex I, Chapter III) include:

• UDI carrier on the label and all higher levels of packaging
• CE mark with Notified Body number (for Class Is, Im, IIa, IIb, III)
• Instructions for use in the official language(s) of each member state where the device is sold
• MDR-specific symbols per EN ISO 15223-1

This is a significant localization effort that goes well beyond FDA labeling requirements.

What you can reuse from your 510(k)

Not everything is a gap. Several elements from your 510(k) submission can be leveraged:

• Risk management file — if based on ISO 14971, it transfers well (update for GSPR mapping)
• Biocompatibility testing — ISO 10993 is accepted by both FDA and EU
• Performance testing — bench and electrical safety testing (IEC 60601, IEC 62304) transfers
• QMS — if ISO 13485-certified, your QMS satisfies both FDA QMSR and MDR
• Usability engineering — IEC 62366 is accepted by both

Key takeaways

• A 510(k) clearance does not provide CE marking — you need a separate MDR conformity assessment
• The biggest gap is clinical evaluation: MDR requires it for all device classes, while 510(k) often does not
• Technical documentation must be restructured from 510(k) format to MDR Annex II/III format
• Post-market surveillance under MDR is substantially broader (PMS plan, PMCF, PSUR, trend reporting)
• EU-specific UDI, EUDAMED registration, Authorized Representative, and multilingual labeling are required
• Reuse risk management, biocompatibility, performance testing, QMS, and usability engineering from your 510(k)

How RegAid helps

RegAid lets you compare FDA and EU MDR requirements side by side using the precedent grid. Ask "Compare the 510(k) substantial equivalence requirements with EU MDR conformity assessment for Class IIa devices" and get a structured comparison with citations to both 21 CFR 807 and MDR Article 52.