Why Your Clinical Investigation Report Gets Sent Back
I reviewed a clinical investigation report last month that had been rejected three times by the same Notified Body. Same core issue every time. The structure was there. The data was there. But the report did not answer the questions the regulation actually asks.
In This Article
The manufacturer thought they had followed the protocol. They included all the tables. They discussed adverse events. But they missed what the regulation demands: a structured demonstration that the clinical investigation actually addresses the clinical evaluation plan.
This is not about missing sections. It is about understanding what each section must achieve under MDR.
The Regulatory Foundation
MDR Annex XV sets out the minimum content requirements for clinical investigation reports. But the regulation does not explain what good execution looks like. It lists elements. It does not tell you how those elements must connect to your clinical evaluation.
The result is reports that contain the right headings but fail to build the case Notified Bodies need to review.
Most deficiencies I see are not about missing data. They are about missing logic. The report does not show how the investigation outcomes support or challenge the benefit-risk determination.
A clinical investigation report is not a study report. It is a bridge document. It must connect the investigation protocol to the clinical evaluation. If that connection is weak, the report will be rejected regardless of how well the study was executed.
What the Report Must Demonstrate
The report structure under MDR is built around accountability. Every section has a regulatory purpose. The structure forces you to show that the investigation was conducted as planned, that deviations were justified, and that outcomes are interpretable within the device’s clinical context.
Here is what that means in practice.
Study Identification and Regulatory Context
This section is not administrative. It establishes the legal basis for the investigation and confirms that the study was conducted under the correct regulatory pathway.
You must state whether the investigation was conducted under MDR Article 62 or under legacy directives during the transition period. You must reference the ethics committee approval and competent authority notification or authorization.
If the investigation was conducted in multiple member states, you must clarify whether it falls under the scope of the Clinical Trials Regulation (EU) No 536/2014 or remains under national frameworks.
Notified Bodies check this carefully. If the regulatory pathway is unclear, they cannot confirm that the investigation meets MDR requirements.
Investigators and Site Information
List the principal investigators, the clinical sites, and the qualification of personnel involved in the investigation. This is not a formality. It demonstrates that the investigation was conducted by appropriately qualified professionals in appropriate settings.
If the investigation involved high-risk procedures or vulnerable populations, the qualifications of the investigators become even more critical. Notified Bodies will assess whether the team had the expertise to execute the protocol safely and competently.
Investigators listed without evidence of relevant clinical expertise. If your device is used in cardiology, the investigators should have documented cardiology qualifications. Generic CVs do not satisfy this requirement.
Device Description and Conformity
Describe the device under investigation. Include the intended purpose, the technical specifications, and any modifications made during the investigation.
You must confirm that the device used in the investigation conforms to the design specifications and that any changes were documented and approved through your quality management system.
If the device evolved during the investigation, explain how design changes were managed and whether they affected the validity of the clinical data.
This section connects the investigation to your technical documentation. Notified Bodies cross-check this against your design dossier.
Objectives and Endpoints
State the primary and secondary objectives of the investigation. Describe the clinical endpoints used to assess safety and performance.
This section must align with your clinical evaluation plan. If your plan identified gaps in clinical evidence, the investigation objectives should address those gaps explicitly.
Notified Bodies will compare the stated objectives to the outcomes. If the investigation did not meet its primary endpoint, you must explain the implications for your benefit-risk determination.
Do not bury this. If the investigation failed to demonstrate what you intended, state it clearly and explain how the failure affects your clinical evaluation.
Study Design and Methodology
Describe the study design, the inclusion and exclusion criteria, the sample size calculation, and the statistical analysis plan.
Justify the design choices. If you used a single-arm study instead of a randomized controlled trial, explain why. If you chose a surrogate endpoint instead of a clinical outcome, justify the choice with reference to clinical practice or regulatory precedent.
This section should also address bias and confounding. Explain how the design minimized potential sources of bias and how you controlled for confounding variables.
Notified Bodies assess whether the design is appropriate for the clinical question. If the design is weak, the evidence generated will be considered weak regardless of how well the study was executed.
Justification is as important as execution. If you cannot explain why your study design is appropriate for the clinical question, the Notified Body will question the validity of your evidence.
Subject Accountability and Flow
Provide a complete account of subject enrollment, follow-up, and withdrawals. Use a CONSORT-style flow diagram to show how subjects moved through the study.
Explain every withdrawal and loss to follow-up. If subjects withdrew due to adverse events, describe those events and their outcomes. If subjects were lost to follow-up, explain the attempts made to contact them and assess whether the losses introduce bias.
This section demonstrates the integrity of your data. High withdrawal rates or unexplained losses raise concerns about the validity of your findings.
Baseline Characteristics
Describe the demographic and clinical characteristics of the study population. Compare these characteristics to the intended user population in your clinical evaluation.
If there are differences, explain them. If your study enrolled younger patients than your target population, explain how you will address the evidence gap. If your study excluded patients with comorbidities, explain the implications for your benefit-risk assessment.
Notified Bodies will assess whether the study population is representative of the real-world users of your device.
Results: Safety and Performance
Present the safety and performance outcomes in structured tables. Report all adverse events, serious adverse events, and device deficiencies.
Do not limit this section to statistical significance. Clinical significance matters more. A statistically significant improvement that has no clinical impact does not support a positive benefit-risk determination.
For safety outcomes, present the incidence, severity, and causality assessment for each adverse event. Explain how you determined causality and whether the events were anticipated or unanticipated.
For performance outcomes, present the results for all primary and secondary endpoints. If the study did not meet its endpoints, explain why and what that means for your device.
Results presented without interpretation. Tables full of numbers but no explanation of what the numbers mean for the clinical evaluation. Notified Bodies will not interpret your data for you.
Discussion and Clinical Implications
This is where most reports fail. The discussion section must connect the investigation outcomes to your clinical evaluation plan. It must explain how the results address the clinical questions you identified. It must interpret the findings in the context of the state of the art.
If the results confirm your benefit-risk determination, explain how. If the results challenge your assumptions, explain how you will address the discrepancy.
Compare your findings to the literature. If your results differ from published studies, explain why. If your results are consistent, explain how they strengthen your evidence base.
This section is not a summary. It is an argument. You are arguing that the clinical investigation provides sufficient evidence to support your benefit-risk determination under MDR Article 61.
Conclusions
State clearly whether the investigation met its objectives. State whether the results support the intended use and the benefit-risk determination.
If the investigation identified new risks or performance issues, state how you will address them. If the investigation raised new clinical questions, explain how you will answer them through post-market surveillance or additional investigations.
The conclusion must be definitive. Ambiguity here creates problems during Notified Body review.
How This Connects to Your Clinical Evaluation
The clinical investigation report does not stand alone. It feeds into your clinical evaluation report. Every finding in the investigation must be reflected in your appraisal of clinical data under MDR Annex XIV Part A.
If the investigation identified a new adverse event, that event must be discussed in your safety evaluation. If the investigation demonstrated a performance benefit, that benefit must be weighed in your benefit-risk analysis.
Notified Bodies cross-check the clinical investigation report against the clinical evaluation report. If there are inconsistencies, they will issue deficiencies.
I have seen clinical evaluation reports that ignored negative findings from clinical investigations. The manufacturer presented the investigation as supporting evidence but did not address the safety signals the investigation revealed. The Notified Body rejected the submission.
The lesson is simple: the clinical investigation report must be integrated into your clinical evaluation, not appended to it.
A well-structured clinical investigation report anticipates the clinical evaluation. It organizes findings in a way that makes integration straightforward. If your report requires extensive reinterpretation to fit into your clinical evaluation, the structure is wrong.
What Happens When the Structure Fails
When the structure is weak, Notified Bodies cannot assess whether the investigation meets MDR requirements. They cannot determine whether the investigation addresses your clinical evaluation plan. They cannot confirm that the evidence is sufficient.
The result is deficiency letters that ask for clarification, reanalysis, or resubmission. Each iteration adds months to your timeline.
The deficiencies I see most often are not about missing data. They are about missing connections. The report does not explain how the investigation fits into the overall clinical evidence. It does not show how the findings affect the benefit-risk determination.
Fixing these deficiencies requires rethinking the report structure. It requires reorganizing the content so that the logic is clear.
This is why structure matters. A well-structured report makes the case easy to follow. A poorly structured report makes the reviewer work to understand your evidence. Reviewers do not have time to work. They issue deficiencies.
Final Thought
The clinical investigation report is not a deliverable. It is a demonstration. You are demonstrating that the investigation was planned correctly, executed correctly, and analyzed correctly. You are demonstrating that the findings support your device’s safety and performance claims.
Structure is how you make that demonstration clear.
If the structure forces you to think through the connections between protocol, data, and clinical evaluation, it is doing its job. If the structure allows you to assemble sections without thinking through those connections, it will fail under review.
Next time you draft a clinical investigation report, ask yourself: does this report answer the questions my clinical evaluation plan asked? If not, the structure needs work.
Peace,
Hatem
Clinical Evaluation Expert for Medical Devices
Follow me for more insights and practical advice.
Frequently Asked Questions
What is a Clinical Evaluation Report (CER)?
A CER is a mandatory document under MDR 2017/745 that demonstrates the safety and performance of a medical device through systematic analysis of clinical data. It must be updated throughout the device lifecycle based on PMCF findings.
How often should the CER be updated?
The CER should be updated whenever significant new clinical data becomes available, after PMCF activities, when there are changes to the device or intended purpose, and at minimum during annual reviews as part of post-market surveillance.
What causes CER rejection by Notified Bodies?
Common reasons include inadequate equivalence demonstration, insufficient clinical data for claims, poorly structured SOTA analysis, missing gap analysis, and lack of clear benefit-risk determination. Structure and logical flow are as important as the data itself.
Which MDCG guidance documents are most relevant for clinical evaluation?
Key documents include MDCG 2020-5 (Equivalence), MDCG 2020-6 (Sufficient Clinical Evidence), MDCG 2020-13 (CEAR Template), MDCG 2020-7 (PMCF Plan), and MDCG 2020-8 (PMCF Evaluation Report).
Need Expert Help with Your Clinical Evaluation?
Get personalized guidance on MDR compliance, CER writing, and Notified Body preparation.
✌
Peace, Hatem
Your Clinical Evaluation Partner
Follow me for more insights and practical advice.
– Regulation (EU) 2017/745 (MDR), Annex XV
– MDR Article 61 (Clinical Evaluation)
– MDR Article 62 (Clinical Investigations)
– MDCG 2020-13 (Clinical Evaluation Assessment Report Template)





