Send us an email:
info@mdrc-services.com

Or use the contact form below

 

How often should Clinical Evaluation Report (CER) be updated?

As per the MDR, clinical evaluations must be duly updated to ensure they reflect the latest data and maintain compliance. However, the MDR does not specify a fixed frequency for these updates. A common question arises: how often should a clinical evaluation be updated?

Should I take a conservative approach updating the CER?

The primary guidance for clinical evaluation has long been MEDDEV 2.7/1, which is supposed to provide insights into best practices. How does it address the frequency of updates? Let’s explore this guidance to understand its recommendations and how they can help determine when clinical evaluations should be reviewed and revised.

First and foremost, MEDDEV 2.7/1 states that manufacturers must define and justify the frequency of clinical evaluation updates. Updates are required when new information from Post-Market Surveillance (PMS) warrants it or when the product has been modified.

In all other cases, MEDDEV 2.7/1 recommends the following update intervals:

  • At least annually for devices carrying significant risks or those not yet well established.
  • Every 2 to 5 years for devices with no significant risks and that are well established, provided a justification is documented.

Or should I look into logic of the MDR and take a more innovative approach?

Despite the above, MEDDEV 2.7/1 was introduced under the MDD framework, which did not mandate the robust and methodical Post-Market Clinical Follow-up (PMCF) processes required by the MDR. The purpose of PMCF is to continuously update clinical data without altering the existing Clinical Evaluation Report. Essentially, it builds upon the existing CER by incorporating new clinical information collected during the reporting period. Therefore, regular updates to the Clinical Evaluation Plan and CER are often unnecessary, as the PMCF plan and periodic PMCF reports serve to fulfill this role.

Here is what MDR says about PMCF: "PMCF shall be understood to be a continuous process that updates the clinical evaluation [...] When conducting PMCF, the manufacturer shall proactively collect and evaluate clinical data from the use in or on humans of a device which bears the CE marking [...] with the aim of confirming the safety and performance throughout the expected lifetime of the device, of ensuring the continued acceptability of identified risks and of detecting emerging risks on the basis of factual evidence."

So it seems updating CER is redundant

In other words, PMCF takes over the role of updating the CER, making regular updates to the CER itself unnecessary. PMCF ensures that new clinical data is continuously collected and documented, effectively performing the function of keeping the evaluation current.

Hence, the modern approach under MDR emphasizes maintaining a robust PMCF system to continuously gather and analyze clinical data. Updates to the CER are typically only required if there are significant changes to the device or if Post-Market Surveillance data reveals information that warrants a formal update.

But there is always a but...

Although this no-updates-to-CER approach aligns with MDR and follows a logical, modern framework, it may be too progressive for some Notified Bodies and Competent Authorities, which might adhere to more traditional practices. To play it safe, consider discussing this approach with them beforehand. Additionally, you could include in your Quality Management System a commitment to update the CER at least once every five years, as recommended in MEDDEV 2.7/1, which remains broadly recognized as valid under the MDR framework.

We are here to assist you with conducting clinical or performance evaluations.

Learn more >>

What you need to have to succeed in certification and sell your products in the EU:

PRRC

Learn more >>

Technical
file
Learn more >>

Post-marketing
surveillance
Learn more >>

Some useful resources for you

Clinical evaluation plan checklist

Learn more >>

Clinical evaluation report checklist
Learn more >>

PMCF

Learn more >>

How often should Clinical Evaluation Report (CER) be updated?

As per the MDR, clinical evaluations must be duly updated to ensure they reflect the latest data and maintain compliance. However, the MDR does not specify a fixed frequency for these updates. A common question arises: how often should a clinical evaluation be updated?

Should I take a conservative approach updating the CER?

The primary guidance for clinical evaluation has long been MEDDEV 2.7/1, which is supposed to provide insights into best practices. How does it address the frequency of updates? Let’s explore this guidance to understand its recommendations and how they can help determine when clinical evaluations should be reviewed and revised.

First and foremost, MEDDEV 2.7/1 states that manufacturers must define and justify the frequency of clinical evaluation updates. Updates are required when new information from Post-Market Surveillance (PMS) warrants it or when the product has been modified.

In all other cases, MEDDEV 2.7/1 recommends the following update intervals:

  • At least annually for devices carrying significant risks or those not yet well established.
  • Every 2 to 5 years for devices with no significant risks and that are well established, provided a justification is documented.

Or should I look into logic of the MDR and take a more innovative approach?

Despite the above, MEDDEV 2.7/1 was introduced under the MDD framework, which did not mandate the robust and methodical Post-Market Clinical Follow-up (PMCF) processes required by the MDR. The purpose of PMCF is to continuously update clinical data without altering the existing Clinical Evaluation Report. Essentially, it builds upon the existing CER by incorporating new clinical information collected during the reporting period. Therefore, regular updates to the Clinical Evaluation Plan and CER are often unnecessary, as the PMCF plan and periodic PMCF reports serve to fulfill this role.

Here is what MDR says about PMCF: "PMCF shall be understood to be a continuous process that updates the clinical evaluation [...] When conducting PMCF, the manufacturer shall proactively collect and evaluate clinical data from the use in or on humans of a device which bears the CE marking [...] with the aim of confirming the safety and performance throughout the expected lifetime of the device, of ensuring the continued acceptability of identified risks and of detecting emerging risks on the basis of factual evidence."

So it seems updating CER is redundant

In other words, PMCF takes over the role of updating the CER, making regular updates to the CER itself unnecessary. PMCF ensures that new clinical data is continuously collected and documented, effectively performing the function of keeping the evaluation current.

Hence, the modern approach under MDR emphasizes maintaining a robust PMCF system to continuously gather and analyze clinical data. Updates to the CER are typically only required if there are significant changes to the device or if Post-Market Surveillance data reveals information that warrants a formal update.

But there is always a but...

Although this no-updates-to-CER approach aligns with MDR and follows a logical, modern framework, it may be too progressive for some Notified Bodies and Competent Authorities, which might adhere to more traditional practices. To play it safe, consider discussing this approach with them beforehand. Additionally, you could include in your Quality Management System a commitment to update the CER at least once every five years, as recommended in MEDDEV 2.7/1, which remains broadly recognized as valid under the MDR framework.

Further reading

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI) - what is it, where to obtain it, and what to do with it

EUDAMED registration - a brief guide

Contract with the Authorised Representative in the European Union (Authorised Representative Mandate)

GSPR – General Safety and Performance Requirements for medical devices in the European Union

How to obtain CE marking for medical software under the EU MDR or IVDR?

Technical documentation for Medical Device Software in the EU

IEC 62304 - the pivotal standard for software medical devices

Medical Device Regulation (MDR) - basics

ISO and IEC standards for medical device software

Clinical Evaluation, PMCF, and PMS in Medical Device Lifecycle

Notified Bodies and their role in certification of medical devices

What is NANDO and why medical device companies should know about it?

Labeling and UDI requirements for medical devices in the EU

Understanding the roles of Authorised Representatives and Importers under MDR/IVDR

MDR implementation - challenges and solutions

Post-market surveillance under MDR and IVDR - requirements and best practices

Notified Body audit - a manufacturer's guide

Risk management plan - guide for medical device companies

Should my medical device comply with GDPR?

EC-certificate for a medical device - Q&A

How long does it take to CE-mark a medical device?

What is a PRRC?

Essential requirements for importers and distributors under MDR and IVDR

Language requirements for IFUs and labels under the MDR and IVDR

Legal Manufacturer and Original Equipment Manufacturer in medical devices

How to structure a PRRC contract for effective compliance

How to Create a Declaration of Conformity According to MDR or IVDR

All articles >>

Get in touch

We're ready to help you. Contact us whether you have a question about our solutions or need help with regulatory issues

Our EU office

MedDev Compliance Ltd
Souliou 1, Strovolos, 2018 Nicosia, Cyprus
Phone: +357 22253765
Email: info@mdrc-services.com
 

©2025 MDRC - Medical Devices Regulatory Compliance

Useful information

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

How to obtain CE marking for medical software under the EU MDR or IVDR?

Technical documentation for Medical Device Software in the EU

Read more >>


Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.

Send us an email:
info@mdrc-services.com

Or use the contact form below

 

Solutions

EU Authorised Representative (EC REP)

EU PRRC

Technical documentation

Risk management

Clinical evaluation

Notified Bodies

Quality management system

Post-market surveillance

Resources

Medical Device Regulation (MDR) - basics

CE-marking process for medical devices

CE-marking process for in vitro diagnostic medical devices

PRRC under MDR or IVDR

Checklists

MDR technical documentation checklist

IVDR technical documentation checklist

Technical documentation checklist for medical device software (MDSW)

MDR-compliant quality system documentation checklist

Clinical Evaluation Plan checklist

Clinical Evaluation Report checklist

All checklists >>

Articles

CE-Certificate vs. EC-Certificate

Basic UDI-DI (bUDI)

EUDAMED registration - a brief guide

Authorised Representative Mandate

GSPR – General Safety and Performance Requirements

More articles >>

Devices

General medical devices and equipment

In vitro diagnostics (IVD)

Medical software

Cookie Policy

We only use essential cookies that enable core functionality and proper operation of the website. These cookies do not store any personally identifiable data. By continuing to use this website, you consent to the use of the essential cookies. You may disable these cookies by changing your browser settings, but this may affect how the website functions.
We do not use our own or third-party analytical, preferences, statistics, marketing, functional, advertisement, performance or any other non-essential cookies.