Predetermined Maintenance vs PCCP
Distinction between routine maintenance changes (cybersecurity patches, minor fixes) and PCCP-controlled algorithm changes.
Definition
Not every software change to an AI/ML device requires a PCCP - cybersecurity patches, bug fixes, and infrastructure updates often fall under standard software maintenance. PCCPs specifically govern pre-specified algorithm modifications. The key test is whether a change modifies the model's behavior or performance claims. Changes outside an authorized PCCP still follow FDA's guidance on deciding when to submit a 510(k) for a software change. Cybersecurity patches for cleared devices generally do not need a new submission unless they affect safety or effectiveness, in line with FDA's postmarket cybersecurity guidance.What this means in practice
Drawing the boundary clearly in the submission and SOPs prevents unnecessary submissions and confusion at audit time.Examples
- A manufacturer releases a software patch to address a newly discovered cybersecurity vulnerability in their AI-powered diagnostic imaging system, classifying it as predetermined maintenance rather than a PCCP change.
- A company submits a PCCP outlining how its AI-driven diabetes management app will be updated annually to incorporate new clinical guidelines into its glucose prediction algorithm.
- An infrastructure update to a cloud-based AI medical device, such as switching to a new server provider without altering the AI algorithm itself, is managed as predetermined maintenance.
- •Confusing routine software maintenance activities with changes that require a PCCP can lead to unnecessary regulatory submissions and delays.
- •Failing to clearly define the scope of a PCCP in relation to general software maintenance can result in regulatory non-compliance during audits.
- •Assuming all AI/ML model retraining constitutes a PCCP-relevant change without distinguishing between performance-enhancing updates and core algorithm modifications is a common misstep.
- •Not adequately documenting the rationale for classifying a software change as maintenance versus a PCCP-governed modification can create audit findings.
- •Applying a PCCP to non-AI/ML software components or changes that do not alter the pre-specified algorithm is an inefficient regulatory strategy.
Frequently asked questions
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsMore in Software & AI
· Same categoryAAMI Technical Information Report providing guidance on applying Agile software development practices within an IEC 62304-compliant medical device software lifecycle.
Resilience of an ML model to inputs deliberately crafted to cause misclassification.
Medical device that uses artificial intelligence or machine learning to perform its intended use.
The detailed procedural section of a PCCP that specifies how planned modifications to an AI/ML model will be developed, validated, and implemented.
Where this term appears across MedTech Terms.
Latest in MedTech
Sources
3 sourcesEvery citation below opens the original document. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.
- 1FDA PCCP GuidanceTier 2 VerifiedFDAfda.gov
- 2IMDRF - Software as a Medical DeviceTier 2 VerifiedIMDRFimdrf.org
- 3MDCG Software GuidanceTier 2 VerifiedMDCGhealth.ec.europa.eu
Inline markers like [1] jump to the matching reference above.