Predetermined Change Control Plan (PCCP) for SaMD: FDA Requirements
Introduction
Software as a Medical Device (SaMD) is continuously evolving. Manufacturers may need to improve software performance, update algorithms, address cybersecurity vulnerabilities, improve interoperability, or make other software modifications after the device has received FDA authorization.
For traditional medical devices, every significant change may require a regulatory assessment to determine whether a new FDA submission is necessary.
For certain planned software modifications, FDA provides a mechanism known as a Predetermined Change Control Plan (PCCP).
As a critical element of your overall premarket SaMD software documentation, a PCCP allows a manufacturer to describe planned future modifications and the methodology used to develop, validate, and implement them during the initial FDA submission.
Contact us for SaMD Approval
What is a PCCP?
A Predetermined Change Control Plan (PCCP) is a regulatory plan that describes:
- The modifications a manufacturer intends to make to the device in the future
- The boundaries of those modifications
- The methodology for developing and validating the modifications
- The assessment that will be performed to determine their impact on safety and effectiveness
In simple terms:
A PCCP allows a manufacturer to tell FDA in advance what certain future changes will be, how those changes will be controlled, and how the manufacturer will demonstrate that the modified device remains safe and effective.
FDA’s predetermined change control plan framework directly aligns with broader FDA guidance on AI-enabled medical devices, applying specifically to AI/ML software functions across 510(k), De Novo, and PMA submission pathways.
Why is PCCP important for SaMD?
Software can change frequently during its lifecycle.
For example, an SaMD manufacturer may want to:
- Improve algorithm performance
- Update an existing AI model
- Improve software compatibility
- Add predefined data sources
- Improve interoperability
- Modify the user interface
- Address certain cybersecurity issues
- Improve performance within an existing intended use
Without an appropriate regulatory framework, manufacturers may need to assess each change individually to determine whether a new marketing submission is required.
A well-defined Predetermined Change Control Plan provides a predefined regulatory framework for certain anticipated changes.
Does Every SaMD Need a PCCP?
No.
A PCCP is not automatically required for every SaMD.
It is particularly useful where the manufacturer can reasonably anticipate future modifications and can define:
- What the modifications will be
- The boundaries of those modifications
- How they will be developed
- How software verification and validation (V&V) protocols will be executed to maintain safety
- How their impact will be assessed
For AI-enabled SaMD, PCCP can be particularly useful because AI/ML models may undergo controlled improvements over the product lifecycle.
PCCP and FDA 510(k)
A PCCP can be submitted as part of an FDA marketing submission.
For example:
Initial SaMD
↓
510(k) Submission
Device + PCCP
↓
FDA Review
↓
510(k) Clearance
↓
Future modifications implemented according to the authorized PCCP
The important point is that the PCCP is not a separate blanket authorization for all future software changes.
The manufacturer must remain within the scope and boundaries of the authorized PCCP.
When structuring your US FDA SaMD submission pathways, incorporating a PCCP during the initial 510(k) or De Novo filing allows for streamlined future updates.
Drafting a PCCP for Your SaMD?
Simplify FDA Clearance and Unlock Seamless Future Software Updates.
PCCP and De Novo
PCCP is also relevant to certain innovative devices pursuing the De Novo pathway.
FDA’s PCCP guidance covers AI-enabled device software functions submitted through:
- 510(k)
- De Novo
- PMA
Therefore, manufacturers developing novel AI-enabled SaMD should consider whether a PCCP would provide value as part of their regulatory strategy.
What Are the Benefits of PCCP?
A properly developed PCCP can help manufacturers:
Support software evolution: It provides a structured approach for implementing certain planned improvements.
Improve regulatory predictability: The manufacturer establishes the modification boundaries and assessment methodology upfront.
Support AI/ML lifecycle management: PCCP can be particularly useful for controlled AI/ML model improvements.
Maintain safety and effectiveness: The manufacturer is required to establish appropriate methods for evaluating the impact of planned modifications.
What Should Manufacturers Remember?
A PCCP should be:
- Specific
- Bounded
- Risk-based
- Evidence-based
- Consistent with the device’s intended use
A manufacturer should not use PCCP as a mechanism to obtain unrestricted authorization for future software development.
Conclusion
PCCP provides an important regulatory framework for managing certain anticipated changes to SaMD and AI-enabled medical devices.
However, preparing a PCCP requires more than listing future software updates. The manufacturer must clearly define the planned modifications, establish appropriate boundaries, and demonstrate how the modifications will be developed, verified, validated, and assessed.
For AI-enabled devices, manufacturers should consider FDA’s current PCCP guidance when determining whether and how to incorporate a PCCP into their marketing submission.
How Operon Strategist Can Help
Navigating FDA requirements for Software as a Medical Device (SaMD) and drafting a compliant Predetermined Change Control Plan (PCCP) requires a deep understanding of software lifecycle processes, risk management, and regulatory strategy.
Operon Strategist provides end-to-end regulatory consulting services to help SaMD and AI/ML medical device manufacturers achieve seamless FDA clearance and maintain lifecycle compliance.
Our Specialized SaMD & PCCP Consulting Services:
PCCP Strategy & Dossier Development: We assist manufacturers in defining specific, bounded, and risk-based modification boundaries, establishing robust verification and validation (V&V) protocols, and drafting FDA-compliant PCCPs aligned with the latest FDA guidance for AI-enabled devices.
SaMD Regulatory Pathway & 510(k) / De Novo Submissions: From classification and predicate identification to complete technical dossier preparation, we streamline your marketing submission across 510(k), De Novo, and PMA pathways.
Software Lifecycle & Cybersecurity Compliance: Guidance on aligning software architectural documentation, verification/validation testing, and cybersecurity controls with IEC 62304 software lifecycle standards and FDA expectations.
QMS & Change Control Integration: We help update and align your Quality Management System (21 CFR Part 820 / FDA QMSR) to ensure your internal change management workflows support authorized PCCP execution without unexpected regulatory friction.
FDA Submission & Review Support: Full support during FDA review cycles, including pre-submission (Q-Submission) meeting preparation and managing responses to FDA queries or deficiency letters.
Ready to Accelerate Your SaMD Approval?
Contact Operon Strategist Today to consult with our FDA regulatory experts and streamline your SaMD market entry.
FAQ's
What is a Predetermined Change Control Plan (PCCP) for SaMD?
A Predetermined Change Control Plan (PCCP) is a documented plan included in an FDA regulatory submission. It describes planned future software modifications, sets specific boundaries for those changes, and details the verification and validation protocols used to ensure the modified software remains safe and effective without requiring a new FDA submission for each update.
Which FDA regulatory pathways support a PCCP?
FDA’s guidance covers PCCPs for device software functions—including AI/ML-enabled devices—submitted through the following pathways:
510(k) Premarket Notification
De Novo Classification Request
PMA (Premarket Approval)
Is a PCCP mandatory for every SaMD submission?
No. A PCCP is optional. It is recommended when a manufacturer foresees iterative algorithm updates, model retraining, or performance refinements during the software lifecycle that can be clearly defined, bounded, and validated upfront.
Can a PCCP be used to change the device’s intended use?
No. A PCCP cannot be used for major modifications that alter the fundamental intended use or indications for use of the device. Any change outside the scope and boundaries authorized in the initial PCCP will require a traditional regulatory assessment and potentially a new marketing submission.
How does a PCCP benefit AI/ML-enabled medical software?
Artificial Intelligence and Machine Learning (AI/ML) models often require continuous or periodic updates using new data sets. An authorized PCCP establishes a pre-approved framework for re-training, tuning, and deploying these model enhancements rapidly while maintaining regulatory compliance.