Risk-benefit determination under MDR – what actually changes your conclusion
I have seen risk-benefit analyses that run for thirty pages yet fail to conclude anything about acceptability. Teams present mountains of data. They describe every risk in detail. They cite every benefit. But when the Notified Body asks whether the benefit-risk profile is favorable, the answer becomes vague. This is not a documentation problem. It is a reasoning problem.
In This Article
The risk-benefit determination is not a summary exercise. It is not a section you write after everything else is done. It is the clinical conclusion that justifies placing your device on the market under MDR Article 61(1) and General Safety and Performance Requirement 1 of Annex I. Yet many manufacturers treat it as a formality.
The result is predictable. Notified Bodies reject conclusions that lack structure. Auditors flag missing elements. And manufacturers rewrite sections without understanding what was actually missing.
The question is not whether your device is safe. The question is whether you have demonstrated, with clinical evidence, that the residual risks are acceptable when weighed against the clinical benefits for the intended patient population.
What the regulation actually requires
MDR Annex I, Chapter I, states that devices must achieve their intended performance without compromising the clinical condition or safety of patients. Residual risks must be acceptable when weighed against the benefits.
MDCG 2020-6 on sufficient clinical evidence clarifies that the risk-benefit determination must be based on clinical data. It is not a theoretical exercise. It is not based on assumptions. It is a conclusion drawn from your clinical evaluation.
Yet the regulation does not provide a formula. It does not tell you how to weigh a 2% complication rate against a 15% improvement in clinical outcome. It does not define what makes a residual risk acceptable.
This is where most manufacturers struggle. They look for a checklist when what they need is a reasoning framework.
The risk-benefit determination is not about proving your device is perfect. It is about demonstrating that the clinical benefit justifies the residual risk for the intended use and patient population.
The inputs that actually matter
Your risk-benefit conclusion depends on three inputs. If any of these is weak, your conclusion will be questioned.
The residual risk profile
This comes from your risk management file under ISO 14971. But not all risk information is relevant to the clinical evaluation. What matters is the residual risk after all mitigation measures have been applied.
Many teams copy the entire risk table into the clinical evaluation report. This adds volume but not clarity. What the Notified Body needs is a clinical interpretation of the residual risks.
Which risks affect patient safety directly? Which risks are clinically significant? What is the frequency and severity based on clinical data, not just theoretical estimates?
If your risk management process relies on risk estimates that are not validated by clinical evidence, your risk-benefit determination will be challenged.
The clinical benefit profile
This is where many reports fail. They describe what the device does. They explain the mechanism of action. They present technical performance data. But they do not demonstrate clinical benefit.
Clinical benefit is the positive impact on the health of the patient. It is measured in clinical outcomes. Symptom relief. Function restoration. Mortality reduction. Quality of life improvement.
If your device is equivalent to a predicate, the clinical benefit is drawn from equivalence. But you must still describe that benefit in clinical terms, not just claim equivalence and move on.
If your device is novel or has no valid equivalent device, you need your own clinical data. Performance testing alone does not establish clinical benefit.
Describing technical specifications or performance characteristics without linking them to patient outcomes. Clinical benefit is not what your device can do. It is what it achieves for the patient.
The intended patient population and clinical context
A 5% complication rate may be unacceptable for a low-risk screening device. The same rate may be entirely acceptable for a device used in life-threatening conditions where no alternative exists.
Your risk-benefit determination must be anchored in the clinical context. What is the severity of the condition being treated? What are the available alternatives? What risks do those alternatives carry?
This is not theoretical. This is part of your state of the art analysis. You should know what the standard of care delivers and what risks patients currently face.
If your device introduces a new risk that does not exist with current treatments, you must justify why that trade-off is acceptable. If your device reduces an existing risk, that must be demonstrated with data.
How to structure the determination
The determination itself must follow a logical sequence. This is not about writing style. This is about reasoning that can be followed and challenged.
Step one: State the residual risks clearly
List the residual risks that are clinically relevant. Include frequency and severity based on clinical evidence. If data is limited, state that explicitly and explain the level of uncertainty.
Do not bury this in a table. Write it out. The reviewer should understand what risks remain after all mitigation measures.
Step two: State the clinical benefits clearly
Describe the clinical benefit in measurable terms. Use clinical outcomes from your appraisal. If your claim is based on equivalence, reference the equivalent device data but describe the benefit in patient terms.
Do not use vague language. “Improves patient outcomes” is not sufficient. Specify what improves, by how much, in which population.
Step three: Compare risks and benefits in context
This is where the clinical judgment happens. You are weighing residual risk against benefit within the clinical context.
Consider the severity of the condition. Consider the alternatives. Consider whether the benefit is significant enough to justify the residual risk.
If the benefit is marginal and the risk is material, you have a problem. If the benefit is substantial and the risk is minimal or well-managed, your conclusion is easier to support.
But you must make the reasoning explicit. Do not assume the reviewer will agree. Show the logic.
Step four: State the conclusion
After presenting the risks, the benefits, and the reasoning, state your conclusion clearly. Is the benefit-risk profile favorable? Yes or no.
If yes, state it plainly. If there are conditions under which the profile remains favorable, specify those conditions. If there are limitations, acknowledge them.
Do not hedge. Do not write “the benefit-risk profile appears to be generally acceptable in most cases.” That is not a conclusion. That is avoidance.
The conclusion must be a definitive statement. Notified Bodies are not looking for perfect safety. They are looking for a reasoned judgment supported by clinical evidence.
What actually changes your conclusion
Here is what many teams misunderstand. The risk-benefit determination is not static. It changes when the inputs change.
If post-market data reveals a risk that was underestimated, your conclusion must be reconsidered. If clinical follow-up shows that the benefit is smaller than expected, your conclusion may no longer hold.
This is why the clinical evaluation must be updated. This is why PMCF exists. You are not writing a conclusion once and defending it forever. You are maintaining a conclusion that reflects current evidence.
When new data contradicts your original determination, you have three options. Update the conclusion if the profile is still favorable. Implement additional risk mitigation and reassess. Or withdraw the device if the profile is no longer acceptable.
What you cannot do is ignore the data and keep the old conclusion.
Treating the risk-benefit determination as a one-time document that does not evolve with post-market data. The determination must be revisited every time the clinical evaluation is updated.
How Notified Bodies review your determination
Notified Bodies do not take your conclusion at face value. They trace the reasoning back to the evidence.
They check whether the residual risks are supported by clinical data or only by theoretical estimates. They check whether the clinical benefits are demonstrated or only claimed. They check whether the comparison makes sense for the intended population and use.
If any link in that chain is weak, they will challenge the conclusion. And if your response is to add more text without addressing the gap in evidence, the deficiency will remain open.
The review is not about the length of your report. It is about the strength of your reasoning and the quality of your evidence.
Why this matters more than you think
The risk-benefit determination is not a formality. It is the clinical justification for your device being on the market.
If that determination is weak, everything downstream is at risk. Your conformity assessment. Your post-market surveillance response. Your ability to defend the device in a regulatory query or legal challenge.
This is not about writing better sentences. This is about making better clinical arguments based on real evidence.
When you sit down to write the risk-benefit section, ask yourself: If a reviewer questioned every sentence, could I defend it with data? If the answer is no, you do not have a documentation problem. You have an evidence problem.
Fix the evidence first. The conclusion will follow.
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). MDCG 2020-6, MDR Annex I
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, Annex I, Chapter I, General Safety and Performance Requirements
– MDR 2017/745, Article 61(1)
– MDCG 2020-6, Regulation (EU) 2017/745: Sufficient clinical evidence for legacy devices
– ISO 14971, Medical devices – Application of risk management to medical devices
Deepen Your Knowledge
Read Complete Guide to Clinical Evaluation under EU MDR for a comprehensive overview of clinical evaluation under EU MDR 2017/745.
