Intended Purpose

Intended purpose (EU MDR) is the use for which a medical device is intended, based on the manufacturer’s label, instructions for use, promotional materials, and clinical evaluation. Defined in Article 2(12) of Regulation (EU) 2017/745, it determines whether a product qualifies as a device and drives its classification and evidence requirements.


What is the intended purpose under the EU MDR?

Intended purpose sits at the very start of the regulatory pathway. Under EU MDR 2017/745, Article 2(12) defines it as the use for which a device is intended according to the data the manufacturer supplies on the label, in the instructions for use, in promotional or sales materials, and as specified in the clinical evaluation. It is a short statement, usually two or three sentences, describing what the device does and for whom.

The concept overlaps with the FDA term “intended use,” and the two are often used interchangeably in Europe. Related but distinct is the “indication,” which MDCG 2020-6 describes as the clinical condition the device diagnoses, treats, monitors, or manages. Intended purpose answers what the device is for; indications describe when it is used.


Why does the intended purpose matter in medical device development

A poorly written intended purpose creates problems that surface late and cost the most to fix. Three consequences follow directly from how you scope it.

First, it decides whether the EU MDR applies at all. If the stated purpose meets the Article 2(1) definition of a medical device, the regulation governs the product; if it does not, a different framework may apply.

Second, it sets the device class. Classification under Annex VIII reads from the intended purpose: duration of contact, invasiveness, and whether the device is active all flow from what you claim the device does.

Third, it fixes the scope of your evidence. The clinical evaluation under Article 61 assesses the device only within its stated purpose, so an overclaim widens the evidence burden, while an underclaim can block a message you need. Notified bodies check the intended purpose for consistency across the technical documentation, and a mismatch between the label, the risk file, and the clinical evaluation is a common audit finding.


How the intended purpose works under the EU MDR

Writing an intended purpose is a structured task, not a marketing exercise. MDR Annex I Chapter III and Annex II Section 1.1 list what the statement and the technical documentation must cover. IEC 62366-1 asks for the same core content in its use specification (clause 5.1), and ISO 14971:2019 treats that specification as an input to risk analysis. A workable intended purpose addresses:

  • Medical purpose: the disease, injury, or condition the device diagnoses, prevents, monitors, treats, or predicts.
  • Patient population: who the device is used on, including age, health status, and selection criteria.
  • Intended user: who operates the device, from trained clinicians to lay users, described by relevant skills.
  • Use environment: where the device is used, such as a hospital, ambulance, or home.
  • Body part and mode of action: the tissue or anatomy involved and the principle by which the device works.
  • Contraindications and exclusions: what the device must not be used for.

The statement then propagates through the file. It seeds the use specification in the Usability Engineering File, frames the hazards analyzed under ISO 14971, scopes the literature search and clinical data in the CER, and must match the wording on the label and in the instructions for use. IEC 60601-1 draws on the same description to fix the application environment for electrical safety testing. Because so many documents inherit it, the intended purpose is written early and placed under change control.


Common challenges and best practices

The most frequent mistake is drafting the intended purpose as sales copy. Vague or aspirational wording (“supports wellness,” “improves outcomes”) fails to define a testable scope and invites questions from a notified body. Write in plain clinical language a reviewer can verify.

A second problem is inconsistency. Teams update the label or the IFU without revising the risk file or the CER, so the same device carries three slightly different purposes. Keep one controlled source and reference it everywhere.

Overclaiming is a third trap. Every claim has to be backed by clinical evidence, so adding an indication you cannot support enlarges the evidence burden rather than the market. An intended purpose that is too narrow can leave a legitimate use unsupported. Good practice is to fix the intended purpose during concept and feasibility, review it at each design phase gate, and treat any change as a trigger for reclassification and evidence review.


How SJML helps with the intended purpose

Syrma Johari MedTech (SJML) works with device teams to define and document the intended purpose as part of its Compliance-as-a-Service offering. Regulatory specialists help draft the statement, confirm device classification under EU MDR and IVDR, and check that the wording stays consistent across the technical file, the risk management file, and the clinical evaluation. Because SJML also runs design, usability engineering, and clinical evaluation in-house, the intended purpose can be traced from concept through the use specification and CER without handoffs between vendors. This reduces the rework that follows a late change of scope.

Talk to SJML’s QARA team →


Frequently asked questions

What is the difference between intended purpose and intended use?

Under EU MDR, intended purpose is the formal term defined in Article 2(12), covering the use a manufacturer specifies on the label, in the instructions for use, and in the clinical evaluation. Intended use is the equivalent FDA term. In Europe, the two are used interchangeably, and standards such as ISO 14971:2019 treat them as the same concept.

Where is the intended purpose defined in the EU MDR?

The intended purpose is defined in Article 2(12) of Regulation (EU) 2017/745. The content requirements for the statement appear in Annex I, Chapter III, and Annex II, Section 1.1, which set out what the technical documentation must describe. MDCG 2020-6 gives further guidance on drafting the intended purpose and distinguishing it from indications and claims.

How does intended purpose affect device classification?

Classification under Annex VIII of the EU MDR reads from the intended purpose. Factors such as how long the device contacts the body, whether it is invasive or implantable, whether it is active, and whether it delivers or measures energy all come from the stated purpose. A change to the intended purpose can move a device into a higher or lower class, which is why it is fixed before classification is finalized.

Who is responsible for defining the intended purpose?

The manufacturer defines the intended purpose and carries full responsibility for it. The statement should be drafted with clinical input so it uses accurate medical language for the intended users, then reviewed by regulatory and quality functions to confirm it aligns with the label, the risk file, and the clinical evaluation. It is best set during concept and kept under change control.


Related terms

  • Intended Use
  • Clinical Evaluation
  • Medical Device Classification
  • General Safety and Performance Requirements (GSPR)
  • Use Specification

Table of Contents

Free EU MDR Technical Documentation Compliance Checklist

Understand documentation gaps and use our single-window worksheet to prepare for Notified Body review.

Related Glossaries

Ask Sygma AI

AI-Powered Assistant

SJ Assistant