A predetermined change control plan (PCCP) allows the manufacturer of a software or AI medical device to agree, before CE marking, which future modifications it intends to make, how each of them will be developed and validated, and how their effect on safety and performance will be assessed.
Once the plan has been accepted, changes that remain within it can be implemented without a separate assessment of each one by the regulator or the notified body.
The concept has been part of the United States framework since section 515C was added to the Federal Food, Drug, and Cosmetic Act, and the International Medical Device Regulators Forum published its final principles on the subject in August 2026.
In the European Union the position is less settled. The MDR as currently in force does not mention such plans, the AI Act refers to predetermined changes only for systems that continue to learn, and the Commission’s proposal to revise the MDR would introduce them formally but has not yet been adopted.
For digital health and SaMD startups that retrain models, update clinical logic or release software on a monthly or quarterly cycle, the way these three frameworks meet determines how quickly an improvement can reach patients once the device carries a CE mark.
This article sets out the current legal position, what regulators and notified bodies have indicated so far, and how a startup can prepare a PCCP that is usable under the rules now in force and under those expected from 2027 onward.
Why change control sets the release pace for SaMD
A certificate issued under Regulation (EU) 2017/745 describes a device at a given point in its design. For hardware, that description often holds for years.
Software differs in that a manufacturer may wish to change it many times within a single certificate cycle, whether to improve model performance, add an input source, extend compatibility to a new operating system or correct a defect without clinical consequence.
Each of those changes passes through the manufacturer’s change control process, which decides whether the change is significant and therefore has to be reported to the notified body before release.
The most widely referenced European guidance on significant changes is the Notified Body Operations Group document from 2014, which was written under the Medical Devices Directive rather than the MDR. Notified bodies and competent authorities consequently apply the criteria with some variation, and manufacturers tend to absorb that uncertainty through slower and less frequent releases.
For a device built on machine learning, where retraining on new data is an expected part of the healthcare AI lifecycle rather than an exception, this uncertainty has a direct effect on the clinical value of the product and on the commercial roadmap of the company behind it.
Significant changes under the current MDR
Two provisions of Annex IX govern changes after certification. Section 2.4 requires the manufacturer to inform the notified body of any plan for substantial changes to the quality management system or to the range of devices it covers.
Section 4.10 requires the manufacturer to inform the notified body that assessed the technical documentation of any change to the approved device that may affect its safety and performance or the conditions prescribed for its use. The notified body then assesses the change and confirms whether a supplement to the certificate is needed.
The MDR contains no explicit provision allowing a manufacturer and its notified body to agree in advance on a category of future changes. In principle, therefore, any modification relevant to safety and performance triggers a new assessment, either limited to the change itself or extending to a broader review.
Our overview of SaMD and AIaMD regulatory compliance explains how classification under Rule 11 determines the depth of that review.
Some notified bodies have nevertheless begun to work with predetermined plans within the existing text. Scarlet, a notified body specialised in software and AI as a medical device, has piloted the approach, treating the plan as part of the assessed technical documentation and confirming at the time of each change that the manufacturer followed what was agreed, rather than conducting a full new assessment.
This route depends on the interpretation of the individual notified body, and a plan accepted by one body does not bind another, which is one reason the treatment of changes belongs in the discussion when choosing a notified body for software as a medical device.
The AI Act and substantial modification
Regulation (EU) 2024/1689, the AI Act, treats an AI system that is a medical device, or a safety component of one, as high risk where the device is subject to third party conformity assessment under the MDR or IVDR.
Following the Digital Omnibus on AI, the high risk obligations for AI embedded in regulated products, medical devices among them, apply from 2 August 2028 instead of August 2027.
Article 43(4) of the AI Act requires a new conformity assessment whenever a high risk AI system undergoes a substantial modification. For systems that continue to learn after being placed on the market, it provides that changes to the system and its performance which the provider predetermined at the time of the initial conformity assessment, and which are described in the technical documentation under point 2(f) of Annex IV, do not constitute a substantial modification.
Because the AI Act and the MDR were drafted separately, the open point was how this exemption would sit alongside section 4.10 of Annex IX. MDCG 2025-6, the joint guidance issued in June 2025 by the Medical Device Coordination Group and the Artificial Intelligence Board and available on the European Commission MDCG guidance page, recommends reading section 4.10 so that predetermined changes covered by Article 43(4) are not treated as changes within the meaning of Annex IX.
Legal commentators have welcomed that reading while noting that it is guidance rather than law, that its scope is limited to systems that continue to learn, and that individual notified bodies may still choose to assess such changes.
The exemption is also likely to be applied only to gradual changes that leave the functionality and intended purpose of the device unchanged.
International alignment through IMDRF N90
On 6 August 2026 the International Medical Device Regulators Forum published its final document N90, Essential Principles and Content of Predetermined Change Control Plans.
It describes the principles and content of a plan for medical device software in a form intended to be usable across jurisdictions, and European regulators have indicated that future guidance on predetermined plans is likely to build on it.
In the United States, the FDA already authorises plans within premarket submissions under section 515C, with dedicated guidance for AI enabled device software functions and a broader draft guidance for all devices issued in August 2024.
The Australian TGA has published draft guidance aligned with the IMDRF document, which makes clear that a plan does not remove the need for clinical evidence or for verification and validation of each change.
A startup that writes one plan to the IMDRF structure is therefore in a position to adapt it for the EU, the US and other markets instead of maintaining separate documents.
What the MDR revision proposes for PCCPs
The Commission’s proposal COM(2025) 1023 of 16 December 2025 for a targeted revision of the MDR and IVDR would give predetermined change control plans an explicit legal basis.
Manufacturers would be able to implement predefined changes without awaiting notified body approval for each one, and the proposal distinguishes between changes that need approval, changes that need only notification and changes that need neither.
It also creates a formal basis for structured dialogue between manufacturers and notified bodies before and after an application is lodged, which is the setting in which a plan would normally be agreed. Our analysis of the EU MDR 2026 amendments covers the wider proposal.
The proposal remains in the legislative process. A vote in the European Parliament is expected in the first quarter of 2027, followed by trilogue negotiations, with adoption targeted for the second or third quarter of 2027.
The current MDR applies until then, so a plan prepared today has to work under the existing text and be ready to carry over to the revised one.
The content of a predetermined change control plan
FDA guidance organises a plan around three components, and the IMDRF principles follow a comparable logic. Writing to this structure from the outset keeps the plan reviewable by a notified body under the current MDR and adaptable to the revised regulation and to other markets.
Description of modifications
Each planned change is described precisely enough to be verified, together with the reason for it, the software items affected and the expected effect on performance.
A plan covering retraining on additional data from the same population and the same input modalities is considerably easier to accept than one referring to unspecified performance improvements. Changes to the intended purpose, the target population or the clinical claims fall outside the plan in practically every framework and continue to require assessment.
Modification protocol
The protocol describes how each change will be developed, verified and validated. For a machine learning device this covers data management practices, the criteria for including new training data, the separation of training and test data, the retraining procedure, the performance metrics and acceptance criteria, and the procedure for releasing the update and informing users.
Acceptance criteria are fixed in advance and expressed in measurable terms, since the notified body will later verify each change against them, and they should be consistent with the clinical evaluation on which the original certificate was based.
Impact assessment
The impact assessment considers the benefits and risks of each planned change, individually and in combination, within the risk management process under ISO 14971.
It addresses how cumulative changes are prevented from moving the device beyond the performance and safety profile originally assessed, and how bias and subgroup performance are monitored after each release.
Quality management system and post market surveillance
A plan works only where the quality management system can execute it. Configuration management under IEC 62304, version control for models and datasets, traceability from each release back to the plan, and post market surveillance that feeds real world performance into the next iteration all form part of what the notified body will examine.
A SaMD software architecture that separates the model from the surrounding application makes this traceability considerably easier to maintain, and the same records support the logging and monitoring obligations that the AI Act adds for high risk systems.
A PCCP roadmap for digital health startups
Startups that expect to modify their device regularly can take the following steps now, without waiting for the revised MDR.
- Map the release roadmap for the next three to five years and separate the changes that could be predetermined from those that will always require assessment.
- Raise the plan with candidate notified bodies at the pre application stage and obtain written confirmation of how each body intends to treat predetermined changes under section 4.10 of Annex IX.
- Write the plan to the IMDRF N90 structure and include it in the technical documentation, so that it is assessed together with the device rather than submitted afterwards.
- Align the plan with point 2(f) of Annex IV of the AI Act where the device contains a system that continues to learn, so that one document serves both regulations.
- Build the evidence trail into the development process through fixed acceptance criteria, locked test datasets and release records that refer directly to the plan. Where teams use language models to draft parts of this documentation, the controls described in our article on LLMs in SaMD regulatory documentation apply equally.
- Review the plan once the revised MDR is adopted and once European guidance on predetermined plans is published, since both are expected to refine what notified bodies accept.
Frequently asked questions
What is a PCCP for a medical device?
A predetermined change control plan describes the modifications a manufacturer intends to make to a device after authorisation, the protocol for developing and validating them, and the assessment of their impact. Once accepted, changes that stay within the plan can be released without a separate review of each one.
Is a PCCP recognised under the EU MDR?
The MDR currently in force has no explicit provision for predetermined plans, although some notified bodies already accept them as part of the assessed technical documentation. The Commission proposal COM(2025) 1023 would give them a formal legal basis, with adoption targeted for 2027.
Does retraining an AI model count as a significant change?
Under section 4.10 of Annex IX MDR, any change that may affect safety and performance must be reported to the notified body. Under Article 43(4) of the AI Act, retraining that was predetermined at the initial conformity assessment and documented under point 2(f) of Annex IV is not a substantial modification, and MDCG 2025-6 recommends applying the same reading under the MDR.
When do AI Act obligations apply to AI medical devices?
Following the Digital Omnibus on AI, the high risk obligations for AI embedded in products regulated under Annex I of the AI Act, including medical devices and IVDs, apply from 2 August 2028.
Can one PCCP be used for both the EU and the FDA?
A plan written to the structure of IMDRF N90, published in August 2026, can be adapted for the FDA, EU notified bodies and other regulators such as the TGA, which reduces the effort of maintaining separate documents for each market.
Plan your PCCP with Aura Health
Aura Health supports digital health and SaMD startups in designing change control strategies, drafting predetermined change control plans to the IMDRF structure and preparing them for discussion with notified bodies, alongside technical documentation, clinical evaluation and AI Act readiness.
To review your release roadmap and the changes your device will need after CE marking, write to partnerships@aurahealth.ch.
