Is your software a medical device under EU MDR? A practical qualification guide

Before any risk class comes into play, there is an earlier question: does the MDR apply to your software at all? That is qualification, and it is decided by the definition in Article 2(1) and by your intended purpose — not by Rule 11, which only classifies software that already is a medical device. Here are the MDCG 2019-11 Rev.1 decision steps, examples of software that does and does not qualify, how accessories and modules are handled, and what to document.

Lizaveta Dabrynskaya
Lizaveta Dabrynskaya
Founder & Regulatory Consultant · 13+ years

Short answer

Software is a medical device under the EU MDR when its manufacturer intends it for a specific medical purpose listed in Article 2(1), such as diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease. The intended purpose (Article 2(12)) comes from your label, instructions for use and promotional and sales materials, so your website and app-store listing count too. MDCG 2019-11 Rev.1 sets out the decision steps. Software that only stores, archives, communicates or performs a simple search on data is generally not a medical device; decision support that applies medical knowledge to an individual patient’s data often is. Only after qualification does Rule 11 set the class.

1. What makes software a medical device?

Article 2(1) of the MDR (Regulation (EU) 2017/745) defines a medical device as any instrument, apparatus, appliance, software, implant, reagent, material or other article intended by the manufacturer to be used, alone or in combination, for human beings for one or more specific medical purposes. For software, the relevant purposes are usually:

  • diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease;
  • diagnosis, monitoring, treatment, alleviation of, or compensation for, an injury or disability;
  • investigation, replacement or modification of the anatomy or of a physiological or pathological process or state.

The definition also covers providing information by means of in vitro examination of specimens derived from the human body. Software whose medical purpose rests on that kind of information may be in vitro diagnostic software under the IVDR rather than the MDR.

The key word is intended. Article 2(12) defines the intended purpose as the use for which a device is intended according to the data supplied by the manufacturer on the label, in the instructions for use or in promotional or sales materials or statements, and as specified in the clinical evaluation. Your website, sales deck and app-store listing are therefore part of the picture, not only the IFU. What the software could technically do does not make it a medical device; what you say it is for can.

Qualification is not classification

Qualification answers whether the MDR applies at all. Classification under Annex VIII — Rule 11 for most software — only starts once the answer is yes. MDCG 2019-11 Rev.1 also states that the risk of harm to patients, users or other persons is not a criterion for whether software qualifies as a medical device: low-risk software with a medical purpose still qualifies.

General-purpose software used in a clinical environment is not a medical device unless the manufacturer gives it a medical intended purpose. A spreadsheet that tracks clinic appointments is not a medical device. A tool built on the same patient data that calculates an individual treatment recommendation very likely is, because it now acts on data, for an individual patient, with a medical purpose.

2. The MDCG 2019-11 Rev.1 decision steps

The reference document for software is the Medical Device Coordination Group guidance MDCG 2019-11 Rev.1, Qualification and classification of software (revised June 2025). It is guidance, not law — the document itself says its views are not legally binding — but Notified Bodies and competent authorities work with it, so your rationale should follow it. Its qualification decision tree has five steps:

  1. Is the product software? The guidance defines software as a set of instructions that processes input data and creates output data. If yes, it may be medical device software (MDSW).
  2. Is it an MDR Annex XVI product, an accessory for a medical device, or software driving or influencing the use of a medical device? If so, it is handled as part of that device's regulatory process, or independently if it is an accessory (see section 4).
  3. Does it perform an action on data beyond storage, archival, communication, simple search or lossless compression? If it does none of these things, it is not MDSW.
  4. Is the action for the benefit of individual patients? Software intended only to aggregate population data, or only for epidemiological studies or registers, does not pass this step.
  5. Does it have a medical purpose within the Article 2(1) definition? If yes, it is MDSW. The guidance then uses a second decision tree to decide whether the MDSW falls under the MDR or the IVDR.
Common mistake

Writing a deliberately vague intended purpose to stay outside the MDR does not work if your marketing says something else. Because the intended purpose includes promotional and sales materials, a product marketed as detecting or predicting a disease will be assessed against that claim.

3. Examples and grey areas

MDCG 2019-11 Rev.1 includes worked examples. Each one depends on the stated intended purpose, so treat them as reference points rather than verdicts on your product.

Typically not medical device software

  • Hospital information systems for patient admission, scheduling or billing — not medical devices in themselves.
  • Electronic health record systems intended primarily to store and transfer patient records.
  • General-purpose communication systems, and telemedicine software that only transfers and displays monitoring information without interpreting it.
  • Image management systems used only for viewing, archiving and transmitting images.
  • Software for non-medical purposes — invoicing, staff planning, wellness or fitness apps without a medical purpose — and simple search functions such as library look-ups.

Typically medical device software

  • Decision support software that combines medical knowledge databases and algorithms with patient-specific data to give recommendations for the diagnosis, prognosis, monitoring or treatment of individual patients.
  • Computer-aided detection software intended to provide information that may suggest or exclude medical conditions.
  • Treatment and dose planning software, such as radiotherapy treatment planning or chemotherapy dose planning.
  • Image management systems that add post-processing functions for diagnostic purposes.
  • Apps that analyse physiological data for a medical purpose — for example, an app that analyses heart rhythm data to alert the user to a possible arrhythmia.

Where the line is often disputed

  • "For physician review only" disclaimers. An AI tool whose output suggests a diagnosis for an individual patient does not stop being MDSW because a clinician reviews the output. Human review matters for classification and risk control, not for qualification.
  • Wellness versus health monitoring. Tracking activity or sleep for general well-being is not a medical purpose. Claims about detecting, monitoring or predicting a disease or condition are.
  • Digital therapeutics. Software intended to treat or alleviate a disease — for example, a programme that delivers a therapeutic intervention for a diagnosed condition — has a medical purpose under Article 2(1).
  • Data platforms with analytics. A platform that stores and displays data is usually not MDSW; a module in it that calculates patient-specific scores or alerts may be (see modules below).

4. Accessories, software that drives a device, and modules

Not every piece of software in a medical product needs its own qualification decision. MDCG 2019-11 Rev.1 distinguishes these situations:

  • Software driving or influencing the use of a (hardware) medical device without a medical purpose of its own — for example, control software or firmware. It is covered by the MDR as a part or component of that device, or as an accessory. Under Annex VIII, Chapter II, section 3.3, software that drives or influences the use of a device falls within the same class as the device.
  • Accessories. Article 2(2) defines an accessory as an article that, whilst not itself a medical device, is intended by its manufacturer to be used together with particular medical device(s) to specifically enable their use in accordance with their intended purpose, or to specifically and directly assist their medical functionality. Accessories are regulated under the MDR and handled independently of the device they are used with.
  • Software with its own medical purpose that also drives a device is qualified as MDSW. Software that is independent of any other device is classified in its own right; where MDSW also drives or influences a hardware device, its class must not be lower than that of the hardware.

Modules. Many products combine medical and non-medical functions. MDCG 2019-11 Rev.1 accepts that a product may be split into modules: modules with a medical purpose fall under the MDR, the others do not. The manufacturer has to delineate the boundaries and interfaces between modules clearly, and non-medical functionality that the MDSW needs in order to operate should not be excluded from the MDSW description. An EHR, for example, is usually not a medical device, but a module integrated into it or running alongside it that fulfils a medical purpose may be.

5. If the answer is not clear

Borderline cases are common. These official reference points help:

  • The European Commission's Manual on borderline and classification under the MDR and IVDR, which sets out positions on specific borderline and classification cases.
  • Your national competent authority. Some authorities give opinions on qualification or classification; whether this is offered, and at what cost, differs between Member States, so check with the authority concerned.
  • At EU level, the Commission can decide by implementing act whether a product or group of products is a medical device, at the duly substantiated request of a Member State or on its own initiative (Article 4 MDR). Disputes between a manufacturer and its Notified Body about the application of the classification rules are referred to the competent authority of the manufacturer's Member State (Article 51(2)).
Practical tip

Write the qualification rationale before you finalise product claims, not after. It is much easier to align the website, the IFU and the sales deck with one agreed intended purpose than to defend inconsistent claims in a Notified Body review.

6. Documenting your qualification decision

The technical documentation must contain the rationale for the qualification of the product as a device (Annex II, section 1.1(e)), alongside the risk class and the justification for the classification rule(s) applied (section 1.1(f)). A qualification rationale that holds up in review usually contains:

  • Intended purpose — medical purpose, intended patient population and medical conditions, intended users and use environment — consistent with the IFU, labelling and marketing material.
  • A walk-through of the MDCG 2019-11 Rev.1 decision steps — with your reasoning at each step, not just the outcome.
  • Module boundaries, if you split the product — which functions are within the scope of the MDR and how the interfaces are controlled.
  • Accessory and combination aspects — any hardware the software drives or is used with.
  • References — MDR Article 2(1), MDCG 2019-11 Rev.1, and any relevant borderline-manual entry or competent-authority opinion.

Where this sits in the wider file is covered in our guide to Annex II technical documentation for software.

7. Next step: classification under Rule 11

If your software qualifies as MDSW, the next question is its risk class. For most software this is decided by Rule 11 of Annex VIII: software intended to provide information used to take decisions with diagnosis or therapeutic purposes is class IIa, or class IIb or III where those decisions may have a more serious impact; software intended to monitor physiological processes is class IIa, or class IIb for vital physiological parameters where variations could result in immediate danger to the patient; all other software is class I. Class I software is generally self-declared by the manufacturer (Article 52(7)); class IIa and above require a Notified Body.

Continue with our guide to EU MDR Rule 11 classification for software, which covers the rule text, how MDCG 2019-11 Rev.1 applies it, worked examples and the pending December 2025 proposal. If you want an independent view on qualification and class before you commit budget to a certification programme, see our regulatory strategy and classification support.

Official sources & references

Related guides

Frequently asked questions

Software is a medical device when its manufacturer intends it to be used, alone or in combination, for one of the specific medical purposes listed in Article 2(1) MDR — for example diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease. The deciding factor is the intended purpose, which Article 2(12) ties to the label, the instructions for use, promotional and sales materials and the clinical evaluation — not what the software could technically do. General-purpose software used in a clinical setting is not a medical device unless it is given a medical intended purpose.
No. Rule 11 (Annex VIII MDR) classifies software that already qualifies as a medical device. Qualification comes first: it is based on the Article 2(1) definition and your intended purpose, and MDCG 2019-11 Rev.1 sets out the decision steps. Software that only stores, archives, communicates or performs a simple search on data is generally not medical device software at all. Only once the software qualifies does Rule 11 decide whether it is class I, IIa, IIb or III.
Often, yes. MDCG 2019-11 Rev.1 qualifies decision support software that combines medical knowledge databases and algorithms with patient-specific data to give recommendations for the diagnosis, prognosis, monitoring or treatment of individual patients as a medical device. Software that only stores, displays or communicates data, performs a simple search, or serves only population-level purposes does not qualify. A "for physician review only" label does not by itself change the intended purpose; human review matters for classification and risk control, not for qualification.
Annex II MDR requires the technical documentation to include the rationale for the qualification of the product as a device (section 1.1(e)) and, separately, the risk class and the justification for the classification rule(s) applied (section 1.1(f)). In practice this means a precise intended purpose (medical purpose, patient population and conditions, users, use environment), a step-by-step walk-through of the MDCG 2019-11 Rev.1 decision tree, module boundaries if only part of the product is medical device software, and consistency with labelling and marketing — because promotional materials form part of the intended purpose.
Check the examples in MDCG 2019-11 Rev.1 and the European Commission's Manual on borderline and classification under the MDR and IVDR. Some national competent authorities give opinions on qualification or classification; availability and any fees differ by Member State. Disputes between a manufacturer and its Notified Body about classification are referred to the competent authority of the manufacturer's Member State (Article 51(2) MDR). A short review of your intended purpose before you commit development budget is usually cheaper than reworking a programme built on the wrong assumption.
Lizaveta Dabrynskaya
Lizaveta Dabrynskaya
Founder, TrustedTraceMed · Regulatory and quality consultant for medical device software

Regulatory and quality consultant for medical device software, with 13+ years in the healthcare domain. Built an ISO 13485 QMS from scratch for a Class IIa SaMD and worked on EU MDR, UKCA and Malaysia MDA submissions. Independent consultant, not a Notified Body.

Not sure how your software qualifies and classifies?

In a free 30-minute call we go through your intended purpose, MDCG 2019-11 and Rule 11, and I tell you how I see the classification.

Request a free call →
No commitment · Fixed-fee proposals · Reply within 1 business day