The clinical evaluation report is not a one-time document produced for CE marking and then filed away. Under MDR Article 61(11), the clinical evaluation and its documentation shall be updated throughout the life cycle of the device with clinical data obtained from the implementation of the manufacturer's post-market clinical follow-up plan under Annex XIV Part B and the post-market surveillance plan under Article 84. For Class III devices and implantable devices, the CER must be updated at least annually with the PMCF data. For lower-risk devices, the cadence is defined in the PMS and PMCF plans and must be proportionate to the risk and novelty of the device. Updates are also triggered by specific events — new safety signals, complaints, literature findings, and vigilance data — not only by the calendar.

By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.

TL;DR

  • MDR Article 61(11) is the legal basis for CER updates. It requires the clinical evaluation and its documentation to be updated throughout the life cycle of the device with data from the PMCF plan under Annex XIV Part B and the PMS plan under Article 84.
  • For Class III and implantable devices, Article 61(11) requires the CER to be updated at least annually. For Class IIa and IIb, the cadence is defined in the PMS and PMCF plans and justified by risk and novelty. For Class I, the update sits inside the PMS report cycle under Article 85.
  • The CER is also updated on triggers, not only on the calendar. New safety signals from vigilance, new literature that changes the state of the art, complaint clusters, PMCF findings that contradict the prior conclusion, and changes to the device or its intended purpose all force an unscheduled update.
  • The update is a documented process, not a one-line note. The updated CER rolls the new clinical data through the four-stage data treatment — scoping, identification, appraisal, analysis — and produces a revised benefit-risk determination and a revised GSPR traceability.
  • The CER update feeds the PSUR under Article 86 for Class IIa, IIb, and III devices, and the PMS report under Article 85 for Class I devices. MDCG 2025-10 (December 2025) is the current operational guidance on how the PMS system produces the data that drives the CER update.

Why the CER is a lifecycle document, not a snapshot

Founders reading MDR for the first time often treat the clinical evaluation report as a hurdle to clear for CE marking. Write it, ship it, get the certificate, move on. That reading produces a file that passes the first Notified Body review and then slowly rots on a shared drive until the next surveillance audit surfaces the problem.

The Regulation does not describe the CER as a hurdle. It describes it as the current, documented picture of the clinical safety and performance of the device. Current is the load-bearing word. The clinical picture of a device changes over time. New literature is published. Users find failure modes the pre-market evidence did not anticipate. Complaints cluster. Vigilance events land. The state of the art moves. Equivalent or similar devices generate new data. A CER frozen at CE marking stops being a true description of the device within months.

Annex XIV Part B of the MDR captures this directly. PMCF is defined as a continuous process that updates the clinical evaluation referred to in Article 61 and Annex XIV Part A. The Annex does not say PMCF reports to the CER once at renewal. It says PMCF updates the clinical evaluation continuously. The CER has to move with it.

Article 61(11) — the update obligation in plain text

Article 61(11) of Regulation (EU) 2017/745 is the specific provision that makes CER updates non-optional. It states that the clinical evaluation and its documentation shall be updated throughout the life cycle of the device concerned with clinical data obtained from the implementation of the manufacturer's PMCF plan referred to in Annex XIV Part B and the post-market surveillance plan referred to in Article 84. For Class III devices and implantable devices, the clinical evaluation report and, if applicable, the summary of safety and clinical performance referred to in Article 32 shall be updated at least annually with the data referred to in the first subparagraph.

Three mechanics fall out of that paragraph.

First, the update obligation exists for every class. There is no Class I exemption from "throughout the life cycle." The difference between classes is the cadence, not the existence of the obligation.

Second, the inputs to the update are specified. PMCF data under Annex XIV Part B and PMS data under Article 84. Those are the two named data sources. Anything the PMCF plan and the PMS plan surface — and those plans together should be capturing everything clinically relevant — is in scope.

Third, the minimum cadence for the highest classes is written into the Regulation. "At least annually" for Class III and implantable devices. Not at renewal. Not when the Notified Body asks. At least annually, as a floor, with more frequent updates if the incoming data demands them.

Article 61(12) sits next to this and defines the CER itself as the document in which the results of the clinical evaluation and the clinical evidence on which it is based are documented, supporting the assessment of conformity of the device. Together, Article 61(11) and 61(12) make the CER a continuously maintained document with a legally mandated update rhythm.

The four triggers that force a CER update

The calendar is one driver of CER updates. The other driver is triggers. A CER update can become necessary at any moment because a specific event has invalidated, or may have invalidated, the prior clinical conclusions. A manufacturer who waits until the scheduled annual update while a trigger event sits unacknowledged has failed the PMS and clinical feedback loop. The four trigger categories that appear again and again in real projects are the following.

PMS signals from Article 83 and Article 84. The PMS system required by Article 83 and the PMS plan required by Article 84 are designed to surface trends, cluster patterns, and outlier events. When the PMS system flags a change — a rising complaint frequency, a new failure mode, a user population behaving differently than predicted — the CER has to be re-examined. If the PMS finding changes the clinical picture, the CER is updated. If the PMS finding is consistent with the CER, the fact of the review is documented.

Complaints and vigilance events. Individual complaints do not automatically trigger a CER update. A pattern of complaints that indicates a previously uncharacterised risk does. Vigilance events reported under Articles 87 to 92 — serious incidents, field safety corrective actions — always trigger a review of the CER's safety conclusions, whether or not the review produces a change.

New literature and state-of-the-art movement. The state-of-the-art section of the CER has a shelf life. New clinical literature on the technology, the clinical indication, or equivalent or similar devices can shift the clinical benchmark against which the device is evaluated. A newly published systematic review that establishes a higher clinical performance threshold in the indication is a trigger. So is a newly reported safety signal in a similar device that forces the manufacturer to reconsider whether a comparable risk applies here.

PMCF findings under Annex XIV Part B. The PMCF evaluation report is the direct clinical input to the CER. Every PMCF evaluation report produces one of three outcomes: the new data confirms the existing CER conclusions (document the confirmation and move on), the new data modifies the conclusions (update the CER), or the new data contradicts the conclusions in a way that affects safety (update immediately, escalate through vigilance if the threshold is met, and consider field action).

Changes to the device itself — a design change, a material change, a manufacturing change, or a change to the intended purpose — are a separate category of trigger that always forces a CER review and usually a CER update. These belong to the change control process under the QMS but are noted here for completeness.

Cadence by class — what "throughout the life cycle" actually looks like

Article 61(11) sets a floor for Class III and implantable devices. The other classes inherit the general "throughout the life cycle" obligation, with the specific cadence defined in the PMS and PMCF plans and justified on the basis of risk and novelty.

Class III and implantable devices. At least annually. The CER, the PMCF evaluation report, the PSUR under Article 86, and the Summary of Safety and Clinical Performance under Article 32 all run on an annual cycle for these classes. In practice, a well-organised manufacturer runs these documents on a single integrated annual clinical review that updates all of them consistently.

Class IIb devices. The PSUR under Article 86 is required for Class IIb implantables at least annually and for other Class IIb devices at least every two years. The CER update cadence is typically aligned with the PSUR cadence so that the PSUR can cite a current CER. A Class IIb non-implantable device with a stable clinical profile might justify a two-year CER update cycle. A novel Class IIb device typically runs on an annual cycle.

Class IIa devices. The PSUR under Article 86 is required at least every two years. The CER update cadence is typically aligned with this, with the justification written into the PMS and PMCF plans. Devices with narrow, well-characterised clinical claims can often justify a two-year cycle. Devices with novel elements or significant residual clinical uncertainty should run on a shorter cycle.

Class I devices. Class I devices do not require a PSUR but do require a PMS report under Article 85. The CER update sits inside the PMS report cycle. For Class I devices with straightforward clinical profiles, the CER is reviewed and updated on the cadence of the PMS report, with triggers handled as they arise.

In every case, the cadence must be written in the PMS plan and the PMCF plan, justified against the risk class and the novelty of the device, and actually followed. A plan that specifies annual updates and produces updates every third year is a PMS finding waiting to be written up at the next audit.

The update process — what a real CER update actually looks like

A CER update is not a single line added to a change log. It is a documented rerun of the clinical evaluation process on the new evidence, producing a revised CER with a new version number, a new date, and a documented rationale for every change. The process has a recognisable structure.

Step 1 — Assemble the new inputs. The PMCF evaluation report for the period. The PMS data for the period. Vigilance events and field safety corrective actions. New literature from the ongoing literature surveillance. New equivalent or similar device data. Any device or intended purpose changes. Any changes to harmonised standards or MDCG guidance that affect the clinical evaluation methodology.

Step 2 — Re-scope if needed. Confirm that the intended purpose on the current label, the current IFU, and the current CER still match. If the intended purpose has moved, the scope of the clinical evaluation moves with it. If the state of the art has moved, the clinical benchmark moves with it. Document both.

Step 3 — Re-identify and re-appraise. Add the new data to the existing data sets. Appraise the new data against the pre-specified appraisal criteria from the clinical evaluation plan. If the CEP itself needs to be updated because the methodology has changed, update the CEP first — reverse-engineered appraisal criteria are the same mistake in an update as in an original CER.

Step 4 — Re-analyse against the GSPRs. Walk back through the GSPR traceability table. For each relevant general safety and performance requirement, confirm whether the supporting clinical evidence has strengthened, weakened, or stayed the same. Update the benefit-risk determination. Update the residual risk discussion and align it with the risk management file under EN ISO 14971:2019+A11:2021.

Step 5 — Update the downstream documents. The updated CER feeds the PMCF plan (the uncertainties the PMCF plan is chasing may have changed), the risk management file (new data may change probability or severity estimates), the PSUR under Article 86, the PMS report under Article 85, and the Summary of Safety and Clinical Performance under Article 32 where applicable.

Step 6 — Version, sign, and file. The updated CER gets a new version number, a new reviewed-by signature from a suitably qualified evaluator, a new date, and a clear change log. The previous version stays in the technical file history. Notified Bodies will look for the version history at surveillance audits.

The process is described here in six steps because that is how it runs in a disciplined project. A CER update that skips any of the six is an update in name only.

Linkage to the PSUR under Article 86

The PSUR is the document in which CER updates become most visible to the Notified Body between full technical file reviews. Article 86 requires the PSUR to summarise the results and conclusions of the analyses of the PMS data gathered as a result of the PMS plan, together with a rationale and description of any preventive and corrective actions taken. The main findings of the PMCF and the volume of sales, estimates of the size and other characteristics of the population using the device, and where practicable the usage frequency of the device, all have to be stated.

In practice the PSUR cannot do its job unless the CER is current. The PSUR's benefit-risk conclusion is a restatement of the CER's benefit-risk conclusion as updated by the PMS and PMCF data for the reporting period. A PSUR that cites a three-year-old CER and then describes two years of new clinical data has a visible gap that a Notified Body reviewer will open.

For Class III and implantable devices, the PSUR runs at least annually and the CER has to run at least annually, which means the two documents are produced in the same review cycle. For Class IIb, the PSUR runs at least annually for implantables and at least every two years otherwise. For Class IIa, the PSUR runs at least every two years. For Class I, there is no PSUR, but the PMS report under Article 85 plays the equivalent role.

MDCG 2025-10 (December 2025) describes the operational context of the PMS system, including how PMS data is structured to feed both the PSUR and the CER update. The guidance is the current authoritative reading of how Articles 83 to 86 operate in practice, and it should be consulted alongside the Regulation text when the PMS and CER update processes are being designed.

The Subtract to Ship angle — run one integrated clinical review, not four parallel ones

The Subtract to Ship framework applied to CER updates produces one operational rule. Do not run the CER update, the PMCF evaluation report, the PSUR, and the SSCP as four separate documents written by four separate processes on four separate timelines. Run them as one integrated clinical review on a single cadence that is aligned with the highest-frequency obligation for the device class.

For a Class III or implantable device, that cadence is annual. For a Class IIb implantable, annual. For a Class IIb non-implantable or Class IIa, the PSUR cadence defined by Article 86. For Class I, the PMS report cadence under Article 85. In each case, one annual or biennial clinical review produces the updated PMCF evaluation report, the updated CER, the PSUR or PMS report, and the updated SSCP where applicable — all at once, with shared evidence, shared appraisal, and a single traceable change log.

The subtraction is the parallel work that disappears. No separate literature search for the CER and the PSUR. No separate benefit-risk determination in the PMCF evaluation report and the CER. No separate GSPR traceability. One appraised evidence base, one analysis, one conclusion, and four documents that express the same conclusion in the formats the Regulation requires. That is cheaper, cleaner, and much harder to produce inconsistencies in.

Reality Check — Where do you stand?

  1. Do you have a written CER update cadence, documented in the PMS plan and the PMCF plan, justified against the risk class and novelty of your device?
  2. If your device is Class III or implantable, can you show at least annual CER updates for every year since CE marking, with version history?
  3. Is there a documented rule for which PMS signals, complaint patterns, and vigilance events trigger an unscheduled CER update?
  4. When your PMCF evaluation report is produced, does it explicitly name whether it confirms, modifies, or contradicts the current CER conclusions, and does a CER update follow when it should?
  5. Does your current PSUR cite the current version of the CER, or does it cite a CER from a previous cycle?
  6. Is the appraisal grid in your updated CER the same grid that was pre-specified in the clinical evaluation plan, or was it re-written to fit the new data?
  7. When the CER is updated, does the risk management file under EN ISO 14971:2019+A11:2021 get updated in the same review cycle?
  8. Can you hand the last three CER versions to a Notified Body reviewer and defend every change with reference to a specific PMCF finding, PMS signal, or new literature source?

Frequently Asked Questions

How often must the clinical evaluation report be updated under MDR? Under Article 61(11), the CER must be updated throughout the life cycle of the device with PMCF data under Annex XIV Part B and PMS data under Article 84. For Class III and implantable devices, the Regulation specifies a minimum cadence of at least annually. For Class IIa and Class IIb, the cadence is defined in the PMS and PMCF plans and is typically aligned with the PSUR cadence under Article 86. For Class I, the CER update runs on the cadence of the PMS report under Article 85. Triggers such as new safety signals, complaint clusters, and significant new literature can force unscheduled updates at any point.

Is the CER update obligation limited to Class III and implantable devices? No. Article 61(11) requires the CER to be updated throughout the life cycle of the device for every class. The annual minimum is specific to Class III and implantable devices. Lower-risk devices still have the continuous update obligation, with the cadence justified in the PMS and PMCF plans.

What triggers an unscheduled CER update? A PMS signal under Article 83 that changes the clinical picture, a pattern of complaints indicating an uncharacterised risk, a vigilance event or field safety corrective action under Articles 87 to 92, new literature that shifts the state of the art or identifies a new safety signal, a PMCF finding that contradicts the current CER conclusions, or a change to the device or its intended purpose. Any of these can require a CER review and, where the clinical picture actually changes, a CER update with a new version, date, and change log.

Does a PMCF evaluation report automatically require a CER update? Every PMCF evaluation report requires a documented review of the CER and a documented decision about whether an update is needed. If the PMCF data confirms the current CER conclusions, the confirmation is documented and the CER version does not change. If the PMCF data modifies or contradicts the conclusions, a CER update is required. The decision itself is a documented output of the review process, not an optional step.

How does the CER update feed into the PSUR? Under Article 86, the PSUR summarises the PMS findings and the main findings of the PMCF for the reporting period, together with the benefit-risk conclusion. The benefit-risk conclusion in the PSUR is the CER's benefit-risk conclusion as updated by the PMS and PMCF data for the period. In practice, the CER update and the PSUR are produced in the same clinical review cycle, so that the PSUR cites a current CER rather than a CER from an earlier cycle.

Do I need to update the clinical evaluation plan when I update the CER? Only if the methodology, scope, or appraisal criteria have changed. The CEP is the pre-specified plan; the CER is the report against the plan. If the incoming data simply extends the evidence base without changing the method, the CEP stays the same and only the CER is updated. If the state of the art or the device has moved in a way that changes the scope, the appraisal criteria, or the analysis method, the CEP is updated first and the new CER is produced against the updated plan. Reverse-engineered changes to the appraisal grid to fit the new data are the same methodological failure in an update as in an original CER.

Sources

  1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, Article 61(11) (lifecycle update of clinical evaluation with PMCF and PMS data; at least annually for Class III and implantable devices), Article 61(12) (CER documents the clinical evaluation), Article 83 (post-market surveillance system), Article 84 (post-market surveillance plan), Article 85 (post-market surveillance report for Class I devices), Article 86 (periodic safety update report for Class IIa, IIb, and III devices), Annex III (technical documentation on post-market surveillance), Annex XIV Part A (clinical evaluation), Annex XIV Part B (post-market clinical follow-up). Official Journal L 117, 5.5.2017.
  2. MDCG 2025-10 — Guidance on post-market surveillance of medical devices and in vitro diagnostic medical devices. Medical Device Coordination Group, December 2025.
  3. EN ISO 14971:2019 + A11:2021 — Medical devices — Application of risk management to medical devices.
  4. EN ISO 14155:2020 + A11:2024 — Clinical investigation of medical devices for human subjects — Good clinical practice.

This post is part of the Clinical Evaluation & Clinical Investigations series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. The CER update cycle is where clinical evaluation stops being a pre-market exercise and becomes a lifecycle discipline — and where the gap between a file that is current and a file that only looks current is widest.