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.

Why it matters

Drawing the boundary clearly in the submission and SOPs prevents unnecessary submissions and confusion at audit time.

Common pitfalls

•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.

Sources

FDA PCCP Guidance · FDA
IMDRF - Software as a Medical Device · IMDRF
MDCG Software Guidance · MDCG

Open full page

Select term B to compare.

Why compare MedTech terms side by side?

MedTech terminology is full of pairs that look interchangeable but carry very different regulatory, clinical, and commercial consequences. Picking the wrong framework, pathway, or standard early in a project can add months to a submission, invalidate clinical evidence, or trigger an audit finding. Side-by-side comparison is the fastest way to surface those differences before they become costly mistakes.

Each comparison on this page pulls from the same vendor-neutral, sourced definitions used throughout the MedTech Terms glossary. You see the one-line summary, the formal definition, why it matters in practice, common pitfalls, and the primary sources (FDA guidance, EU MDR/IVDR articles, ISO/IEC standards, MDCG documents, IMDRF principles) that back each entry. That makes the comparison defensible in regulatory strategy memos, design reviews, and submission narratives.

Common comparison patterns

Regulatory pathway choice - 510(k) vs PMA, 510(k) vs De Novo, Abbreviated vs Special 510(k).
Quality systems - QSR vs ISO 13485, QMSR vs QSR.
Software classification - SaMD vs SiMD, Locked vs adaptive AI.
EU frameworks - MDR vs IVDR, CE Mark vs UKCA.
Cybersecurity artifacts - SPDX vs CycloneDX SBOM, CVE vs CVSS.
Post-market actions - Recall vs field action, Removal vs correction.

How to use this tool

Pick term A and term B from the dropdowns, or click a preset above. The URL updates with both slugs so you can bookmark or share the exact comparison with a colleague, a notified body reviewer, or your regulatory consultant. Click Open full page on either side for the complete entry, including FAQs, related terms, and the full citation list. If you are not sure which term to start with, browse the Categories view or the A-Z index.

MedTech Terms is a vendor-neutral community resource sponsored by Blue Goat Cyber. Definitions are written for educational use and are not legal or regulatory advice.