Context card
The intended purpose as the semantic anchor of the technical file
Why is the intended purpose the reference point of every document in a medical-device technical file?
The short answer
Because the MDR defines the intended purpose as the use for which a device is intended according to the manufacturer’s label, IFU, promotional material and clinical evaluation (Article 2(12)), and every other part of the file refers back to it: classification, risk management, GSPR, clinical evidence and labeling. When the IFU says something the clinical evaluation does not support, that is not a style problem but an evidence failure.
For: Technical writers, regulatory affairs and marketing teams of medical device manufacturers
Key points
- MDR Article 2(12) names the label, the IFU, promotional or sales materials and the clinical evaluation as where the intended purpose is stated.
- Classification, risk management and the GSPR checklist are all read against it.
- The clinical evaluation proves benefit and performance for it, not for more.
- An IFU, a website or a sales deck that widens it creates a claim without evidence.
- In an information model, the intended purpose is the node every other element points to.
The context
One definition, many places
The intended purpose under the MDR is 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 or statements and as specified in the clinical evaluation (Article 2(12)). Annex II asks for it in the device description: intended patient population, medical conditions, indications, contra-indications, warnings, intended users.
That is why it is the semantic anchor: the term every other part of the file is defined against.
What hangs on it
- Classification under Annex VIII depends on the intended purpose (device classification).
- Risk management under ISO 14971 starts from the intended use and reasonably foreseeable misuse.
- The GSPR of Annex I are answered for the device as intended (GSPR).
- Clinical evaluation demonstrates safety, performance and clinical benefit for that purpose (clinical evaluation).
- Labeling and IFU state it to users (labeling and IFU).
When the IFU contradicts the clinical evaluation
An IFU that names an indication the clinical evaluation does not cover, a population the data do not include, or a claim of superiority without data has widened the intended purpose without evidence. A notified body will treat that as a gap in the evidence, not as wording. The same applies to promotional material, which the MDR names in the definition itself; a claims matrix keeps every claim tied to its evidence (see claims to evidence).
In an information model
Model the intended purpose as one controlled object with its parts (indication, population, users, setting, contra-indications), give it a version, and let classification, risk file, clinical evaluation and IFU reference it instead of restating it. Then a change of the intended purpose shows every document it touches — the path the evidence chain map draws.
Questions readers ask next
- Is intended purpose the same as intended use?
- The MDR uses intended purpose; intended use is common in ISO 14971 and US usage. In the machine safety glossary, intended use has its own entry under machinery law — keep the contexts apart.
- Can marketing change the intended purpose?
- Yes, in effect: the MDR definition includes promotional and sales materials. A claim there that the file does not support is a problem for the file.
Sources
- Regulation (EU) 2017/745 on medical devices (MDR) — EUR-Lex, May 5, 2017Law in force: Binding legislation that applies as of the review date.
- EN ISO 14971:2019/A11:2021 Medical devices — Application of risk management to medical devices — ISO / CEN, December 2019Harmonized standard (cited): A harmonized standard whose reference is published in the Official Journal of the EU; applying it can give a presumption of conformity for the requirements it covers.
Review log and changes
Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.
Reviewed
No corrections or additions since publication.