Algorithm Change Protocol
Historical FDA AI/ML change-control terminology, now reflected in the PCCP Modification Protocol.
Definition
Algorithm Change Protocol (ACP) is terminology from FDA’s 2019 proposed AI/ML framework, not the component name in current final guidance. The August 18, 2025 final PCCP guidance, originally issued December 4, 2024, describes three components: Description of Modifications, Modification Protocol, and Impact Assessment. The Modification Protocol covers data management, retraining practices, performance evaluation, and update procedures. Only modifications consistent with the FDA-authorized PCCP may be implemented without an otherwise required new marketing submission. No standard 30-page length is specified.What this means in practice
Algorithm Change Protocol (ACP) is terminology from FDA’s 2019 proposed AI/ML framework, not the component name in current final guidance. The August 18, 2025 final PCCP guidance, originally issued December 4, 2024, describes three components: Description of Modifications, Modification Protocol, and Impact Assessment. The Modification Protocol covers data management, retraining practices, performance evaluation, and update procedures. Only modifications consistent with the FDA-authorized PCCP may be implemented without an otherwise required new marketing submission. No standard 30-page length is specified.Examples
- Illustrative: An ACP for an AI-powered diagnostic imaging tool would detail the specific data drift thresholds that trigger model retraining and the statistical methods used to validate new versions against a predefined ground truth dataset.
- Illustrative: For a continuous glucose monitor with an adaptive algorithm, the ACP would describe how patient-specific data will be used to retrain the model, the frequency of such retraining, and the performance metrics required for approval of the updated algorithm.
- Illustrative: A medical device using an AI model to detect anomalies in physiological signals would have an ACP outlining the process for incorporating newly identified anomaly patterns, including data collection, model update procedures, and post-update performance monitoring.
- •Treating the ACP as a high-level outline, FDA expects specific protocols with quantitative criteria.
- •Omitting subgroup analysis methodology, disparate performance changes across patient subgroups are a focus area.
- •Failing to specify rollback procedures, what happens when an update doesn't meet acceptance criteria in production?
Frequently asked questions
Related terms
Grouped by themeEditor's picks
· Hand-selected related conceptsMedical device that uses artificial intelligence or machine learning to perform its intended use.
Methods (SHAP, saliency maps, prototype explanations) that help users understand why a model made a given prediction.
Guiding principles for the development of AI/ML-enabled medical devices.
Distinction between models whose behavior is fixed at release vs. those that continue learning.
More in Software & AI
· Same categoryStructured documentation of a machine learning model's intended use, performance, and limitations.
Ongoing surveillance of input data and model outputs to detect performance degradation post-deployment.
FDA mechanism to pre-authorize specific modifications to AI/ML-enabled devices.
AAMI Technical Information Report providing guidance on applying Agile software development practices within an IEC 62304-compliant medical device software lifecycle.
Where this term appears across MedTech Terms.
Latest in MedTech
Sources
3 sourcesSources support the definition or relevant regulatory context, not necessarily every claim on this page. Each is graded against our source-tier hierarchy so you can see what rests on binding law versus commentary.
Official-source claim check:
ACP is historical 2019 terminology. Current final PCCP guidance uses Modification Protocol, alongside Description of Modifications and Impact Assessment.
Partial review: verified corrections are applied, but this is not a full accuracy certification. The last full review date is unchanged.
Remaining verification limits
- Original merged record reviewed in full. Illustrative examples are hypothetical, not verified case histories. Evidence supports the specific propositions below, not an assertion that every linked page verifies all merged content.
- 1FD&C Act section 515C (21 U.S.C. 360e-4), PCCPsTier 2 UncheckedU.S. Codefda.gov
- 2MDCG Software GuidanceTier 2 VerifiedMDCGhealth.ec.europa.eu
- 3FDA - Software as a Medical Device (SaMD)Tier 2 VerifiedFDAfda.gov
Inline markers like [1] jump to the matching reference above.