Your device changed. Your CER didn’t. What happens next?

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

Product changes are part of the medical device lifecycle. Materials improve. Suppliers shift. Manufacturing processes evolve. Software versions update. The device you submitted last year is not the device you manufacture today.

Most manufacturers understand this. They follow change control procedures. They file notifications with the Notified Body. They tick the boxes in the quality system.

But when the Notified Body asks for the updated clinical evaluation report, the response is often silence. Or worse—a statement that the change had no clinical impact, therefore no update is needed.

That logic fails under MDR. And it fails fast.

Why Product Changes Matter Clinically

MDR Article 51 establishes that clinical evaluation is not a one-time activity. It is continuous. It must reflect the current version of the device throughout its lifecycle.

A change to the device means a change to the clinical evaluation scope. Even if the change seems minor from an engineering perspective, it may alter the clinical risk-benefit profile.

The Notified Body does not assess this on faith. They assess it on documented evidence.

This creates a procedural burden that many companies underestimate. Every change must be screened not only for quality and regulatory notification requirements, but also for clinical evaluation implications.

And that screening must be defensible.

What Triggers a Clinical Evaluation Update

Not every change requires a full CER rewrite. But every change requires an evaluation of whether the CER remains valid.

This assessment should be systematic. It should be documented. And it should be reviewed by someone with clinical competence.

Here are the categories of changes that typically require clinical evidence updates:

Design and Material Changes

Any modification to materials in contact with the patient or user must be assessed clinically. A switch from one biocompatible polymer to another may seem equivalent on paper. But the clinical literature may show differences in inflammatory response, degradation, or long-term tissue interaction.

The CER must reflect the material actually used. If the literature review was based on the old material, it is no longer applicable.

Manufacturing Process Changes

A change in sterilization method, surface treatment, or manufacturing location can affect device performance. If the clinical evaluation relied on data from devices manufactured under the old process, the equivalence may no longer hold.

This is especially critical for equivalence-based CERs. The predicate device and the current device must remain substantially equivalent. A process change can break that link.

Indication and Labeling Changes

Expanding the intended use, adding a new patient population, or changing contraindications all require clinical evidence updates. The existing CER may not cover the new claim.

Even a seemingly minor labeling change—such as removing a contraindication—must be justified clinically. The Notified Body will ask: what clinical data supports this expansion?

Software Updates

For devices with embedded or companion software, version changes must be assessed. A software update that alters measurement algorithms, data processing, or user interface may affect clinical performance.

If the clinical data was generated with version 1.0 and the device now ships with version 2.3, the CER must address this. Either by demonstrating equivalence between versions or by providing new clinical data.

The Notified Body Perspective

From the Notified Body’s view, the clinical evaluation is the anchor document. It defines what device is covered by the certificate. It defines what clinical evidence supports that device.

When a manufacturer notifies a change, the Notified Body asks two questions:

First: Does this change affect the clinical risk-benefit profile?

Second: Is the clinical evaluation still valid for the changed device?

If the answer to the first question is yes, the manufacturer must provide updated clinical evidence. If the answer to the second question is no, the certificate may be suspended until the CER is updated.

This is not theoretical. I have seen certificates suspended because the CER referenced an old material specification, an outdated software version, or a narrower intended use than what was being marketed.

The gap between the technical file and the actual device is a gap in compliance. And gaps do not age well.

What a Defensible Change Assessment Looks Like

The change control procedure should include a clinical evaluation impact assessment. This assessment should be documented for every change, no matter how minor.

The assessment should answer these questions clearly:

Does the change affect the device description in the CER?

Does the change affect the intended use, indications, or patient population?

Does the change affect the technical or biological characteristics that were used to establish equivalence?

Does the change introduce new hazards or alter existing ones?

Does the change affect the clinical performance or safety profile?

If the answer to any of these is yes, the CER must be updated. If the answer is no, the rationale must be documented.

The person performing this assessment should have clinical evaluation competence. This is not a checkbox for a project engineer. It requires understanding of clinical evidence, risk-benefit analysis, and regulatory interpretation.

Timing and Notification

MDR Article 51 does not specify an exact timeline for updating the CER after a change. But the principle is clear: the clinical evaluation must remain current.

In practice, this means the CER update should be completed before the changed device is placed on the market under the existing certificate.

If the change requires Notified Body approval, the CER update should be part of the submission package. If the change is notifiable but not subject to prior approval, the CER update should be completed and available for review.

Delaying the CER update until the next periodic update is not acceptable if the change has already been implemented. The certificate covers the device as described in the technical file. If the technical file no longer matches the device, the certificate validity is in question.

What Happens When the CER Is Not Updated

The consequences depend on the severity of the mismatch and the Notified Body’s assessment.

In the best case, the Notified Body issues a non-conformity and requests the update within a defined timeframe. The certificate remains valid during this period.

In more serious cases, the Notified Body may suspend the certificate until the CER is updated and reviewed. This blocks further market placement and can trigger Field Safety Corrective Actions if devices are already distributed.

In the worst cases—especially if the manufacturer continued marketing a significantly changed device without updating the clinical evaluation—the certificate may be withdrawn.

I have also seen situations where a missed CER update was discovered during a post-market surveillance investigation. A complaint pattern emerged. The analysis revealed that the device configuration in the field did not match the clinical evaluation. This raised questions about whether the clinical risk-benefit was ever properly assessed for the current device.

At that point, the regulatory exposure is significant.

Integrating CER Updates Into Change Control

The solution is not to overburden every change with a full CER revision. The solution is to integrate clinical evaluation impact assessment into the existing change control process.

This means training the change control team to recognize clinical implications. It means involving clinical evaluation authors early in the change approval workflow. And it means maintaining a clear link between the CER version and the device configuration baseline.

Some manufacturers maintain a CER change log that tracks which device changes have been assessed and whether they triggered an update. This log is reviewed during internal audits and Notified Body assessments. It provides traceability and demonstrates proactive management.

The key is to treat the CER as a living document, not as a static submission artifact.

What About Equivalence-Based CERs

If your CER relies on equivalence to another device, product changes create additional complexity.

Any change that affects the technical or biological characteristics used to establish equivalence must be reassessed. If the change breaks equivalence, the entire clinical evaluation strategy may need to shift.

This is why equivalence-based CERs require more frequent updates than CERs based on own clinical data. The equivalence demonstration is fragile. It depends on maintaining a specific configuration.

If the predicate device is discontinued or modified, or if your device changes in a way that affects the equivalence argument, the CER must reflect this immediately.

The Cost of Neglect

Manufacturers often view CER updates as administrative overhead. But the cost of neglecting them is far higher.

A suspended certificate stops revenue. A withdrawn certificate triggers recalls. A misaligned CER discovered during a post-market incident investigation creates liability exposure.

The regulatory system does not forgive gaps that persist over time. The longer the CER remains outdated, the harder it is to justify why the device was marketed without proper clinical assessment.

The investment in maintaining the CER is not optional. It is a condition of compliance.

Final Thought

Product changes are inevitable. Clinical evaluation updates should be too.

The question is not whether the change is big enough to matter. The question is whether your clinical evaluation still represents the device you are placing on the market.

If it does not, the gap will be found. And when it is found, the explanation will matter less than the gap itself.

Keep the CER aligned. Keep the documentation clear. And keep the Notified Body informed.

Because the device you describe clinically must be the device you manufacture commercially.

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

Device changes may trigger mandatory CER updates outside the regular schedule. Understand the CER update frequency requirements under MDR.