Use intended purpose and Annex VIII to decide whether a product is class I, IIa, IIb, or III under Regulation (EU) 2017/745.
This guide focuses on duration, invasiveness, active-device status, software Rule 11, conformity route consequences, and the evidence needed to defend the classification rationale.
EU MDR classification is a risk-based legal and technical decision. Start from the manufacturer-stated , apply the Annex VIII definitions and rules, use the highest applicable class where several rules fit, and keep a rationale that links the device claims, evidence, and conformity assessment route.
1
Section 1
Start with intended purpose
The classification record should begin with the supplied by the manufacturer: indications, target patient population, users, use environment, body site, mode of action, duration of contact, and whether the product is standalone software, an accessory, a system component, or a device in its own right.
Do not classify from marketing shorthand. Check labels, instructions for use, clinical claims, software outputs, risk-management files, and product variants for claims that change the intended medical purpose. A new diagnostic, monitoring, therapeutic, invasive, implantable, or active function can move the device into a different Annex VIII rule or class.
Record the exact device model, Basic UDI-DI where available, version or configuration, and the claims being classified.
Separate accessories from the parent device: Annex VIII says accessories are classified in their own right.
For combined use, classify each device separately unless the MDR treats the combination as a system, procedure pack, or a device in its own right.
If more than one rule or sub-rule applies to the , use the strictest applicable outcome.
Annex VIII combines definitions, implementing rules, and device-type rules rather than assigning classes by product category. Work through duration, invasiveness, body site, active-device function, substances, special materials, and software before selecting the class.
Duration is measured as continuous use: transient means less than 60 minutes, short term means 60 minutes to 30 days, and long term means more than 30 days. For replaceable devices, Annex VIII can count accumulated use where the manufacturer intends immediate replacement with another of the same type.
If the product is an active Annex XVI product without a medical purpose, check binding reclassification before accepting Rule 13 class I. Implementing Regulation (EU) 2022/2347 makes skin-treatment high-intensity electromagnetic radiation equipment class IIb, except hair-removal-only equipment is class IIa; adipose-tissue reduction, removal, or destruction equipment is class IIb; and covered brain-stimulation equipment is class III.
For non-invasive devices, start with Rule 1, then check channelling or storage, biological or chemical modification, contact with injured skin or mucous membrane, and special substance rules.
For invasive devices, identify body-orifice use, surgical invasiveness, implantable status, duration, body site, absorption, biological effect, ionising radiation, medicinal product administration, and direct contact with the heart, central circulatory system, or central nervous system.
For active devices, decide whether the device administers or exchanges energy, diagnoses or monitors, emits ionising radiation, administers or removes substances, controls an active implantable device, or falls into the active-device fallback.
Check special rules for ancillary medicinal substances, contraception or sexually transmitted disease prevention, cleaning or sterilisation, X-ray image recording, non-viable tissues or cells, nanomaterials, inhalation administration, substance-based devices, and active therapeutic devices with integrated diagnostic functions.
Software classification needs two decisions before the class outcome: whether the software qualifies as medical device software under the MDR, and whether it drives or influences a hardware device or is independent. Annex VIII treats software as an active device, and software that drives or influences another device falls within the same class as that device.
Rule 11 applies to software that provides information used for diagnostic or therapeutic decisions or monitors physiological processes. The risk analysis should explain the significance of the software output, the healthcare situation or patient condition, the intended population, context of use, and likely impact of incorrect information.
Class IIa is the baseline for software providing information used for diagnostic or therapeutic decisions.
Class III applies where those decisions may cause death or irreversible deterioration of health.
Class IIb applies where those decisions may cause serious deterioration of health or surgical intervention.
Software monitoring physiological processes is class IIa unless it monitors vital physiological parameters where variations could immediately endanger the patient, in which case it is class IIb.
All other software is class I, but only after documenting why the higher Rule 11 branches and any hardware-driving rule do not apply.
Turn MDR classification into a reviewable evidence file
Use Sorena to convert intended-purpose claims, Annex VIII rules, Rule 11 software logic, and conformity route consequences into a cited classification rationale.
Classification determines the conformity assessment route, notified body involvement, technical documentation review depth, clinical evidence expectations, certificate content, and the resources needed before market placement.
As a general rule under the MDR recitals, class I conformity assessment is carried out under the manufacturer's responsibility because of lower vulnerability, while class IIa, IIb, and III devices require an appropriate level of notified body involvement. Class I devices placed on the market in sterile condition, devices with a measuring function, and reusable surgical instruments still require notified body involvement for the limited aspects stated in Article 52(7).
For class I, confirm whether the device is plain class I or has a class I feature that requires notified body involvement for limited aspects.
For class IIa and IIb, plan notified body selection, QMS assessment, representative technical documentation sampling, and clinical evaluation evidence early.
For class III, expect the highest scrutiny, including technical documentation assessment and any applicable consultation or expert-panel pathway.
For each route, align the classification memo with the EU declaration of conformity, technical documentation, clinical evaluation, PMS/PMCF planning, UDI/device registration, and certificate scope.
A classification rationale should let a reviewer reproduce the decision without interviewing the product team. The document should show the reviewed, the Annex VIII definitions applied, each candidate rule considered, the selected class, the conformity route consequence, and the evidence that supports or excludes higher-risk rules.
Reopen the rationale when claims, labels, instructions for use, software functionality, energy delivery, body contact, material composition, duration of use, target population, clinical use environment, or combination with another device changes. The same trigger list should be connected to design-change control and notified body communication where certificates or approved technical documentation are affected.
Include a rule table with columns for fact pattern, Annex VIII rule, class result, reason included or excluded, and evidence reference.
Attach intended-purpose evidence: label and IFU extracts, clinical claims, software functional specification, risk analysis, usability assumptions, and product-variant boundaries.
For software, retain the qualification decision, Rule 11 branch, hardware-driving or influencing analysis, patient-condition analysis, and failure-impact rationale.
For active or invasive devices, retain body-contact, duration, energy, substance, absorption, material, and body-site evidence.
Tie the final class to conformity assessment planning: notified body need, application scope, certificate scope, technical documentation sampling, and clinical evaluation depth.
If the manufacturer and notified body dispute Annex VIII application, route the dispute under Article 51(2) to the identified competent authority and retain that decision.
Commission page explaining that notified bodies assess conformity when third-party intervention is required and that designated bodies are listed publicly.
The June 2025 revision explains software qualification, modular software, software driving or influencing device use, and Rule 11 classification logic.
"MDSW should be classified in the same way, regardless of the software's location"