ClassificationEU

EU Medical Device Regulation (MDR) 2017/745 Device Classification Guide

Classify your device with a memo reviewers can follow.

Classification drives conformity route, notified body involvement, clinical evidence depth, and PMS/PSUR obligations - so treat it as a controlled decision.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 22, 2026

Updated

Feb 22, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 22, 2026

Updated Feb 22, 2026

Overview

Device classification under MDR Annex VIII is not a best guess - it is a reasoning chain. The fastest path to approval is a classification memo that clearly states the device characteristics, which rules apply, and why alternative rules do not apply. This page gives you a practical, repeatable classification workflow, including software Rule 11 guidance.

Section 1

Start with a classification memo (the artifact that prevents churn)

Write one classification memo per device family and intended purpose. Keep it versioned and tie it to change control (especially for software updates or material changes).

A good memo is short, explicit, and cites the exact Annex VIII implementing rules and classification rules used.

Device facts: intended purpose, users, use environment, anatomical site, contact duration, invasiveness, energy sources, measurement/control functions.
Classification path: implementing rule or rules used, classification rule or rules applied, resulting class, and justification for non-applied rules.
Downstream impacts: conformity assessment route, notified body involvement, clinical evidence expectations, PMS/PSUR and vigilance planning.

Recommended next step

Use EU Medical Device Regulation (MDR) 2017/745 Device Classification Guide as a cited research workflow

Research Copilot can take EU Medical Device Regulation (MDR) 2017/745 Device Classification Guide from clarifying scope and applicability with cited answers to a reusable workflow inside Sorena. Teams working on EU Medical Device Regulation (MDR) 2017/745 can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Research workflow

Open Research Copilot for EU Medical Device Regulation (MDR) 2017/745 Device Classification Guide

Start from EU Medical Device Regulation (MDR) 2017/745 Device Classification Guide and answer scope, timing, and interpretation questions with cited outputs.

Explore next step

Talk to Sorena

Talk through EU Medical Device Regulation (MDR) 2017/745

Review your current process, evidence gaps, and next steps for EU Medical Device Regulation (MDR) 2017/745 Device Classification Guide.

Explore next step

Section 2

A practical Annex VIII workflow (how to apply the rules without getting lost)

Annex VIII has implementing rules (how to use the rules) and classification rules (what class results). Use this sequence to keep decisions consistent across documents.

Output: a classification memo that your technical file and CER can reference consistently.

1) Confirm qualification and intended purpose (classification is meaningless if scope is wrong).
2) Determine device type: invasive/non-invasive, active/non-active, implantable, reusable surgical instrument, measuring function, sterile supply.
3) Decide contact duration and anatomical site; be consistent with IFU and clinical evaluation population/use scenario.
4) Apply relevant rule families (non-invasive, invasive, active, special rules) and document why others don't apply.
5) Re-check edge cases: accessories, systems/procedure packs, software controlling/driving devices, and decision support outputs.

Section 3

Software classification: Rule 11 and the medical device software decision

Software often fails classification reviews because the intended purpose and outputs are ambiguous. Make the clinical context explicit: what decision is being influenced and what harm could occur if the output is wrong.

Control: include UI screenshots and output descriptions in the classification memo and keep them aligned to claims.

Decide whether the software itself has a medical purpose (vs administrative or general wellness).
If software drives/influences a device, document the relationship and shared risk controls.
Apply Rule 11 with explicit reasoning tied to the output's impact (information used for decisions, monitoring physiological processes, etc.).
Document change impact: algorithm updates, model retraining, new inputs, and performance changes should trigger reclassification review.
Tie software classification to clinical evaluation and PMS: model drift, false positives/negatives, and post-market monitoring plans.

Section 4

Common classification pitfalls (and how to avoid them)

Most classification issues are consistency issues: labeling says one thing, UI outputs imply another, and the classification memo uses a third interpretation.

Use these as pre-review checks before you lock the classification.

Claims creep: marketing adds diagnosis/monitoring language that changes classification.
Duration ambiguity across transient, short-term, and long-term use not defined consistently across documents.
Accessory vs device confusion: accessories have MDR obligations and can change route and evidence depth.
Software output ambiguity: for information only disclaimers don't help if users rely on outputs clinically.
Not capturing variants: family-level differences that trigger different rules should be documented explicitly.

Primary sources