Intended use

What it is

Intended Use (US) / Intended Purpose (EU) states what the device does, who uses it, and where it is used. It appears in labeling and files and, in turn, drives claims, class, testing, and review (21 CFR 801.4; MDR 2017/745 Art. 2(12), Annex I Ch. III). Clear wording reduces risk and guides safe, effective use.

Regulatory framework

• United States (FDA): Objective intent comes from labeling, ads, and how you market the device (21 CFR 801.4). Indications for use go in submissions and labels (e.g., 510(k) summary at 21 CFR 807.92). If you change intended use, you may need a new 510(k) or PMA supplement (21 CFR 807.81(a)(3); 21 CFR 814.39).
• European Union (MDR/IVDR): “Intended purpose” guides class rules (MDR/IVDR Annex VIII §1.2), clinical or performance evaluation (MDR Annex XIV; IVDR Annex XIII), and label content (MDR Annex I Ch. III). It covers IFU and promo materials (MDR Art. 2(12); IVDR Art. 2(12)).
• Standards: ISO 14971 links risk work to intended use and foreseeable misuse. IEC 62366-1 (usability) and IEC 62304/IEC 82304-1 (software) align user needs and software safety class with the stated purpose.

Key elements

• Clinical intent: Diagnose, monitor, treat, prevent, or compensate; include body site or condition.
• Population & user: Adult, pediatric, lay, or professional; name the operator.
• Setting & duration: Hospital, home, ambulance, or lab; transient, short-, or long-term; single-use or reusable.
• How it works: Mode of action, key specs, software role (SaMD), and any connectivity.
• Limits: Contraindications, warnings, and use limits that bound safe use.

Process — how it works

• Define: First, write a tight statement that covers condition, user, setting, and measurable claims; then align it with risk and usability (ISO 14971; IEC 62366-1).
• Classify: Next, apply the class rules that follow from the purpose (EU Annex VIII; US device class/panel). Choose the pathway (EU Annex IX–XI; US 510(k)/De Novo/PMA).
• Plan evidence: After that, build a clinical or performance plan that proves each claim (MDR Annex XIV; IVDR Annex XIII; 21 CFR 812 if a study is needed).
• Label & validate: Then translate the statement into IFU and run design validation to show users can achieve the claims (MDR Annex I Ch. III; 21 CFR 820.30(g)).
• Control changes: Finally, assess any new claim or population; if it shifts intended use, submit the required update (21 CFR 807.81(a)(3); 21 CFR 814.39) or seek NB review in the EU.

Common pitfalls

• Mixing “intended use” with “indications for use” in US files, which slows review.
• Marketing claims that reach beyond the cleared or CE-marked scope.
• Vague user or setting details that weaken usability and risk controls.
• Adding new patients or endpoints without a change assessment and, where needed, a new submission.
• EU claims that outpace the clinical evaluation in MDR Annex XIV.

Quick checks / Tips

• Use one clear sentence for purpose; add short bullets for indications.
• State condition, user, setting, and key performance metrics up front.
• Trace each claim to evidence, risk files, and usability records.
• Before any claim change, run a documented US/EU regulatory impact check.