Short answer

Under EU MDR Rule 11 (Annex VIII, section 6.3), software that provides information used to take diagnostic or therapeutic decisions is class IIa; class IIb if those decisions may cause a serious deterioration of health or a surgical intervention; class III if they may cause death or an irreversible deterioration of health. Software that monitors physiological processes is class IIa, or IIb when it monitors vital parameters whose variations could result in immediate danger. All other medical device software is class I. MDCG 2019-11 Rev.1 explains how to apply the rule. The December 2025 proposal to rewrite Rule 11 is not adopted, so plan on the current text.

Why the class matters

Once you know your software is a medical device, its class drives most of what follows: whether a Notified Body must be involved, which conformity assessment routes are open to you, how much clinical evidence will be scrutinised, and which post-market reports you have to produce and how often. Under EU MDR, the class of most software is set by Rule 11 of Annex VIII.

Misclassification is more common than the industry acknowledges. We have seen software teams declare class I for products that fall into class IIa under Rule 11 — and discover the error when a Notified Body review reveals the mismatch. We have also seen teams over-classify in the other direction, building class IIb documentation for what is a class IIa device. Both errors are costly.

Qualification comes first: Rule 11 only classifies software that already qualifies as a medical device. Whether it qualifies depends on Article 2(1) MDR and your intended purpose, following the decision steps in MDCG 2019-11 Rev.1. Purely administrative software, software that only stores, archives or communicates data, general wellness apps and software that only aggregates population data typically do not qualify. Our guide Is your software a medical device under EU MDR? walks through those steps.

Rule 11: the text, explained

Rule 11 (Annex VIII, section 6.3 MDR) has three parts, which MDCG 2019-11 Rev.1 refers to as sub-rules 11a, 11b and 11c.

Rule 11a — information used for decisions. Software intended to provide information which is used to take decisions with diagnosis or therapeutic purposes is:

  • Class III if such decisions have an impact that may cause death or an irreversible deterioration of a person's state of health;
  • Class IIb if such decisions have an impact that may cause a serious deterioration of a person's state of health or a surgical intervention;
  • Class IIa in all other cases.

Rule 11b — monitoring. Software intended to monitor physiological processes is:

  • Class IIb if it is intended for monitoring of vital physiological parameters, where the nature of variations of those parameters is such that it could result in immediate danger to the patient;
  • Class IIa in all other cases.

Rule 11c — everything else. All other software is class I.

Three points are often misread:

  • Class I is the residual category, not the "storage" category. Software that only stores, archives, communicates or performs a simple search on data is generally not medical device software at all, so Rule 11 never applies to it. Class I under Rule 11c is for software that qualifies as a medical device but neither provides information used for diagnostic or therapeutic decisions nor monitors physiological processes — MDCG 2019-11 Rev.1 gives a fertility-tracking app and a symbol-based communication app as examples.
  • Rule 11b covers all physiological processes, not only vital ones. Monitoring of non-vital physiological processes is class IIa; continuous surveillance of vital physiological processes, for example in anaesthesia, intensive care or emergency care, is class IIb.
  • The strictest rule applies. Software is an active device, so Rules 9, 10, 12, 13, 15 and 22 may also be relevant. Where several rules or sub-rules apply, the strictest one resulting in the higher class applies (Annex VIII, Chapter II, section 3.5). Software that drives or influences the use of a device falls within the same class as that device (section 3.3).

How MDCG 2019-11 Rev.1 helps apply Rule 11a

The guidance links Rule 11a to two factors taken from the IMDRF framework: the significance of the information to the healthcare decision (to treat or diagnose, to drive clinical management, or to inform clinical management) and the state of the healthcare situation or patient condition (critical, serious or non-serious). Its illustrative table in Annex III maps them to MDR classes:

  • Critical situation: treat or diagnose → class III; drive clinical management → class IIb; inform clinical management → class IIa.
  • Serious situation: treat or diagnose → class IIb; drive or inform clinical management → class IIa.
  • Non-serious situation: class IIa in all three cases.

The table is explicitly illustrative, does not cover class I (Rule 11c) software, and the guidance does not define these terms in detail. Your justification still has to argue from the wording of Rule 11 itself: what decisions the information is used for, and what impact a wrong decision may have.

Applying Rule 11 in practice: worked examples

The examples below show the reasoning, not a determination for any real product. The class always depends on the exact intended purpose, the intended patient population and how the output is used in the clinical workflow.

AI diagnostic imaging software (ophthalmology)

Intended use: "Automated analysis of retinal photographs to assist ophthalmologists in identifying findings consistent with diabetic retinopathy for diagnostic review."

Classification analysis: The software provides information (an algorithmic assessment of retinal images) used to take decisions with diagnostic purposes, so Rule 11a applies. The question is the impact a wrong decision may have: diabetic retinopathy can lead to serious and, if missed, potentially irreversible loss of vision, so the justification has to explain why class III does not apply and whether class IIb does. Using the MDCG 2019-11 Rev.1 table, information that drives clinical management (for example, referral) in a serious situation points to class IIa, while software intended to diagnose in a serious situation points to class IIb. Whether the software "assists" or "diagnoses" must be visible in the intended purpose, the IFU and the real workflow — not only in the wording.

Classification: Class IIa or IIb depending on intended purpose and workflow, with an explicit argument why class III does not apply.

Clinical decision support — antibiotic stewardship

Intended use: "Recommends antibiotic selection and dosing for hospital patients based on patient data, microbiology results, and local resistance patterns, for physician review and approval."

Classification analysis: The software provides information (antibiotic recommendations) used to take decisions with therapeutic purposes. Incorrect antibiotic selection or dosing can cause a serious deterioration of a patient's health. Physician approval is relevant to the significance of the information, but it does not take the software out of Rule 11a. If the intended population includes critically ill patients, where a wrong decision may cause death or an irreversible deterioration, class III has to be considered and either justified away or accepted.

Classification: Class IIb as the working hypothesis, with the class III question addressed explicitly for the intended population.

Remote patient monitoring — post-operative vital signs

Intended use: "Continuous monitoring of heart rate, oxygen saturation, and respiratory rate in post-operative patients, with alerts for values outside predefined clinical thresholds."

Classification analysis: This is software intended to monitor vital physiological parameters, and variations in these parameters (post-operative deterioration, hypoxia) could result in immediate danger to the patient. That is the class IIb limb of Rule 11b, not the class IIa default. Because the alerts are also information used to take therapeutic decisions, Rule 11a should be checked as well and the stricter outcome applied.

Classification: Class IIb.

Not sure which class applies to your software? In a 1.5-hour strategy session (€200) we go through your intended purpose, the likely class and the route to market. Start with a free 30-minute call.
Request a free call →

The December 2025 proposal: what it would change in Rule 11

On 16 December 2025 the European Commission proposed a regulation to simplify the MDR and IVDR (COM(2025) 1023, procedure 2025/0404(COD)). Its annex would replace the text of Rule 11. Under the proposed wording, software intended to generate an output that confers a clinical benefit, and used for diagnosis, treatment, prevention, monitoring, prediction, prognosis, compensation or alleviation of a disease or condition, would be class I, unless the output is intended for a disease or condition:

  • in a critical situation with a risk of causing death or an irreversible deterioration of a person's state of health — class III;
  • in a serious situation with a risk of causing a serious deterioration of a person's state of health or a surgical intervention, or to drive clinical management in a critical situation — class IIb;
  • in a non-serious situation, or to drive clinical management in a serious situation, or to inform clinical management in a critical or serious situation — class IIa.

The proposed rule has no separate monitoring sub-rule. The Commission's explanatory memorandum describes the change as adapting classification rules so that certain devices, including software, end up in lower risk classes. How far that would go in practice depends on the final wording and on how terms such as "critical situation" and "drive clinical management" are interpreted.

Status: as of October 2026 the proposal has not been adopted. In the Council it is still being examined at working-party level — the Council's June 2026 progress report records no general approach yet — and in the European Parliament the lead committee (SANT) is preparing its report, with a plenary position expected in early 2027 according to that progress report. Parliament and Council then have to agree a final text, which must be published in the Official Journal; application dates and any transitional arrangements will be set in that text. Until then, the current Rule 11 applies.

Do not base your certification strategy on the proposal. Plan for the current Rule 11 as it stands. If an amended rule is adopted and your device would fall into a lower class, the transitional provisions of the final text will determine what you can change and when. You cannot afford to wait for a legislative outcome whose content and timing are not yet known.

Writing a defensible classification justification

Your classification is not a decision you make once and forget — it is a documented position that the technical documentation must justify (Annex II, section 1.1(f) requires the risk class and the justification for the classification rule(s) applied) and that Notified Bodies will scrutinise. A weak or unsupported justification generates questions at the start of the review. A robust Rule 11 classification document includes:

  • Intended purpose: Specific, precise, unambiguous. Defines the medical purpose, patient population and medical conditions, intended users and clinical context — consistent with your IFU and marketing material.
  • Qualification analysis: Why the software qualifies as medical device software under EU MDR, following MDCG 2019-11 Rev.1.
  • Rule 11 analysis: Which sub-rule applies (11a, 11b or 11c) and why, with explicit reasoning about the decisions the information supports and the impact a wrong decision may have — not just a statement of the class.
  • Consideration of other rules: Confirmation that no other classification rule (for example Rules 9, 10, 12, 13, 15 or 22) results in a higher class, since the strictest rule applies.
  • Device combinations: If the software drives or influences the use of a hardware device, it falls within the same class as that device; if it has its own medical purpose and also drives a device, its class must not be lower than the device's.

If you want an independent check of your qualification and classification rationale before you commit to a certification plan, see our regulatory strategy and classification support. For what the class means for time and budget, see our guide to a realistic EU MDR timeline for software.

Official sources & references