● FDA CSAOverviewSource LibraryArticles & ClausesApplicabilityInterpretationEvidence ReadinessAI GovernanceOperational FlowActors & ServicesUpdates & Assets
Regulations/FDA CSA/Applicability
Applicability · FDA CSA

Applicability for FDA CSA.

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: Computer Software Assurance for Production and Quality System SoftwareUse: evidence-readinessBoundary: not legal advice
FDA CSA TRACE FDA CSA FINAL GUIDQMSR TERMINOLOGYPRODUCTION SOFTWQUALITY MANAGEME
/ Applicability logic

Applicability begins with scope, not assumption.

FDA CSA
Applicability 01

Medical device production/QMS software

Core scope is software used as part of device production or quality management systems.

Applicability 02

Not device software functions

Market-authorised device software functions require their own product regulatory route.

Applicability 03

Not generic IT

Enterprise software without production/QMS impact should not be pulled into CSA by label alone.

Applicability 04

Supplier and SaaS tools

Supplier evidence matters when external platforms support regulated production or QMS processes.

/ Dates and gates

Timing changes what can be responsibly claimed.

status gates
Gates

Track these before publishing a checklist or readiness claim.

2025-09 final guidance · 2026-02 QMSR-aligned revision · software intended-use assessment · risk-to-assurance decision · change impact review

05
/ Use cases

Regulated use cases need a decision record.

life sciences lens
Use case 01

Intended use

Use this as a trigger for FDA CSA applicability review, not as an automatic compliance conclusion. Assurance starts with what the software is used for in the quality or production process.

Use case 02

Risk-based assurance

Use this as a trigger for FDA CSA applicability review, not as an automatic compliance conclusion. Higher-risk use needs stronger evidence; lower-risk use can avoid unnecessary burden.

Use case 03

Assurance activity selection

Use this as a trigger for FDA CSA applicability review, not as an automatic compliance conclusion. Testing approach should match risk and use, not follow a fixed ritual.

Use case 04

Objective evidence

Use this as a trigger for FDA CSA applicability review, not as an automatic compliance conclusion. Records should show what was checked, by whom, with what result.

Use case 05

Unscripted testing

Use this as a trigger for FDA CSA applicability review, not as an automatic compliance conclusion. Exploratory and ad hoc testing may be appropriate when justified and documented.

Use case 06

Automation support

Use this as a trigger for FDA CSA applicability review, not as an automatic compliance conclusion. Tools can support assurance but need their own fit-for-use rationale.

/ Source anchors

Current public sources for FDA CSA.

official first

These links are the public source anchors for this workspace. Interpretation, checklists, and future assets should point back here before being reused outside iFeed.

Official FDA guidance

FDA CSA guidance

2026-02 · Current final guidance on computer software assurance for production and quality management system software; it supersedes the September 2025 final guidance.

open
Official FDA PDF

FDA CSA guidance PDF

2026-02 · Guidance history notes February 2026 revisions to align terminology with QMSR amendments to Part 820.

open