Clinical Evaluation Report Template: EU MDR CER Structure and Traceability
Use a section-by-section EU MDR CER template covering clinical evaluation plans, literature search, appraisal tables, equivalence, benefit-risk, PMCF links, and evidence traceability.
Why a Structured CER Template Matters
Under EU MDR Article 61 and Annex XIV, every medical device — every risk class, no exceptions — must have a Clinical Evaluation Report (CER) as part of its technical documentation. The CER is not a literature review, not a summary, and not a formality. It is a systematically structured document that evaluates all available clinical evidence to demonstrate that the device achieves its intended clinical benefit, that risks are acceptable relative to benefits, and that the evidence is sufficient for CE marking.
Notified Bodies consistently identify CER deficiencies as one of the top causes of nonconformities. The 2024 MedTech Europe MDR/IVDR Survey reported that clinical documentation and technical documentation assessment remain the most frequent sources of review findings, and multiple Notified Bodies cite incomplete clinical evidence and weak CER structure as recurring issues. The gap between a CER that passes review and one that triggers a multi-page deficiency letter is often a matter of structure and traceability — not necessarily the underlying data.
This article provides a complete CER template with section-by-section guidance, example tables, and an evidence traceability matrix. It is a companion to our Clinical Evaluation Report Complete Guide — use that article for methodology and process guidance, and this template to build your actual document.
Regulatory Basis and Key References
Before using this template, understand the governing framework:
| Reference | Content | Role |
|---|---|---|
| EU MDR Article 61 | Legal requirement for clinical evaluation | Primary legal basis |
| EU MDR Annex XIV, Part A | Clinical evaluation process and minimum requirements | Process requirements |
| EU MDR Annex XIV, Part B | Clinical investigation requirements | When clinical investigation is needed |
| MEDDEV 2.7/1 Rev. 4 | Clinical evaluation methodology guidance (still referenced by NBs) | Methodology |
| MDCG 2020-13 | Clinical evaluation assessment report template for NBs | Shows what NBs look for |
| MDCG 2020-5 | Clinical evidence — equivalence | Equivalence justification |
| MDCG 2020-6 | Clinical evidence requirements for legacy devices | Transition devices |
CER Document Template: Section-by-Section
Document Header (Every Page)
Document Title: Clinical Evaluation Report
Document No.: CER-[Product Code]-[Version]
Device Name: [Trade Name]
Revision: [X.X]
Classification: [Class I/IIa/IIb/III]
Effective Date: [YYYY-MM-DD]
Next Review Date: [YYYY-MM-DD] (see update schedule)
Owner: [Name, Title]
Approved By: [Name, Title]Section 1: Scope and Clinical Evaluation Plan
This section defines what the CER covers and how the evaluation will be conducted.
| Sub-section | Content Required | Guidance |
|---|---|---|
| 1.1 Device under evaluation | Trade name, model/version, classification, basic UDI-DI | Must match the device description in the technical file |
| 1.2 Intended purpose | Exact wording from IFU, including indication, target population, and conditions of use | Copy verbatim from labeling |
| 1.3 Clinical evaluation scope | What clinical claims are being evaluated, which GSPR are addressed by clinical evidence | Link to GSPR checklist |
| 1.4 Clinical evaluation plan reference | Reference to the standalone clinical evaluation plan document | The plan may be a separate document or embedded here |
| 1.5 Methodology | Literature search, clinical investigation data, PMCF data, equivalence route, or combination | Specify per Annex XIV Part A |
| 1.6 Clinical evaluator qualifications | Name, qualifications, relevant experience, declaration of independence | Required per MEDDEV 2.7/1 Rev. 4 Section 5 |
| 1.7 Update schedule | Frequency of updates based on risk class: Class I/IIa: annually or per PMS; Class IIb: annual; Class III: annual minimum | Required per Article 61(11) |
Example: Clinical Evaluator Qualification Table
| Evaluator | Qualification | Relevant Experience | Independence |
|---|---|---|---|
| Dr. S. Patel, MD PhD | Board-certified orthopedic surgeon; PhD in biomedical engineering | 15 years clinical practice; 20+ peer-reviewed publications on spinal implants; previous NB assessor | Independent contractor; no financial interest in [Company] |
Section 2: Device Description and Context
| Sub-section | Content Required |
|---|---|
| 2.1 Device description | Physical characteristics, materials, principles of operation, variants/accessories, device generation |
| 2.2 Intended clinical benefit | Specific, measurable clinical outcomes claimed (e.g., "fusion rate ≥90% at 12 months") |
| 2.3 Stage of development | New device, modified device, line extension, legacy device under MDR transition |
| 2.4 Regulatory history | Previous approvals (CE, FDA, other); previous clinical investigations |
| 2.5 State of the art | Current treatment alternatives, standard of care, comparator devices |
| 2.6 Benchmark/comparator | Device(s) used as clinical benchmark for equivalence or comparison |
Section 3: Clinical Data Sources
3.1 Data Source Identification Table
| Data Category | Source Type | Description | Applicability |
|---|---|---|---|
| Manufacturer's own clinical data | Clinical investigation(s) | [Study ID]: prospective, multi-center, n=[X] | Directly applicable |
| Manufacturer's own PMCF data | Post-market surveillance | [PMS report ID]: registry data, n=[X] patient-years | Directly applicable |
| Literature — own device | Systematic literature review | [Search protocol ID], databases searched, date range | Directly applicable |
| Literature — equivalent device | Systematic literature review | [Search protocol ID], equivalence justified per Section 4 | Applicable if equivalence demonstrated |
| Other clinical experience | Registries, published case series | [Registry name], n=[X] | Supportive |
| Published safety data | Vigilance databases, MAUDE, BfArM | [Query results ID] | Safety signals |
3.2 Literature Search Protocol Summary
| Parameter | Detail |
|---|---|
| Databases searched | PubMed/MEDLINE, Cochrane, Embase, [others] |
| Search date range | [Start date] to [End date] |
| Search terms | [List key terms and Boolean logic] |
| Inclusion criteria | [Population, intervention, comparator, outcomes, study design] |
| Exclusion criteria | [Specific exclusion criteria] |
| Number of hits (initial) | [X] |
| Number after title/abstract screening | [X] |
| Number after full-text review | [X] |
| Number included in analysis | [X] |
3.3 PRISMA Flow Diagram Reference
Include a PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flow diagram showing the literature search screening process. This is increasingly expected by Notified Bodies per 2026 guidance.
Section 4: Equivalence Justification (If Applicable)
If clinical data from an equivalent device is used, the manufacturer must demonstrate equivalence per MDCG 2020-5 and Annex XIV Section 3. Three dimensions must be assessed:
Equivalence Assessment Table
| Aspect | Characteristic | Proposed Equivalent Device | Your Device | Equivalent? | Justification |
|---|---|---|---|---|---|
| Technical | Intended purpose | [Description] | [Description] | Yes/No | [Explanation] |
| Technical | Principle of operation | [Description] | [Description] | Yes/No | [Explanation] |
| Technical | Design | [Description] | [Description] | Yes/No | [Explanation] |
| Technical | Materials (contact) | [Description] | [Description] | Yes/No | [Explanation] |
| Technical | Manufacturing processes | [Description] | [Description] | Yes/No | [Explanation] |
| Technical | Surface treatment/coating | [Description] | [Description] | Yes/No | [Explanation] |
| Technical | Software algorithm | [Description] | [Description] | Yes/No | [Explanation] |
| Biological | Tissue contact type | [Description] | [Description] | Yes/No | [Explanation] |
| Biological | Duration of contact | [Description] | [Description] | Yes/No | [Explanation] |
| Biological | Biocompatibility profile | [Description] | [Description] | Yes/No | [Explanation] |
| Biological | Substance release | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | Clinical condition | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | Severity and stage of disease | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | Site of application | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | Target population | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | User profile | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | Clinical performance outcomes | [Description] | [Description] | Yes/No | [Explanation] |
| Clinical | Critical performance assessment | [Description] | [Description] | Yes/No | [Explanation] |
Critical requirement: The manufacturer must have sufficient access to the technical documentation of the equivalent device to justify the technical and biological characteristics. If access is limited, equivalence cannot be claimed — a clinical investigation may be required instead.
Section 5: Clinical Data Appraisal
5.1 Data Appraisal Table
For each included clinical data source, assess its quality and relevance:
| Study/Data Source | Study Design | Sample Size | Follow-up | Population Relevance | Methodological Quality | Data Weighting |
|---|---|---|---|---|---|---|
| [Study 1: Author, Year] | RCT / prospective / retrospective | n= | [Duration] | High/Medium/Low | High/Medium/Low | High/Medium/Low |
| [Study 2] | ... | ... | ... | ... | ... | ... |
| [PMCF Registry] | Registry | n= | [Duration] | High | Medium | Medium |
| [Literature — equivalent] | Systematic review | n= | [Duration] | Medium | High | Medium |
5.2 Quality Assessment Criteria
| Quality Level | Criteria |
|---|---|
| High | Well-designed RCT or large prospective study; adequate sample size; appropriate controls; long-term follow-up; relevant endpoints |
| Medium | Well-designed non-randomized study; prospective cohort; registry with good data quality; adequate follow-up |
| Low | Retrospective study; case series; small sample size; short follow-up; potential confounding |
Section 6: Clinical Data Analysis
6.1 Performance Outcomes Table
| Clinical Endpoint | Target (from IFU claims) | Observed Result | Confidence Interval | Source(s) | Meets Claim? |
|---|---|---|---|---|---|
| [Primary endpoint 1] | e.g., ≥90% fusion rate | [X]% | [CI] | [Study refs] | Yes/No |
| [Primary endpoint 2] | e.g., ≤5% complication rate | [X]% | [CI] | [Study refs] | Yes/No |
| [Secondary endpoint 1] | e.g., VAS pain reduction ≥50% | [X] points | [CI] | [Study refs] | Yes/No |
| [Safety endpoint 1] | e.g., ≤2% serious adverse events | [X]% | [CI] | [Study refs] | Yes/No |
6.2 Safety Data Summary Table
| Adverse Event Category | Frequency (Own Data) | Frequency (Literature) | Severity | Related to Device? | Adequately Controlled? |
|---|---|---|---|---|---|
| [AE Category 1] | [X]% (n/N) | [X]% (range) | [Mild/Moderate/Severe] | Yes/No/Unlikely | Yes/No |
| [AE Category 2] | [X]% (n/N) | [X]% (range) | [Mild/Moderate/Severe] | Yes/No/Unlikely | Yes/No |
Section 7: Benefit-Risk Analysis
7.1 Benefit-Risk Summary Table
| Aspect | Assessment |
|---|---|
| Identified benefits | [List all clinical benefits with magnitude] |
| Identified risks | [List all risks with frequency and severity] |
| Risk mitigation measures | [Design features, IFU warnings, training requirements] |
| Residual risks | [Risks remaining after mitigation] |
| Benefit-risk conclusion | [Statement: benefits outweigh risks under conditions of use] |
7.2 Benefit-Risk Assessment per ISO 14971 Alignment
Link the clinical benefit-risk assessment to the risk management file:
| Risk (from RM File) | Clinical Evidence Addressing This Risk | Risk Level After Clinical Evidence | Acceptable? |
|---|---|---|---|
| [Risk 1 from RM file] | [CER Section reference + evidence] | [Low/Medium/High] | Yes/No |
| [Risk 2 from RM file] | [CER Section reference + evidence] | [Low/Medium/High] | Yes/No |
Section 8: GSPR Compliance Through Clinical Evidence
Map clinical evidence to the specific GSPR that it supports:
| GSPR No. | GSPR Requirement | Clinical Evidence Provided | CER Section Reference | GSPR Compliant? |
|---|---|---|---|---|
| GSPR 1.1 | Achieves intended performance | [Evidence summary] | Section 6.1 | Yes |
| GSPR 1.8 | Benefits outweigh side effects | [Benefit-risk analysis] | Section 7 | Yes |
| GSPR 1.9 | State of the art considered | [SOTA comparison] | Section 2.5 | Yes |
| [Additional GSPR] | [Requirement] | [Evidence] | [Section] | [Status] |
Section 9: Data Gaps and PMCF Linkage
This section is critical. Every identified gap in the clinical evidence must be linked to a specific PMCF activity.
9.1 Clinical Data Gap Table
| Gap ID | Data Gap Description | Affected GSPR/Claim | PMCF Activity to Address Gap | PMCF Plan Reference | Expected Timeline |
|---|---|---|---|---|---|
| GAP-001 | [e.g., Limited long-term data (>5 years) for new coating] | GSPR 1.6 | PMCF registry study, 10-year follow-up | PMCF Plan Section 4.2 | 2026–2031 |
| GAP-002 | [e.g., No clinical data in pediatric subpopulation] | GSPR 1.9 | PMCF survey of off-label pediatric use | PMCF Plan Section 4.3 | 2026 Q3 |
| GAP-003 | [e.g., Equivalence not fully established for software algorithm] | GSPR 14.7 | PMCF clinical performance study | PMCF Plan Section 4.4 | 2026–2027 |
9.2 PMCF-CER Cross-Reference
| PMCF Activity | CER Gap Addressed | Current PMCF Status | Next PMCF Data Expected | CER Update Triggered? |
|---|---|---|---|---|
| [Activity 1] | GAP-001 | [Ongoing/Planned/Complete] | [Date] | Yes/No |
| [Activity 2] | GAP-002 | [Ongoing/Planned/Complete] | [Date] | Yes/No |
Section 10: Conclusions
10.1 Conclusion Statements
| Statement | CER Section Reference |
|---|---|
| The clinical evidence is sufficient to demonstrate conformity with relevant GSPR | Section 8 |
| The device achieves its intended clinical benefits as claimed | Section 6.1 |
| The identified risks are acceptable in relation to the benefits | Section 7 |
| The state of the art has been appropriately considered | Section 2.5 |
| Data gaps are identified and addressed by PMCF activities | Section 9 |
| The clinical evaluation will be updated per the defined schedule | Section 1.7 |
10.2 Conditions for Conformity
List any conditions under which the conclusions hold (e.g., specific patient populations, use environments, training requirements, or follow-up schedules).
Section 11: Dates, Signatures, and Revision History
Revision History Table
| Version | Date | Author | Description of Change |
|---|---|---|---|
| 1.0 | [Date] | [Author] | Initial CER |
| 1.1 | [Date] | [Author] | Updated literature search; added PMCF data from [study] |
| 1.2 | [Date] | [Author] | Addressed NB deficiency [ref]; updated equivalence assessment |
Approval Signatures
| Role | Name | Signature | Date |
|---|---|---|---|
| Author (Clinical Evaluator) | [Name] | [Signature] | [Date] |
| Reviewer (Regulatory Affairs) | [Name] | [Signature] | [Date] |
| Approver (Head of RA/Clinical) | [Name] | [Signature] | [Date] |
Evidence Traceability Matrix
This master traceability matrix links every clinical claim to its supporting evidence, the CER section where it is analyzed, and the GSPR it supports:
| Claim ID | Clinical Claim (from IFU) | Data Source(s) | CER Section | Appraisal Quality | GSPR Addressed | Data Sufficient? | PMCF Gap? |
|---|---|---|---|---|---|---|---|
| CLM-001 | [Claim 1] | [Study 1, Study 2] | Section 6.1 | High | GSPR 1.1 | Yes | No |
| CLM-002 | [Claim 2] | [Study 3] | Section 6.1 | Medium | GSPR 1.1 | Partial | GAP-001 |
| CLM-003 | [Safety claim] | [PMS data, Literature] | Section 6.2 | High | GSPR 1.8 | Yes | No |
| CLM-004 | [Claim 4] | [Equivalence data] | Section 6.1 | Medium | GSPR 14.7 | Partial | GAP-003 |
CER Update Schedule by Risk Class
| Risk Class | Minimum Update Frequency | Trigger Events for Interim Update |
|---|---|---|
| Class I | Annually (or per PMS plan) | New safety signals; significant design change; new literature findings |
| Class IIa | Annually | New PMCF data; FSNN/FSCA; NB request; design change |
| Class IIb | Annually | All Class IIa triggers plus: new clinical investigation results; change in SOTA |
| Class III / Implantable | Annually (minimum); NB may require more frequent | All Class IIb triggers plus: periodic safety update; SSCP update; any PMCF activity completion |
Document Quality Checklist
Before submitting the CER to your Notified Body, verify:
| Check | Description | Pass? |
|---|---|---|
| 1. Scope defined | Intended purpose and scope clearly stated, matching IFU | Yes/No |
| 2. Evaluator qualified | Clinical evaluator has documented relevant expertise | Yes/No |
| 3. Literature search systematic | Protocol documented with databases, terms, inclusion/exclusion | Yes/No |
| 4. PRISMA diagram included | Literature screening process transparent | Yes/No |
| 5. Equivalence justified | Three dimensions assessed per MDCG 2020-5 (if used) | Yes/N/A |
| 6. Data quality appraised | Each source assessed for methodological quality and relevance | Yes/No |
| 7. Performance claims supported | Every IFU claim linked to clinical evidence | Yes/No |
| 8. Safety data comprehensive | All adverse events analyzed, including literature and PMS | Yes/No |
| 9. Benefit-risk explicit | Clear statement that benefits outweigh risks | Yes/No |
| 10. GSPR linkage | Clinical evidence mapped to specific GSPR requirements | Yes/No |
| 11. Data gaps identified | Every evidence gap documented with PMCF plan linkage | Yes/No |
| 12. PMCF cross-reference | PMCF activities address specific CER gaps | Yes/No |
| 13. Update schedule defined | Next review date and frequency stated | Yes/No |
| 14. Revision history complete | All versions and changes documented | Yes/No |
| 15. Signatures obtained | Clinical evaluator, reviewer, and approver signed | Yes/No |
Writing Best Practices
Based on Notified Body feedback patterns and industry experience:
Write in the third person — the CER is an objective evaluation, not an advocacy document
Define all terms — avoid unexplained jargon; if you use "equivalent device," define which device and justify equivalence in Section 4
Support every statement with a source — trace every claim to a specific data source, test report, or published reference
Use tables over prose — Notified Body reviewers scan tables faster than paragraphs; convert narrative descriptions to structured tables wherever possible
Tell a coherent clinical story — the CER should read as a logical progression from device description through evidence to conclusions, not a collection of disconnected sections
Address unfavorable data — omitting contradictory evidence destroys credibility; acknowledge it and explain why it does not undermine the overall conclusion
Draft CER and PMCF Plan in parallel — the two documents must cross-reference each other explicitly; create a formal data gap table in the CER, then map each gap to a specific PMCF activity
Common CER Nonconformities and How This Template Prevents Them
| NB Nonconformity | Root Cause | How This Template Addresses It |
|---|---|---|
| "Insufficient clinical evidence to support performance claims" | Claims not mapped to data | Evidence Traceability Matrix (Claim ID → Data Source) |
| "Equivalence not adequately justified" | Only clinical comparability assessed, not technical/biological | Three-dimension Equivalence Table (Section 4) |
| "Literature search methodology not documented" | No search protocol included | Literature Search Protocol Summary (Section 3.2) + PRISMA diagram |
| "No data gap analysis" | CER treats existing evidence as complete | Data Gap Table with PMCF linkage (Section 9) |
| "CER not updated to reflect PMCF data" | CER treated as one-time document | Update Schedule (Section 1.7) + PMCF Cross-Reference (Section 9.2) |
| "Clinical evaluator qualifications not documented" | No CV or qualification statement | Evaluator Qualification Table (Section 1.6) |
| "Benefit-risk analysis not linked to risk management" | Separate documents with no cross-reference | ISO 14971 Alignment Table (Section 7.2) |
| "No mapping to GSPR" | Clinical evidence presented without regulatory context | GSPR Compliance Table (Section 8) |
MEDDEV 2.7/1 Rev. 4 vs. EU MDR Annex XIV vs. MDCG 2020-13
Understanding the relationship between these three documents is essential for CER structure:
| Aspect | MEDDEV 2.7/1 Rev. 4 | EU MDR Annex XIV | MDCG 2020-13 |
|---|---|---|---|
| Status | Guidance document (no longer updated, still referenced) | Binding regulation | NB assessment template |
| Purpose | Methodology for clinical evaluation | Legal requirements for the process | Format for NB assessment of CER |
| Structure guidance | Detailed section-by-section | High-level process steps | Assessment report structure |
| Equivalence | Three dimensions described | Referenced in Article 61 | Assessment criteria |
| PMCF linkage | Required | Required by Article 61(11) | Assessed by NB |
| Practical use | Use for CER methodology | Use for legal compliance | Use to understand NB expectations |
Key References
| Document | Description |
|---|---|
| Regulation (EU) 2017/745, Article 61 | Clinical evaluation requirement |
| Regulation (EU) 2017/745, Annex XIV Parts A and B | Clinical evaluation process |
| MEDDEV 2.7/1 Rev. 4 | Clinical evaluation methodology |
| MDCG 2020-5 | Clinical evidence — equivalence |
| MDCG 2020-6 | Clinical evidence for legacy devices |
| MDCG 2020-13 | Clinical evaluation assessment report template |
| MDCG 2022-21 | Template for technical documentation related to custom-made devices |
| ISO 14971:2019 | Risk management |
| ISO 14155:2020 | Clinical investigation of medical devices |
| PRISMA Statement | Preferred Reporting Items for Systematic Reviews and Meta-Analyses |
Sources: Regulation (EU) 2017/745 Article 61 and Annex XIV; MEDDEV 2.7/1 Revision 4; MDCG 2020-5, 2020-6, 2020-13; MedTech Europe IVDR & MDR Survey Results 2024; Global RWC EU MDR CER Requirements 2025; Celegence CER Template and CAPTIS structure; PRISMA Statement.