The Clinical Evaluation Plan That Survives Scope Changes

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

Scope changes are not exceptional events. They happen regularly during development, during regulatory preparation, and sometimes even after submission. A marketing request shifts the intended use. A clinical partner suggests an additional indication. Risk management identifies a new hazard that requires a claim adjustment.

Each of these changes has direct consequences for the clinical evaluation. But most clinical evaluation plans are written as if the scope is frozen. They define objectives, literature search strategies, equivalence approaches, and acceptance criteria based on one version of the device description. When that version changes, the plan does not adapt. It breaks.

The result is not just administrative rework. It creates gaps in the evaluation logic, unsupported claims, and deficiencies that surface during Notified Body review or even later during surveillance.

Why Most Plans Cannot Handle Scope Changes

A clinical evaluation plan is supposed to define what clinical data will be collected, analyzed, and used to demonstrate safety and performance. According to MDR Annex XIV Part A and MDCG 2020-13, the plan must be specific to the device, its intended use, and its claims.

The problem is that most plans are written as linear documents. They describe one search strategy, one set of equivalence criteria, one PMCF approach. Everything is designed around a fixed scope. When the scope shifts, the plan does not flex. It simply no longer fits.

I see this frequently when a device that was initially positioned for general use gets repositioned for a specific patient population. The literature search may have been broad. The equivalence device may no longer be relevant. The clinical data that was considered sufficient may now be insufficient because the risk profile has changed.

The team realizes this only when the Notified Body points out that the plan does not match the technical documentation. Or when the CER is drafted and the data does not support the updated claims.

What Changes Actually Affect the Clinical Evaluation

Not every scope change requires a full revision of the clinical evaluation plan. But certain changes have direct regulatory and clinical consequences.

A change in intended use or indication always affects the clinical evaluation. The device may now be used in a different patient population, a different clinical setting, or for a different purpose. This changes the relevant clinical data, the applicable standards, the literature to review, and the risks to address.

A change in claims also has immediate impact. If a performance claim is added, the clinical evaluation must provide data to support that claim. If a safety claim is modified, the risk analysis and clinical data must align with the new claim. The plan must define how that data will be obtained.

Changes in device design or materials can shift the equivalence strategy. A device that was equivalent to a predicate may no longer be equivalent after a design change. The plan must address how the clinical evaluation will handle that gap.

Even changes in contraindications or warnings can affect the clinical evaluation. If a new contraindication is added based on risk analysis, the plan should define how clinical data will confirm or refine that contraindication.

The key question is not whether the change is major or minor. The key question is whether the change affects what needs to be demonstrated clinically. If it does, the plan must address it.

Building Flexibility Into the Plan Without Losing Specificity

A flexible clinical evaluation plan does not mean a vague plan. Vague plans get rejected. Notified Bodies expect specificity. They expect defined search strategies, defined equivalence criteria, defined acceptance thresholds.

Flexibility comes from structure, not from ambiguity.

The plan should define objectives that are directly tied to claims and risks. Each objective should state what needs to be demonstrated and why. If a claim changes, it becomes clear which objective is affected and what needs to be revised.

The literature search strategy should be defined in terms of the clinical questions that need to be answered, not just in terms of keywords. Keywords can be adjusted. Clinical questions provide the logic that connects the search to the evaluation.

Equivalence criteria should be defined as a framework, not as a single binary decision. The plan should specify what technical, biological, and clinical characteristics must be compared and what degree of difference is acceptable. If the device changes, the framework can be applied again without rewriting the entire section.

PMCF objectives should be linked to residual uncertainties and specific claims. If the claims change, the uncertainties may shift, and the plan should make it clear how PMCF objectives will be adjusted accordingly.

This approach does not eliminate the need for plan updates. But it reduces the need for complete rewrites. It also makes it easier to justify updates to the Notified Body because the logic remains consistent.

How to Manage Scope Changes During an Ongoing Evaluation

Scope changes do not always happen before the clinical evaluation starts. Sometimes they happen in the middle of the process. Literature has been reviewed. Equivalence has been analyzed. The CER is being drafted. Then the scope changes.

The first step is to assess the impact. Which sections of the evaluation are affected? Which data is still valid? Which conclusions need to be reconsidered?

If the change affects the intended use or patient population, the literature review must be reassessed. Some studies may no longer be relevant. Other studies may need to be included. The appraisal may need to be updated to reflect the new clinical context.

If the change affects claims, the analysis of clinical data must be revisited. Data that was considered sufficient for one claim may not be sufficient for another. The gap analysis must be updated, and PMCF may need to be expanded.

If the change affects equivalence, the entire equivalence demonstration must be reviewed. A device that was equivalent under one set of criteria may not be equivalent under another. If equivalence can no longer be claimed, the plan must define an alternative path to demonstrate safety and performance.

The second step is to document the impact assessment and the plan update. This is not optional. MDR Article 61(11) and MDCG 2020-13 require that the clinical evaluation plan and CER are updated when new data or information becomes available. A scope change is new information.

The update should clearly state what changed, why it changed, how it affects the clinical evaluation, and what actions are being taken. This documentation will be reviewed by the Notified Body and may be inspected by competent authorities.

Version Control and Traceability

A clinical evaluation plan that survives scope changes is also a plan that is properly versioned and traceable.

Every version of the plan should be dated, numbered, and linked to the corresponding version of the technical documentation. When the scope changes, the plan version should change. The revision history should document what was changed and why.

This is not bureaucracy. It is regulatory hygiene. During an audit or assessment, reviewers will compare the plan to the technical file, to the risk management file, and to the CER. If versions do not align, the evaluation looks unreliable.

Traceability also helps the team. When preparing for a Notified Body meeting or responding to a deficiency, it is essential to know which version of the plan was used for which version of the CER. Without that traceability, it becomes difficult to justify decisions or demonstrate consistency.

Some teams maintain a traceability matrix that links claims, risks, clinical evaluation objectives, and data sources. This matrix is updated whenever the scope changes. It makes it easy to see what is affected and what needs to be revised.

What Notified Bodies Expect

Notified Bodies do not expect that the scope will never change. They expect that changes are managed properly.

They expect that the clinical evaluation plan reflects the current device scope and claims. If the scope has changed, the plan must have been updated accordingly. They will compare the plan to the technical file, to the IFU, and to the CER. Misalignment is a deficiency.

They expect that updates are documented and justified. A plan that has been revised multiple times without explanation raises questions. A plan that clearly documents what changed and why builds confidence.

They expect that the clinical evaluation remains coherent. If the scope has changed but the literature review has not been updated, or if equivalence is still claimed despite significant design changes, the evaluation is incomplete. The plan should demonstrate that all necessary updates have been made.

They also expect that PMCF is adjusted when needed. If the scope change introduces new uncertainties or shifts the risk profile, the PMCF plan should reflect that. A static PMCF plan that does not adapt to scope changes suggests that post-market activities are not being managed proactively.

Practical Steps to Prepare for Scope Changes

The best time to prepare for scope changes is when writing the initial clinical evaluation plan.

Define objectives in terms of claims and risks, not in terms of device features alone. This makes it easier to update objectives when claims change.

Structure the literature search around clinical questions, not just around keywords. This allows the search to be refined without starting from scratch.

Define equivalence as a framework with clear criteria, not as a binary conclusion. This allows equivalence to be reassessed when the device changes.

Link PMCF objectives to specific uncertainties and claims. This makes it clear how PMCF should evolve if the scope changes.

Maintain version control and traceability from the start. Do not wait until the Notified Body asks for it.

Establish a clear process for reviewing and updating the plan when changes occur. Define who reviews the impact, who approves the update, and how the update is documented.

These steps do not prevent scope changes. But they make scope changes manageable. They reduce the risk of gaps, inconsistencies, and deficiencies. They also reduce the time and effort needed to bring the clinical evaluation back into alignment.

Final Considerations

A clinical evaluation plan is not a document that is written once and never touched again. It is a living document that must remain aligned with the device, its claims, and its risks throughout the product lifecycle.

Scope changes are inevitable. The question is whether the plan can adapt without breaking. A plan that survives scope changes is a plan that was designed with structure, clarity, and traceability. It is a plan that defines clear links between what the device does, what needs to be demonstrated, and how it will be demonstrated.

When the scope changes, those links guide the necessary updates. The team knows what to revise. The Notified Body sees that the revision was done properly. The clinical evaluation remains coherent and defensible.

That is the difference between a plan that collapses under the first change and a plan that evolves with the product.

Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.