- Commission page explaining that notified bodies assess conformity when third-party intervention is required and that designated bodies are listed publicly.
"to assess the conformity of certain products"
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.
Structured answer sets in this page tree.
Cited legal and guidance references.
EU MDR classification is a risk-based legal and technical decision. Start from the manufacturer-stated intended purpose, 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.
The classification record should begin with the intended purpose 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.
Annex VIII is not a checklist of product categories; it is a sequence of definitions, implementing rules, and device-type rules. 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.
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.
Use Sorena to convert intended-purpose claims, Annex VIII rules, Rule 11 software logic, and conformity route consequences into a cited classification rationale.
Classification is not just a label. It 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. Specific class I cases can still require notified body involvement, such as sterile condition, measuring function, reusable surgical instruments, or software class changes triggered by Annex VIII.
A classification rationale should let a reviewer reproduce the decision without interviewing the product team. The document should show the intended purpose 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.
"to assess the conformity of certain products"
"MDSW should be classified in the same way, regardless of the software's location"
"The criteria can then be applied"
"risk classification and applicable classification rule pursuant to Annex VIII"