Regulations/FDA QMSR/Applicability
Applicability · FDA QMSR

Applicability for FDA QMSR.

This page turns scope and timing into a decision route. It separates who is in scope, what trigger applies, which date matters, and where teams should avoid premature compliance claims.

Source basis: Quality Management System Regulation amendments to 21 CFR Part 820Use: evidence-readinessBoundary: not legal advice
FDA QMSR TRACE 21 CFR PART 820 SCQMSR FINAL RULE ISO 13485:2016 IFDA-SPECIFIC PRO
/ Applicability logic

Applicability begins with scope, not assumption.

FDA QMSR
Applicability 01

Finished device manufacturers

Commercially distributed medical devices in the US are the core population.

Applicability 02

Specification developers and contractors

Applicability may flow through design, manufacturing, sterilisation, relabeling, repackaging, and quality agreements.

Applicability 03

Suppliers

Suppliers are usually controlled through purchasing and supplier controls rather than direct QMSR identity.

Applicability 04

Non-device systems

Pharma-only QMS and wellness tools need separate regulatory reasoning.

/ Dates and gates

Timing changes what can be responsibly claimed.

status gates
Gates

Track these before publishing a checklist or readiness claim.

2024-02-02 final rule published · 2026-02-02 effective date · post-effective inspection programme transition · procedure and training effectiveness review

04
/ Use cases

Regulated use cases need a decision record.

life sciences lens
Use case 01

21 CFR Part 820 amendment

Use this as a trigger for FDA QMSR applicability review, not as an automatic compliance conclusion. Regulatory text changes create a transition project, not only a policy update.

Use case 02

ISO 13485:2016 alignment

Use this as a trigger for FDA QMSR applicability review, not as an automatic compliance conclusion. Quality-system language and evidence expectations move closer to international QMS structure.

Use case 03

Effective date 2026-02-02

Use this as a trigger for FDA QMSR applicability review, not as an automatic compliance conclusion. Teams need implementation evidence before the rule is fully in effect.

Use case 04

Design and development controls

Use this as a trigger for FDA QMSR applicability review, not as an automatic compliance conclusion. Design evidence must connect to risk, requirements, verification, validation, and change.

Use case 05

Risk management

Use this as a trigger for FDA QMSR applicability review, not as an automatic compliance conclusion. Risk becomes part of the quality-system evidence fabric.

Use case 06

Supplier and purchasing controls

Use this as a trigger for FDA QMSR applicability review, not as an automatic compliance conclusion. External-party quality evidence remains an operational weak point.