How to write a clinical evaluation report (CER) under MEDDEV 2.7/1 Rev. 4 and EU MDR

If you are selling a medical device in the European Union, the clinical evaluation report (CER) is one of the most scrutinized documents in your technical file. Notified Bodies assess it at every certification and renewal cycle. It has to satisfy EU Medical Device Regulation (EU MDR) Annex XIV requirements, and yet the primary guidance document manufacturers use to write it, MEDDEV 2.7/1 Rev. 4, was published under the old Medical Device Directive (MDD).

That creates a real documentation challenge. MEDDEV 2.7/1 Rev. 4 explains how to structure and execute a clinical evaluation. EU MDR determines what clinical evidence must support it, how it connects to post-market obligations, and how often it must be updated. Neither document is sufficient on its own, and treating them as competing rather than complementary frameworks is one of the more common reasons CERs get flagged during Notified Body review.

Below is a practical breakdown of how the two frameworks work together, what the CER must contain, how to structure and write it, and what the update obligations look like across different device risk classes.

Clinical evaluation report (CER): definition and regulatory basis

A clinical evaluation report (CER) is a regulatory document that records the systematic collection, appraisal, and analysis of clinical data about a medical device. Its purpose is to demonstrate that the device performs as intended, that its benefit-risk profile is acceptable, and that any residual risks are outweighed by the clinical benefits.

Under EU MDR 2017/745, every medical device sold in the European Union requires a CER regardless of risk class. Article 61 of EU MDR mandates that manufacturers document the clinical evaluation of their device in a report that supports the conformity assessment. Even devices in the lowest risk class, Class I, require clinical evidence documented in a CER as part of the technical file submitted to the Notified Body.

The CER is a living document. It is not written once at the point of CE marking and then archived. EU MDR requires it to be updated throughout the device lifecycle as new clinical data becomes available through post-market surveillance and post-market clinical follow-up (PMCF).

Where MEDDEV 2.7/1 Rev. 4 still fits under EU MDR

MEDDEV 2.7/1 Rev. 4 carries its origins in its full title: "Clinical Evaluation: A Guide for Manufacturers and Notified Bodies under Directives 93/42/EEC and 90/385/EEC." Those are the MDD and Active Implantable Medical Device Directive (AIMDD), both superseded by EU MDR 2017/745 when MDR entered full application in May 2021.

Despite that history, MEDDEV 2.7/1 Rev. 4 remains one of the most-used documents in EU clinical evaluation practice. The reason is that EU MDR defines the clinical evaluation obligation clearly but provides limited procedural guidance on how to execute it. Article 61 and Annex XIV Part A of EU MDR establish what must happen. MEDDEV 2.7/1 Rev. 4 explains how.

Several Medical Device Coordination Group (MDCG) guidance documents cite MEDDEV 2.7/1 Rev. 4 directly. MDCG 2020-6, which covers sufficient clinical evidence for legacy devices, even includes an appendix that maps which sections of MEDDEV 2.7/1 Rev. 4 remain applicable under MDR. Notified Bodies continue to use the MEDDEV methodology as a benchmark for assessing whether a manufacturer's clinical evaluation is technically sound.

The working read, confirmed through Notified Body practice since 2021, is that MEDDEV 2.7/1 Rev. 4 describes the methodology and MDCG guidance documents set the substantive MDR-specific requirements. Both apply.

BONUS RESOURCE: Click here to download your free Clinical Evaluation Procedure Template.

Key MDCG guidance documents for clinical evaluation

MDCG 2020-5 covers equivalence claims in clinical evaluation. Demonstrating equivalence under EU MDR is significantly more demanding than under the MDD. The device must be similar in technical, biological, and clinical characteristics, and if the equivalent device is manufactured by another company, the manufacturer must have contractual access to that company's technical documentation. This requirement has blocked equivalence pathways for many manufacturers who relied on published literature about a competitor's device under the MDD.

MDCG 2020-6 provides guidance on sufficient clinical evidence for legacy devices and defines well-established technologies. It also includes the appendix that maps MEDDEV 2.7/1 Rev. 4 sections to MDR context, making it an essential reference alongside the MEDDEV guidance itself.

MDCG 2020-7 and MDCG 2020-8 provide the PMCF plan and PMCF evaluation report templates. These documents are directly connected to the CER because the PMCF evaluation report is a required input into the CER update cycle. Under EU MDR, PMCF is a structured requirement that feeds back into the clinical evidence base for the CER, not a supplementary activity.

MDCG 2020-13 provides the clinical evaluation assessment report template that Notified Bodies use when reviewing a manufacturer's CER. Understanding what reviewers are scoring helps manufacturers write CERs that hold up under scrutiny.

MDCG 2019-9 covers the summary of safety and clinical performance (SSCP), a public-facing document required for Class III devices and Class IIb implantables that draws directly from the CER.

The four-stage clinical evaluation process

MEDDEV 2.7/1 Rev. 4 describes clinical evaluation as a four-stage process. The CER documents what happened at each stage and what conclusions were drawn.

Stage 0: Scope. The scope section covers the device being evaluated, its intended purpose and indications for use, the technology it relies on, any clinical claims about its performance or safety, and the general approach being taken to gather clinical evidence, whether through literature, clinical investigation data, or a combination. Getting scope right at this stage matters because the rest of the evaluation flows from it. A scope that is too narrow will miss relevant clinical data, while one that is too broad generates irrelevant data that obscures the actual analysis of the device in question.

Stage 1: Identification of pertinent data. The manufacturer must identify all relevant clinical data. This includes published literature on the device and equivalent devices, data from premarket clinical investigations conducted by the manufacturer, data from investigations of equivalent devices, and post-market surveillance data. The search strategy, including databases, search strings, date ranges, language restrictions, and inclusion and exclusion criteria, must be documented in enough detail that an independent reviewer could replicate it. The literature review process is a substantial part of most CERs and one of the sections Notified Bodies scrutinize most carefully.

Stage 2: Appraisal. Not all clinical data carries equal weight. The appraisal stage evaluates each data source for methodological quality, relevance to the specific device under evaluation, and the weight it should carry in the overall analysis. Published literature that does not adequately characterize the device's clinical context, or data from investigations that used different patient populations or endpoints, may be appraised as low relevance even if it is methodologically sound. The data analysis methodology used during appraisal must itself be documented.

Stage 3: Analysis. Across the appraised data, the manufacturer draws conclusions about clinical performance and safety, the acceptability of the benefit-risk profile, any residual risks or uncertainties, and whether the clinical evidence is sufficient or whether additional data collection through clinical investigation or PMCF is required. For devices where the evidence is insufficient, Stage 3 should identify what data is needed and through what mechanism it will be collected.

How to structure and write the CER

MEDDEV 2.7/1 Rev. 4 is explicit about the transparency standard the CER must meet. The report must provide enough detail for external parties, including Notified Body reviewers, to understand the search criteria adopted, the data available, all assumptions made, and all conclusions reached. That standard has direct implications for how the document is written.

Every substantive claim in the CER must be cross-referenced to the documentation that supports it. The report must clearly distinguish between statements substantiated by clinical data and statements that reflect the evaluator's conclusions or judgment. References to published literature must include enough bibliographic detail to locate the source. References to clinical investigation data must include the investigation code and cross-reference the investigation report location in the technical documentation.

Appendix A9 of MEDDEV 2.7/1 Rev. 4 provides a proposed table of contents, and Annex 10 includes a pre-submission checklist worth working through before any CER goes to a Notified Body. That proposed structure covers:

• Summary
• Scope of the clinical evaluation
• Clinical background, current knowledge, and state of the art
• Device under evaluation (type of evaluation, equivalence if claimed, manufacturer-held data, literature data, summary and appraisal, performance requirements, acceptability of side effects)
• Conclusions
• Date of next evaluation
• Dates and evaluator signatures
• Evaluator qualifications
• References

Under EU MDR, the clinical background and state of the art section carries particular weight. MDR requires manufacturers to demonstrate not just that the device performs safely, but that the benefit-risk profile is acceptable relative to the current standard of medical practice for the condition the device addresses. For Class IIb and Class III devices, this comparison against current clinical alternatives is something Notified Bodies scrutinize closely.

Evaluator qualifications

MEDDEV 2.7/1 Rev. 4 sets requirements for who can conduct a clinical evaluation. Evaluators must have relevant subject matter expertise, which at minimum typically means a medical degree and clinical experience appropriate to the device's indication. The CER must document evaluator qualifications including clinical specialty, years of relevant experience, and conflict of interest declarations.

That requirement has become a more active point of scrutiny under EU MDR. Notified Bodies have flagged CERs where evaluators lacked clinical specialty relevant to the device's indication, where undisclosed commercial relationships existed between evaluators and the manufacturer, or where the evaluation was clearly authored by regulatory affairs staff without appropriate clinical input. For Class IIb and Class III submissions, using external clinical experts with documented independence and a relevant specialty has become standard practice rather than an optional precaution.

CER update frequency under EU MDR

One of the more concrete changes EU MDR introduced is the formalization of the CER update schedule across device risk classes, replacing the MDD's looser expectations with specific obligations tied to risk classification. Article 61 and Annex XIV Part A establish that clinical evaluation is a continuous activity throughout the device lifecycle.

For Class III devices and Class IIb implantable devices, the CER must be reviewed and updated at least annually. For other devices, the manufacturer defines the update schedule, but must justify it based on the device's risk class and the maturity of the underlying technology.

MDCG 2020-6 defines well-established technologies as those with relatively simple and stable designs, no significant history of safety concerns, well-understood clinical performance characteristics, and a long market history. Manufacturers using that characterization to justify a less-frequent update schedule should document the justification explicitly, because Notified Bodies will check it.

The PMCF obligation connects directly to the update cycle. The PMCF plan defines what post-market clinical data the manufacturer is collecting, and the PMCF evaluation report analyzes that data and feeds it back into the CER. For manufacturers who have not yet established a structured PMCF program, the CER update cycle tends to surface that gap quickly, since the CER will lack the post-market clinical evidence EU MDR expects to see as the device accumulates real-world use.

How PMCF feeds the CER

Under EU MDR, PMCF is not a standalone compliance checkbox. It is the mechanism through which manufacturers gather the ongoing clinical evidence required to keep the CER current. The relationship between PMCF and the CER is cyclical: the CER's Stage 3 analysis identifies gaps in clinical evidence, the PMCF plan addresses those gaps through structured data collection, and the resulting PMCF evaluation report provides the new clinical data that updates the CER.

Systematic literature reviews are typically the backbone of the Stage 1 data identification step and must also be repeated at CER update cycles to capture new published evidence. For devices with no premarket clinical investigation data of their own, literature and PMCF data are often the only clinical evidence available. How well that evidence is organized, analyzed, and documented in the PMCF evaluation report directly determines whether the next CER update will hold up under review.

Managing CER documentation as a lifecycle activity

The CER under EU MDR is not a document you write once and archive. EU MDR describes clinical evaluation as a continuous activity, and the CER records that activity over time. The inputs to the CER, primarily literature reviews, clinical investigation reports, and PMCF evaluation reports, update on different schedules. Coordinating those inputs and maintaining traceability between the clinical evidence and the device's general safety and performance requirements (GSPR) checklist is where many manufacturers run into operational difficulty.

Notified Bodies assessing MDR conformity check whether the clinical evidence in the CER actually supports the safety and performance claims made elsewhere in the technical documentation. When that evidence and those claims live in disconnected systems without clear traceability, gaps emerge that require expensive remediation before submission.

Keep reading

If you are working through clinical evaluation and CER documentation under EU MDR, these related guides go deeper on the specific components:

• Clinical evaluation of medical devices: process, requirements, and evidence
• Clinical evaluation process and establishing equivalency (Part 1)
• The clinical evaluation literature review process (Part 2)
• Performing data analysis for clinical evaluation (Part 3)
• Post-market clinical follow-up (PMCF) under EU MDR: the complete guide
• Systematic literature reviews for EU MDR compliance

Greenlight Guru Clinical is built for manufacturers who need to manage clinical data as part of their device lifecycle, not as a separate compliance function. If you are managing PMCF data collection or building out the clinical evidence that feeds your CER, request a demo to see how the platform connects that work to the rest of your technical documentation.