Intended Use is the manufacturer’s formal statement of what a medical device is for: its medical purpose, target users, patient population, and use environment. It defines the device’s regulatory identity, drives classification, and sets the scope for risk management, verification, validation, and labeling. In EU law, the equivalent term is intended purpose.
What is Intended Use?
Intended Use is the anchor statement that tells regulators, notified bodies, and users what a device does and for whom. Under US rules, it appears at 21 CFR 801.4, which ties intended use to the objective intent of the people legally responsible for the labeling. The European equivalent, intended purpose, is defined in Article 2(12) of EU MDR 2017/745 as the use for which a device is intended according to the label, instructions for use (IFU), and promotional materials.
The statement sits at the very start of the device lifecycle. Before a single requirement is written, it decides whether a product is a medical device at all, and if so, which class it falls into.
Why Intended Use matters in medical device development
A precise Intended Use statement controls the entire regulatory pathway. It determines device class (I, II, or III under FDA; I, IIa, IIb, or III under EU MDR), which in turn sets the submission route: 510(k), De Novo, or PMA in the US, and the conformity assessment route in Europe.
Get it wrong, and the cost is real. An overly broad statement invites extra clinical evidence, a larger validation scope, and tougher scrutiny. Too narrow, and the marketing team may promote uses that the labeling does not cover, which the FDA can treat as off-label promotion or misbranding. Auditors and notified bodies check that the intended use in the technical file matches the IFU, the risk file, and the clinical evaluation. Any mismatch becomes a finding.
How Intended Use works
An Intended Use statement is short, usually two or three sentences, but every clause carries regulatory weight. A well-formed statement covers:
- Medical purpose: diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation of disease.
- Target patient population: the age, condition, or anatomy the device is meant for.
- Intended users: clinicians, trained operators, or lay users.
- Use environment: hospital, home, point of care, or ambulance.
- Body part or physiological process the device acts on.
That statement then feeds every downstream activity. Risk management under ISO 14971 starts from the intended use to identify hazards and foreseeable misuse. Usability work under IEC 62366-1 defines use scenarios from it. Design verification and validation confirm the device meets requirements derived from it. For software, IEC 62304 scopes the safety classification against it. In the US, teams also write a separate Indications for Use statement, naming the specific clinical conditions and populations the device is cleared or approved for. Intended use is the broad frame; indications for use are the specific claims inside it.
Common challenges and best practices
The most frequent mistake is drift: the intended use in the technical file says one thing, the website says another, and the sales deck says a third. Regulators read all of them. Keep one controlled statement and propagate it everywhere.
Teams also confuse intended use with indications for use, or swap the EU and US terms as if they were identical. They are related but distinct, and mixing them creates review questions. Another trap is writing the statement late, after design is frozen, when changing it forces expensive rework of the risk file and validation protocols.
Good practice is to draft the intended use in the concept phase, review it with regulatory affairs before design inputs are locked, and treat any change to it as a formal change control event. When the statement is stable and specific, classification, testing scope, and labeling fall into place with far less friction.
How SJML helps with Intended Use
SJML’s Compliance-as-a-Service team works with device makers to define and pressure-test intended use and intended purpose statements early, when they are cheapest to get right. Its regulatory specialists align the statement with device classification, technical documentation, and DHF, clinical evaluation, and labeling across FDA, EU MDR, and IVDR frameworks, so the wording stays consistent from concept through submission. Because SJML also handles design, risk management, and manufacturing under one roof, the intended use you agree on flows directly into verification, validation, and post-market planning without translation loss between teams.
Frequently asked questions
Intended Use is the broad statement of a device’s medical purpose, users, and environment. Indications for Use are narrower: the specific clinical conditions, patient populations, and settings the device is cleared or approved to address. FDA submissions require both. The intended use frames the device; the indications for use list the exact claims supported by evidence.
They mean the same core concept but come from different regulations. US law (21 CFR 801.4) uses intended use; EU MDR 2017/745 uses intended purpose, defined in Article 2(12). For a device sold in both markets, the statements should describe the same function, worded to satisfy each framework. Keeping them aligned avoids inconsistencies that auditors and notified bodies flag.
Classification depends directly on intended use. Regulators read the statement to decide the risk class, which sets the submission route and the level of controls. A device intended to monitor a non-critical parameter may be low risk; the same hardware intended to drive a treatment decision may jump classes. This is why the statement must be settled before classification is finalized.
The manufacturer owns the intended use. Under FDA rules, it reflects the objective intent of those legally responsible for the labeling, shown through labeling, IFU, and promotional materials. In practice, regulatory affairs, engineering, and marketing draft it together, but regulatory affairs controls the final wording so it stays consistent across the technical file and every customer-facing document.
Related terms
- Indications for Use
- Device Classification
- Instructions for Use (IFU)
- Intended Purpose (EU MDR)
- Design Inputs
