Updated 21 October 2026 — FDA source dated 20 October 2026.
The FDA published illustrative examples of Predetermined Change Control Plans (PCCPs). An authorized PCCP can allow specified device changes without a new marketing submission for every update, provided changes stay within the authorized plan and follow its conditions. This mechanism already existed; the new development is operational documentation with sepsis and arrhythmia examples.
Why this matters for emergency care. Assessing an algorithm also requires reviewing how future versions are managed. Updates may change thresholds, missed events and alarm burden. Clinical teams need to identify the installed version and the performance evaluated for its intended setting.
Two hypothetical examples. A hospital sepsis alert is adapted to local data, with the model locked before independent validation and monitored after deployment. An inpatient telemetry system detecting atrial fibrillation, ventricular tachycardia and complete heart block may undergo automated retraining and deployment within predefined limits, with deployment blocked when acceptance criteria fail. These hospital scenarios do not validate prehospital use.
Evidence and maturity. This is official regulatory documentation, not a clinical trial or a new authorization of the hypothetical systems. It does not demonstrate improved patient outcomes. The examples are not complete PCCPs and should not be presented as universal requirements for all devices.
Risks and human oversight. Automated updates can alter performance, subgroup bias and alarm fatigue. In the arrhythmia example, the FDA explicitly acknowledges the risk of no human review during updating, validation and deployment. This does not remove clinicians’ responsibility to assess patients and original signals.
Italy and the European Union. The document concerns the US regulatory pathway. It neither grants CE marking nor establishes availability in Italy. Intended use, applicable European conformity requirements and update conditions must be checked for each product and version.
Before adoption. Ask suppliers for permitted changes, thresholds and acceptance criteria, independent and subgroup validation, version notifications and local monitoring. Agree on how problematic updates can be suspended and, where available, rolled back. Review GDPR legal basis, access, retention and training-data reuse with institutional governance teams. Do not enter identifiable patient data into unauthorized consumer tools.
Primary sources. FDA CDRH update of 20 October 2026: PCCP overview and authorized devices; hypothetical sepsis and arrhythmia examples.
Prepared with artificial intelligence assistance and verification of the cited sources. For educational and informational purposes; it does not replace clinical judgment, device instructions or local protocols.