Understanding Intended Use and Indications for Use

Instructions and indications for use
MDR · IVDR · FDA — Labeling & Claims

Intended Use vs Indications for Use

Understand (and document) the regulatory difference between Intended Use and Indications for Use. This practical guide includes definitions, checklists, traceability tools, and examples you can lift into your QMS and submissions for medical devices including SaMD.

MDR/IVDR Labeling FDA Labeling Clinical Evidence Fit Claims Control PRRC Oversight

What These Terms Mean (and Why They Matter)

Intended Use is the manufacturer’s formal statement of the device’s purpose, users, use environment, and general medical function—owned by the manufacturer and reflected in labeling/IFU.

Indications for Use are the specific clinical conditions, populations, or settings for which the device has been shown to be safe and effective. They are evidence-based and guide when/how clinicians should use the device.

Why this matters: These statements drive classification, clinical strategy, validation scope, reimbursement positioning, and enforcement risk. Misalignment leads to reviewer questions, labeling rework, or post-market findings.

At a Glance — Key Differences

AspectIntended UseIndications for Use
OwnershipManufacturer definesDefined/cleared with the regulator
ScopeGeneral medical purpose and usersSpecific diseases, conditions, populations, settings
Evidence BasisDesign inputs, risk mgmt, usabilityClinical evidence showing safety/performance
Regulatory ImpactDrives classification & conformity routeDrives labeling claims & approval/clearance
Change ControlQMS design change; may trigger submissionUsually triggers submission/notification

How to Draft an Audit-Ready Intended Use

  1. State the medical purpose (diagnosis, monitoring, treatment, mitigation, prediction, support).
  2. Define intended users (HCP specialty, trained lay users) and use environment (hospital, home).
  3. Limitations & boundaries (adjunctive use; does not replace clinician judgment).
  4. Population (adult/pediatric, disease stage, contraindications if known).
  5. Device mode of action (what it does, not how it’s built).
  6. Consistency check across IFU, risk file, clinical plan, and marketing content.
TEMPLATE — Intended Use: “The [device name] is intended to [general medical purpose] for [target users] in [use environment] for [target population]. It is intended to be used as [primary/adjunctive] support and does [not replace clinician judgment / not provide autonomous diagnosis].”

How to Craft Evidence-Backed Indications for Use

  1. List the clinical conditions or use cases your evidence supports (be precise).
  2. Define population & setting (age ranges, severity, inpatient/outpatient, home use).
  3. Specify triggers/parameters (e.g., symptomatic bradycardia; HbA1c thresholds; imaging modality).
  4. Tie to endpoints measured (diagnostic accuracy, sensitivity/specificity, usability, safety outcomes).
  5. Avoid over-reach—do not exceed your data; add “not intended for” if needed.
TEMPLATE — Indications for Use: “The [device name] is indicated for [specific condition(s)] in [population] within [care setting] to [action/clinical decision supported], based on [type of evidence summarized at high level].”

Traceability — Keep Claims, Evidence, and Labels in Lockstep

ElementWhere It LivesPrimary OwnerAudit-Ready ProofCommon Pitfalls
Intended UseIFU, labeling master, design inputsRA with PRRCSigned labeling master; consistency across docsVague purpose; claims creep in marketing
Indications for UseIFU front matter; submission summaryRA/ClinicalEvidence summary matching exact wordingOver-claim beyond datasets or populations
ClaimsIFU, website, brochures, app store textMarketing with RA reviewClaim register with evidence linksUnsupported superlatives; off-label in ads
EvidenceCER/performance eval; V&V; usabilityClinical/QATraceability matrix to endpointsEndpoints don’t match indications

Examples

Pacemaker (Implantable)

Intended Use: To regulate heart rhythm in patients requiring cardiac pacing, used by qualified cardiologists in hospital settings.

Indications for Use: Symptomatic bradycardia; sinus node dysfunction with or without symptomatic bradycardia; high-grade AV block with or without symptomatic bradycardia.

SaMD — Glucose Data Decision Support

Intended Use: To analyze interstitial glucose and lifestyle inputs and provide decision support to adults with type 2 diabetes for therapy optimization, under healthcare professional supervision.

Indications for Use: Adjunctive use in adults with type 2 diabetes for assessment of glycemic trends and identification of hypoglycemia risk; not intended for standalone diagnosis or pediatric use.

Orthopedic Planning Software

Intended Use: To assist surgeons in preoperative planning of joint replacement by measuring anatomical parameters from radiographic images.

Indications for Use: Quantitative measurement of osteoarthritic knee alignment parameters on AP/Lat radiographs in adults to inform implant sizing and alignment selection.

Operationalize in Your QMS

  • Design Inputs: Capture Intended Use early; align user needs and hazards accordingly.
  • Clinical Plan: Build studies/endpoints that directly support desired Indications.
  • Labeling SOP: RA + PRRC approve wording; maintain a master labeling file.
  • Marketing Review: Route all public claims through RA/PRRC claim review.
  • Change Control: Treat wording changes as design changes; assess submission impact.

RACI — Who Does What

ActivityRACI
Draft Intended UseRAPRRCClinical, ProductQA, Marketing
Draft Indications for UseClinicalRAPRRC, MedicalQA, Product
Evidence MappingClinicalQARAPRRC
Labeling ApprovalRAPRRCQAMarketing
Change Control AssessmentRAQAPRRC, ClinicalProduct

Common Pitfalls (and How to Avoid Them)

  • Blurry language: Use clinical terms, define users/settings, avoid marketing adjectives.
  • Evidence mismatch: If you didn’t study it, don’t claim it; adjust indications or add data.
  • Claims creep: Keep websites, brochures, and app store text aligned with approved wording.
  • Population drift: Pediatric vs adult, comorbidities, and contraindications must be explicit.
  • Change unmanaged: Even minor wording shifts can change risk or submission status—run through change control.

Quick Checklists

Pre-Submission Wording Checks

  • Intended Use and Indications are consistent across IFU, submission, and marketing.
  • Endpoints in studies map directly to Indications wording.
  • Risk file reflects the users, settings, and populations named.
  • Usability and cybersecurity testing align with the environments claimed.
  • PRRC sign-off captured in labeling approval record.

Post-Release Surveillance Alignment

  • Capture off-label usage signals in PMS; feed into risk management and labeling review.
  • Trend complaints by indicated condition/population; reassess claims if patterns emerge.

FAQ

Can Intended Use and Indications be identical?
They should be consistent, but Indications are typically more specific and evidence-anchored. A broader Intended Use with precise Indications is common.

Can we broaden Indications later?
Yes—if supported by new evidence and processed via change control and, where required, regulatory submission.

Who has final say on wording?
RA/PRRC approve labeling. Clinical ensures evidence fit. QA verifies process and records.

Bottom Line

Draft the Intended Use to define purpose and boundaries. Build clinical and V&V plans that prove the Indications for Use. Keep wording synchronized across labeling, submissions, and marketing, with PRRC oversight and structured change control. That’s how you stay compliant and audit-ready while enabling safe, effective adoption.

Need a quick review of your Intended Use / Indications wording for MDR, IVDR, or FDA?
Book Free Consult Regulatory Strategy

Disclaimer: This material is for general informational purposes to support internal documentation. It is not legal advice and does not replace applicable laws, standards, guidance, or regulator/Notified Body decisions.