Why Your Benefit-Risk Analysis Fails Before the Notified Body Sees It
I review clinical evaluation reports every week. Most of them contain a benefit-risk section. But when I read it carefully, I find the same pattern: residual risks listed without context, benefits described in marketing terms, and no real balancing logic. The manufacturer thinks the analysis is complete. The Notified Body disagrees.
In This Article
The benefit-risk analysis is not a formality. It is not a table to fill at the end of the CER. It is the central reasoning that supports the claim that your device is safe and performs as intended under normal conditions of use.
Yet, this section generates more deficiencies than almost any other part of the technical file. Why? Because manufacturers treat it as documentation instead of evaluation.
What the MDR Actually Requires
Article 61(1) of MDR 2017/745 states clearly: the clinical evaluation must demonstrate that the device achieves its intended performance, that the known and foreseeable risks are minimized and acceptable when weighed against the benefits, and that adverse events are acceptable when weighed against the intended performance.
This is not abstract. It is a legal requirement.
Annex XIV further specifies that the clinical evaluation must include a benefit-risk analysis, considering the intended clinical benefit, the probability of occurrence of adverse events, the nature and severity of those events, and the benefit-risk profile of alternative treatments or no treatment.
But here is what I observe: most benefit-risk analyses list risks from the risk management file and benefits from the instructions for use, then conclude that benefits outweigh risks. No weighting. No comparison. No clinical reasoning.
The benefit-risk section describes benefits and risks separately, but does not demonstrate how they were balanced or why the residual risks are acceptable in the clinical context of the intended use.
Where the Logic Breaks Down
The problem starts with how benefits are defined. I see statements like “improves patient outcomes,” “enhances quality of life,” or “reduces procedure time.” These are claims, not demonstrated benefits.
A benefit in the MDR context must be supported by clinical data. It must be specific, measurable, and relevant to the intended patient population. If your device reduces surgical time by 15 minutes compared to standard procedure, that is a benefit. But only if you have data showing that this reduction translates into clinical advantage—less blood loss, shorter anesthesia time, faster recovery.
The same applies to risks. Listing residual risks from ISO 14971 documentation is not enough. You must describe the clinical consequence of each risk, the probability in the intended use environment, and the severity in the context of the patient condition being treated.
This is where the analysis should happen. But most manufacturers stop before they start.
The Missing Step: Clinical Context
Every benefit and every risk must be interpreted within the clinical scenario where the device will be used. A risk that is minor in one population may be critical in another. A benefit that seems significant in isolation may be marginal when compared to existing treatment options.
I worked on a file where the device was intended for use in frail elderly patients. The risk management file listed a residual risk of minor skin irritation as low severity. But when we analyzed the clinical context, we realized that in this population, minor irritation could lead to non-compliance, treatment discontinuation, and worsening of the underlying condition. The severity was not low. The benefit-risk balance shifted.
This kind of reasoning does not appear in a table. It appears in paragraphs that explain the clinical relevance of each finding.
The benefit-risk analysis is not about listing data. It is about interpreting data in the context of the clinical problem, the patient population, and the alternative treatments. Without this interpretation, the analysis is incomplete.
How to Structure a Real Benefit-Risk Analysis
There is no single template that fits every device. But there is a logical structure that must be followed.
1. Define the Clinical Problem and the Intended Benefit
Start by describing the clinical condition or problem that the device is intended to address. What is the unmet need? What are the limitations of current treatment options? What specific benefit does your device claim to provide?
This sets the baseline for comparison. Every benefit you claim must be measured against this baseline.
2. Summarize the Clinical Evidence for Benefit
Present the data that supports each claimed benefit. Reference the clinical investigations, literature studies, or PMCF data that demonstrate the effect. Be specific. Quantify when possible. State the level of evidence.
If the benefit is based on surrogate endpoints, explain why those endpoints are clinically relevant. If the benefit is based on non-inferiority to a comparator, state the margin and justify it.
3. Summarize the Clinical Evidence for Risks
List the residual risks that remain after risk control measures. For each risk, provide the clinical consequence, the probability based on available data, and the severity in the context of the intended patient population.
Do not rely only on the risk management file. Clinical data may reveal risks that were underestimated during design. Post-market data may show that the probability of certain events is higher than predicted. Update your analysis accordingly.
4. Analyze Alternative Treatments
This is the step that most manufacturers skip. But it is required by Annex XIV.
What are the alternative treatment options for the same clinical condition? What are their benefits? What are their risks? How does your device compare?
If the alternative is no treatment, describe the natural progression of the condition and the associated risks. If the alternative is a different device or procedure, compare the benefit-risk profiles side by side.
This comparison provides the clinical justification for why your device is acceptable. A risk that would be unacceptable in a low-risk condition may be acceptable if the alternative is a high-risk surgical procedure.
5. Perform the Weighing
Now you can weigh. This is not a formula. This is clinical reasoning.
For each residual risk, explain why it is acceptable given the demonstrated benefit and the available alternatives. If the risk is serious but rare, and the benefit is significant and consistent, the balance may favor use. If the risk is common and the benefit is marginal compared to existing options, the balance may not favor use.
This reasoning must be documented. It must be transparent. It must be signed by a qualified person.
The benefit-risk conclusion states that benefits outweigh risks, but the document does not explain the reasoning process or how the balance was determined. This leaves the Notified Body with no basis to verify the claim.
What Notified Bodies Look For
When a Notified Body reviews your benefit-risk analysis, they are not checking boxes. They are verifying that the reasoning is sound.
They want to see that you understand the clinical context. That you have considered the patient population, the severity of the condition, the available alternatives. That you have used clinical data to support your conclusions.
They want to see that the analysis is updated with post-market data. That new risks identified through vigilance or PMCF are integrated. That the benefit-risk balance is reassessed when new information becomes available.
And they want to see traceability. Every claim in the benefit-risk section must be traceable to clinical data, risk management files, or scientific literature. If you state that a risk is rare, you must show the data that supports that statement. If you claim a benefit, you must reference the study that demonstrates it.
This level of rigor is not optional. It is what the MDR expects.
The Template Is Not the Analysis
Many companies ask for a template. I understand why. A template provides structure. It ensures that all required elements are covered.
But the template is not the analysis. The template is the container. The analysis is the content.
I have seen perfectly formatted benefit-risk tables that contain no real reasoning. I have also seen documents with no formal template that demonstrate clear, transparent, evidence-based balancing.
The Notified Body does not care about the format. They care about the substance.
If you use a template, make sure it guides you to perform the analysis, not to skip it. Make sure it prompts you to interpret data, compare alternatives, and document reasoning.
What a Good Template Should Include
If you are building or refining a benefit-risk template, here is what it should contain:
– A section for describing the clinical problem and the intended clinical benefit
– A section for summarizing the clinical evidence supporting each benefit
– A section for summarizing the residual risks and their clinical consequences
– A section for comparing the device to alternative treatments or no treatment
– A section for the weighing process, with clear reasoning for each conclusion
– A section for updating the analysis based on post-market data
– Traceability to supporting documents and data sources
This structure ensures that you follow the logic required by the MDR. But the structure alone does not produce a compliant analysis. You still need to fill it with real clinical reasoning.
A benefit-risk template is useful only if it forces you to think critically about the clinical evidence and the balancing logic. If it becomes a form to fill, it has failed its purpose.
Common Mistakes That Lead to Deficiencies
I see the same mistakes repeated across different manufacturers, different device types, different risk classes.
Mistake 1: Listing benefits without evidence. The benefit section reads like marketing material. Claims are made without reference to clinical data. The Notified Body asks for evidence, and the manufacturer realizes it does not exist.
Mistake 2: Copying risks from the risk management file without clinical interpretation. The risks are listed as technical failures or use errors, but the clinical consequences are not described. The severity ratings do not reflect the patient population or the clinical context.
Mistake 3: Ignoring alternative treatments. The analysis focuses only on the device in isolation. There is no comparison to existing options. The Notified Body cannot verify that the device offers an acceptable benefit-risk profile relative to what is already available.
Mistake 4: Concluding that benefits outweigh risks without explaining why. The analysis ends with a statement, not a reasoning process. There is no documentation of how the balance was determined or who made the decision.
Mistake 5: Failing to update the analysis with post-market data. The benefit-risk analysis is written once during initial certification and never revised. New adverse events are handled in vigilance reports, but not integrated into the CER. The analysis becomes outdated and non-compliant.
Each of these mistakes is avoidable. But avoiding them requires understanding what the MDR actually requires and applying clinical judgment to the documentation.
How to Strengthen Your Benefit-Risk Analysis
If you are revising your benefit-risk section, here are the steps that will improve it:
Step 1: Review your clinical evidence. Identify which data supports each claimed benefit. If a benefit is not supported by data, either remove the claim or plan a clinical investigation to generate the evidence.
Step 2: Analyze your residual risks in clinical terms. For each risk, describe what it means for the patient. Consider the severity in the context of the condition being treated and the vulnerability of the patient population.
Step 3: Research and document alternative treatments. Identify what clinicians would use if your device were not available. Compare the benefit-risk profiles. Use published literature, clinical guidelines, and expert opinion.
Step 4: Document the weighing process. Write paragraphs that explain why each risk is acceptable given the benefit and the alternatives. Use clinical reasoning. Reference specific data. Make the logic transparent.
Step 5: Integrate post-market data. Schedule regular reviews of vigilance reports, complaints, and PMCF findings. Update the benefit-risk analysis when new information changes the balance.
This is not a one-time exercise. The benefit-risk analysis is a living section of the CER. It must evolve as evidence accumulates and as the device moves through its lifecycle.
Final Thought
The benefit-risk analysis is not a compliance burden. It is the core justification for placing your device on the market. It answers the fundamental question: Is this device safe and effective for its intended purpose?
If the analysis is weak, the entire technical file is vulnerable. If the analysis is strong, it supports every other section and provides the clinical foundation for certification.
Do not delegate this section to junior staff. Do not copy templates without understanding the logic. Do not treat it as a formality.
Treat it as what it is: the clinical argument that proves your device is acceptable for use.
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.
– MDR 2017/745 Article 61, Annex XIV
– MDCG 2020-13 Clinical evaluation assessment report template
– ISO 14971:2019 Application of risk management to medical devices





