Product Compliance And Certification For Medical Device In The Eu

Scope and evidence must be confirmed before any paid tests or filings.

An EU medical device is not certified by selecting a laboratory test first. Start with the manufacturer’s documented intended purpose, mechanism of action, users and exact configuration; then determine whether Regulation (EU) 2017/745 (MDR), another primary product regime, and additional horizontal rules apply. This route map concerns a specific device brought to the EU market, not a generic promise of “EU approval”. A CE mark represents conformity with applicable requirements; it is not an EU authority’s product approval.

Decide what the product is before choosing a certification route

Freeze one product version and its claims before assessing the law. A diagnostic claim can change the legal route even when the hardware is identical. Evaluate the marketed system including accessories, software, substances and supplied power/radio components. A device intended to examine human specimens in vitro may instead fall under IVDR; a product whose principal intended action is pharmacological, immunological or metabolic requires a medicine–device borderline analysis. Certain Annex XVI products are MDR-covered despite lacking a medical purpose.

Intended purpose: exact disease, condition, monitoring or treatment claim, plus contraindications and patient group.
Operation: physical mechanism, invasiveness, duration, anatomy contacted and whether used in the body.
System boundary: accessories, software version, cloud functions, wireless module, power supply and battery.
Commercial path: manufacturer of record, brand owner, place of establishment, importer and EU markets/languages.
Unresolved borderline: record competing MDR/IVDR/medicine/accessory interpretations rather than assuming the lower-risk route.

Classification triggers that change the EU route

Under MDR Article 51 and Annex VIII the intended purpose and risk rules determine class I, IIa, IIb or III; software, active and invasive-device rules may matter. The table is a screening tool, not a class determination.

Indicator	Question to resolve	Regulatory consequence
Simple non-sterile, non-measuring class I candidate	Is an Annex VIII rule actually consistent with class I, and are sterile, measuring or reusable-surgical features absent?	If verified, standard class I normally uses manufacturer conformity assessment without a notified body; exceptions below matter.
Class I sterile, measuring or reusable-surgical feature	Which sterile, measuring or reusable-surgical aspect is claimed?	A notified body participates for the relevant aspects; do not describe all class I devices as self-certified.
Active diagnostic, therapy or implanted device	What energy is delivered, what decisions depend on the result, is it implanted and for how long?	Apply the relevant Annex VIII rules; classes IIa/IIb/III generally require notified-body conformity assessment.
Software that influences clinical decisions	Does the output drive diagnosis or treatment, and what harm could an erroneous decision cause?	Screen MDR Rule 11 and software guidance; an app or AI label alone does not establish its legal class.
Custom-made or investigational device	Is the item made for one patient under a written prescription, or only used in an investigation?	Special MDR routes and restrictions may apply; neither is a blanket exemption for ordinary sales.

Current-law checkpoint: the 2026 delegated amendments to MDR Articles 52(4) and 61(6) expanded specified exceptions for per-device technical-file review of certain class IIb implants and for conducting clinical investigations in some implantable/class III categories. These are narrow, conditional exceptions, not exemptions from clinical evaluation or all notified-body scrutiny.

Cross-regime applicability matrix for one medical-device product

Apply each row as a separate yes/no/unknown test. “Unknown” means evidence is missing, not that legislation is inapplicable. Overlapping legislation must be analysed for the actual product and scope of each instrument.

Regime	Applicability trigger	Next safe action
MDR 2017/745 — main route	Device/accessory for a human medical purpose, or an included Annex XVI product.	Classify, map Annex I safety/performance requirements, choose Article 52 conformity route and document clinical evidence.
IVDR 2017/746 — alternative primary route	System examines specimens from the human body in vitro to provide defined medical information.	Reassess under IVDR; do not carry an MDR class or certificate over to IVD products.
RED 2014/53/EU — additional radio layer	Product intentionally transmits or receives radio waves, e.g., Bluetooth/Wi-Fi.	Evaluate RED scope, exclusions and applicable radio/spectrum and safety obligations alongside MDR; distinguish RED from standalone EMC/LVD assumptions.
RoHS / WEEE / batteries — component and lifecycle layers	Electrical/electronic unit, waste electrical equipment or a battery is in scope.	Map substance restrictions/exemptions, producer or take-back responsibilities and applicable battery requirements by device, component and market.
AI Act — conditional software overlay	Software qualifies as an AI system and its intended role meets an AI Act applicability/high-risk test.	Perform a separate Article 6/Annex I and applicability-date review; MDR classification does not by itself settle AI Act duties.
GDPR — personal-data processing layer	App, cloud or support process handles identifiable patient or health data.	Identify controller/processor, lawful basis and, where relevant, Article 9 health-data condition; document security and data flows.
Medicinal substance / combination boundary	A medicinal substance is incorporated, or principal action may be pharmacological, immunological or metabolic.	Evaluate MDR Article 1/Annex VIII and medicine rules for the particular configuration; obtain expert borderline review before filing.

AI Act route control: for the product route in Article 6(1), both an AI-system/safety-component condition and a product conformity assessment by a third party are relevant. AI alone, a radio module alone or MDR class alone does not prove high-risk status. Under the current Article 113 timetable, the specific high-risk obligations in Chapter III, Sections 1–3 for Annex I product systems apply from 2 August 2028; other AI Act provisions have different dates. Recheck the current consolidated law before release.

Apply the July 2026 amendments to Article 6, not just its original two-part test: AI used solely for non-safety assistance, efficiency or convenience is not a safety component unless its malfunction would endanger health or safety (Article 6(1a)–(1b)). Third-party assessment required solely for non-health-and-safety risks, such as radio-spectrum or non-safety electromagnetic interference, does not fulfil the product-route condition (Article 6(1c)). Screen Annex III separately under Article 6(2); its Chapter III Sections 1–3 timetable is 2 December 2027, not the Annex I product-route date. Record the AI function, failure consequences, and the actual reason third-party assessment is required before deciding high-risk status.

Product evidence file: what to collect and why

Build one evidence index with a responsible owner and version for each item. Harmonised standards, when applicable and properly used, may support a presumption of conformity for covered requirements; a standard is not itself the legislation and an ISO certificate is not a substitute for MDR conformity assessment.

Claims-and-configuration dossier: intended purpose, target users, indications, product variants, architecture, drawings, accessories and marketing screenshots.
Classification memo: MDR/IVDR/medicine borderline, each applicable Annex VIII rule, rationale for class and notified-body decision.
Annex I GSPR checklist and risk-management file linked to verification and validation; document electrical, mechanical, biological, usability, sterilisation and software risks as applicable.
Clinical evaluation and appropriate clinical data (MDR Article 61/Annex XIV); plan post-market clinical follow-up where required rather than treating bench testing as clinical proof.
Technical documentation under Annexes II–III, QMS, supplier controls, software lifecycle/cybersecurity testing and change-history traceability.
Label/IFU/packaging matrix for target Member States: claims, warnings, symbols, UDI, CE mark and notified-body number if applicable; check each national language rule.
Economic-operator and market-access pack: EU authorised representative where required, importer/distributor duties, declaration of conformity, registration and post-market surveillance/vigilance procedures.

Also identify the person responsible for regulatory compliance (PRRC) under MDR Article 15 and document how that role interfaces with the manufacturer and, where relevant, its EU authorised representative.

Launch dependency gates: do not confuse CE marking with a sale-ready product

The following gates are sequential dependencies, not a fixed regulatory timetable. Where a gate fails, do not infer that a paid laboratory report or a voluntary “CE certificate” cures the defect.

Gate	Evidence required	Blocker
G1 — product and classification locked	Approved intended purpose, version, MDR/IVDR assessment, class and regime matrix.	Marketing claims or software features remain contradictory.
G2 — manufacturer and evidence ready	MDR-compliant QMS/technical file, GSPR/risk/clinical evidence; authorised representative mandate if manufacturer is outside the EU.	No substantiated clinical benefit or no established responsible economic operator.
G3 — conformity route completed	Required notified-body review/certificates (if applicable), declaration of conformity and correctly applied CE mark.	Class II/III product relies on a generic test certificate or an unverified notified-body scope.
G4 — identification and market information	UDI and EUDAMED actor/device work as applicable; market-specific labels/IFU, importer details and supply-chain checks.	Registration, translations or traceability are missing; do not presume database registration alone grants market approval.
G5 — post-launch controls operational	Complaint handling, PMS/PMCF as relevant, vigilance, field-safety actions and change notification rules.	No process to detect/report serious incidents or reassess a changed device.

Important exception to the CE-marking gate: the table describes ordinary CE-marked devices. A qualifying custom-made device follows the specific MDR Article 52(8)/Annex XIII route and does not bear the Article 20 CE mark; investigational devices also have a distinct route. A prescription or patient-specific order does not by itself turn a mass-produced device into a custom-made device.

A class III implantable custom-made device is not free of notified-body oversight: MDR Article 52(8) also requires a quality-management-system conformity assessment under Annex IX Chapter I or Annex XI Part A. Verify the implant class and the qualified custom-made status separately.

Changes that invalidate the initial route map

Re-open the route map when a clinical claim, patient population, algorithm, material, sterilisation method, wireless module, battery, manufacturing site, software function or EU market changes. Not every change changes classification, but the manufacturer must assess effects on risk, technical documentation, notified-body terms, labelling and registration. For legacy MDD/AIMDD products, MDR transitional dates apply only if all statutory conditions are met; never assume an old certificate is a general launch authorisation for a newly designed device. The Commission’s proposed MDR/IVDR simplification of December 2025 is not itself an enacted change to these duties.

Official legal texts and implementation guidance

Use the current consolidated MDR and IVDR texts; the Commission’s EUDAMED deployment page, medical-device guidance, and Member-State language overview explain implementation. MDCG guides are non-binding and must not be cited as legislation.

A body-worn product needs the additional device-specific analysis in EU wearable medical-device route. For Member-State-specific implementation questions, compare medical-device market entry in Italy.

Specific questions before EU launch

Can a wellness app avoid MDR just by dropping the word “diagnosis”?

Not necessarily. Analyse the whole intended purpose, functions, presentation and actual clinical claims. A genuine general-wellness function may fall outside MDR, while software providing patient-specific information for diagnostic or therapeutic decisions may qualify; record the borderline rationale and Rule 11 analysis.

Is a blood-testing device covered by the MDR class I–III scheme?

Usually the first test is IVDR: in-vitro examination of human specimens for medical information falls within IVDR definitions. Determine IVDR class and conformity route separately. Do not transfer MDR classes or certificates. The distinction is the method and intended purpose, not the word “blood”: testing a collected specimen in vitro may be IVDR, while an in-vivo physiological monitor needs its own MDR assessment.

Does every class I medical device need a notified body?

No. Standard non-sterile, non-measuring class I devices generally do not, but sterile, measuring and reusable-surgical class I features bring notified-body involvement for specified aspects. Check the classification rule and Article 52 before proceeding.

Can a non-EU manufacturer place a CE-marked device on the market without an EU authorised representative?

Generally no under MDR Article 11: a manufacturer not established in a Member State must designate a sole EU authorised representative by an accepted written mandate before placing the device on the EU market. An importer has distinct Article 13 checks and does not automatically replace that mandate.

Does MDR CE marking cover Bluetooth, batteries and clinical AI?

Not automatically. A wireless component may trigger RED; electrical equipment, batteries and waste obligations need their own scope assessment; a qualifying AI system may fall under the AI Act. Avoid assuming every such law applies to every device or is displaced by MDR.

Is EUDAMED registration a substitute for CE conformity assessment in 2026?

No. From 28 May 2026 the actor, UDI/device, notified-body/certificates and market-surveillance modules are mandatory in their respective scopes; the last is primarily for authorities. Registration supports traceability but does not establish intended purpose, clinical evidence or a compliant conformity route.