How do you respond to a Notified Body deficiency letter on a Clinical Evaluation Report?
What a deficiency letter is, and where it comes from
A Notified Body deficiency letter — also called a non-conformity report or open items list — is the formal record that the Clinical Evaluation Report as submitted does not yet demonstrate that the device meets the clinical evaluation obligations of Article 61 and Annex XIV of Regulation (EU) 2017/745. It is a checkpoint in an iterative assessment, not a rejection.
Behind the letter sits an internal document. Assessors record their conclusions in a Clinical Evaluation Assessment Report, whose structure is set out in MDCG 2020-13: device description and classification, literature review, clinical investigations, safety and performance, equivalence, post-market activities, labelling. Reading your findings against that section order shows which part of the assessment could not be closed — usually more informative than the wording of the finding.
Article 61 requires a "defined and methodologically sound procedure" built on three elements: critical examination of pertinent scientific literature, critical review of accessible clinical investigation results, and assessment of existing alternative treatment options. Most findings amount to one of the three being present as a conclusion but not as a method. Deadlines and review rounds come from the letter and the Notified Body's procedures, not the regulation.
The recurring deficiency categories, and what the reviewer is actually asking for
Certain findings recur across manufacturers and classes. Identifying the category early decides the strategy: some are documentation work, others are evidence generation that cannot be written around.
| Deficiency category | What the Notified Body needs to see |
|---|---|
| State-of-the-art not established | A prespecified, reproducible literature search: databases, search strings, date ranges, inclusion and exclusion criteria, screening decisions, audit trail. Missing PRISMA-style flow diagrams and vague appraisal criteria are the usual symptoms. |
| Equivalence claim not substantiated | Demonstration across all three pillars — technical, biological and clinical — under Annex XIV Part A Section 3, with a documented gap analysis and sufficient access to the reference device's data, not a feature comparison table. |
| Insufficient clinical data for the claimed intended purpose | Evidence stratified by the patient populations, device variants and user groups named in the intended purpose, so no claimed subgroup rests only on aggregate data. |
| Benefit-risk not quantified | Safety and performance objectives as measurable outcome parameters, with benefit-risk supported by quantitative comparison against the state-of-the-art baseline rather than a general assertion of acceptability. |
| PMCF plan not justified | An Annex XIV Part B plan justifying method, design, data volume and time schedule against a named residual risk or data gap — evidence generation, not a post-approval formality. |
| Technical file lacks a coherent narrative | Traceable links from hazard to risk control to verification evidence to clinical conclusion, followable without reconstruction from several documents. |
Structure the response so the traceability table is the deliverable
The highest-value document in a response package is not the revised CER but the point-by-point traceability table in front of it. An assessor closing items checks whether each numbered finding was answered; a table allows that without a full re-read.
A working table needs, at minimum:
- Deficiency reference — verbatim, in the Notified Body's numbering, never renumbered.
- Deficiency text — quoted, so a partial answer cannot look complete.
- Location of the change — revised CER version, section and page, so the assessor navigates directly rather than through a redline.
- What changed — a substantive one- or two-sentence description. "Updated as requested" is not a response.
- New evidence added — the source: literature added under the revised protocol, a PMCF interim report, further investigation data, a reworked gap analysis.
- Residual limitation — where evidence still does not cover the claim, stated openly with the mitigation or planned PMCF activity.
Every finding gets a row, and where one finding drove edits in several sections, each section gets its own row. Traceability, not prose, is what is graded.
The state-of-the-art and equivalence traps under Annex XIV Part A
Both areas produce repeat findings because they are drafted as narrative and assessed as method. On state-of-the-art, Annex XIV Part A requires the clinical evaluation plan to establish the state of the art through a systematic literature search. A finding here is rarely about the conclusion drawn; it is about whether an independent reader following your protocol reaches the same included set. Adding references to the discussion without repairing the protocol reproduces the finding next round.
On equivalence, MDCG 2020-5 treats technical, biological and clinical characteristics cumulatively and expects a gap analysis, not a declaration that differences are minor. The Annex XIV Part A Section 3 test is similarity such that there is no clinically meaningful difference in safety and clinical performance. Access to the reference device's data matters as much as the comparison: without it the route may be indefensible however the table is formatted. MDCG 2020-5 also restricts equivalence for implantable and Class III devices.
Two guidances shape what "sufficient" means. MDCG 2020-6 covers devices previously marketed under Directives 93/42/EEC or 90/385/EEC, defining sufficient clinical evidence for legacy devices and how post-market data is integrated. MDCG 2020-1 covers medical device software, framing evidence around valid clinical association, technical and analytical performance, clinical performance and benefit-risk — worth adopting in a software CER because it mirrors the assessment.
When the honest answer is new evidence, not a better argument
Some findings cannot be closed by writing. If the evidence genuinely does not cover a population, variant or use duration the intended purpose claims, the defensible response is to say so and propose a scoped evidence path: a PMCF study, registry participation, or a clinical investigation.
Annex XIV Part B sets what such a plan must do: confirm safety and performance across the device lifetime, identify previously unknown side-effects, monitor the rate and severity of known ones, analyse emergent risks, keep benefit-risk acceptable, and identify systematic misuse or off-label use. It expects general procedures (clinical experience collection, user feedback, literature screening) and specific methods (registry evaluation, PMCF studies), each with justification and a time schedule; MDCG 2020-7 gives the plan template, MDCG 2020-8 the evaluation report template. A commitment scoped to the residual uncertainty named in the finding is a legitimate closure route, not an admission of failure.
Keep the response consistent with the post-market documents
A revised CER that contradicts the post-market file invites a new finding. Article 83 requires a surveillance system that continuously verifies development-phase results using real-world data; Article 84 requires a PMS plan defining what data is needed, how it is collected and how it is assessed across risk management, design and manufacturing information, clinical evaluation and trend detection. Article 85 covers the Post-Market Surveillance Report; Article 86 sets periodic reporting by class.
| Class | Periodic reporting requirement (Article 86) |
|---|---|
| Class IIa | PSUR updated at least every two years, and when necessary. |
| Class IIb | PSUR updated at least annually. |
| Class III | PSUR updated at least annually and submitted via EUDAMED to the notified body. |
Scope limits: whether "every two years" means calendar or rolling years is unverified here, as is whether MDCG 2020-13 remains the current assessment-report guidance — MDCG 2023-7 on the practical application of Article 61 exists and was not reviewed. Check the reporting boundary for your class against the regulation text, not any summary.
For implantable and Class III devices, Article 32 adds the Summary of Safety and Clinical Performance, written for end users — healthcare professionals and, where applicable, patients. It must give a balanced summary of favourable and unfavourable data including residual risks and mitigation, goes to a notified body for validation, and is published in EUDAMED; MDCG 2019-9 Rev.1 sets its eight-section structure. Because it is public, a claim softened in the CER response must be softened there too.
What not to do
- Do not rebut clinical judgement in prose. An essay without evidence and a traceability map reads as avoidance.
- Do not resubmit a silently rewritten CER. With no index of changes, the assessor re-reviews from scratch.
- Do not strengthen the claim to cover the gap. Benefit-risk or equivalence statements that outrun the data stack a new finding on the original.
- Do not answer an evidence gap with reinterpretation. Re-reading the same dataset does not change what it covers.
- Do not fix one section in isolation. Changes to intended purpose, benefit-risk or claimed population propagate into the risk management file, PMCF plan, PMS plan, labelling and, where applicable, the SSCP.
Where Clinoble fits
Clinoble Innovations Private Limited (Hyderabad, Telangana, India; founder and director Dr. Jaideep Rao M., MBBS, MD Community Medicine) provides EU MDR clinical evaluation writing as subcontract capacity: CER authoring and revision, deficiency response packages built around traceability tables, documented literature search protocols, PMCF plans and evaluation reports on the MDCG 2020-7 and 2020-8 templates, PSUR and PMS reports, and SSCP drafting on MDCG 2019-9 Rev.1.
The engaging manufacturer or consultancy remains the signing party and owner of the Technical Documentation. Clinoble holds no Notified Body relationship or endorsement and does not represent manufacturers before Notified Bodies; the work is document preparation and evidence structuring. Scope details are at /clinical-evaluation-services.html. Clinoble also develops screening-aid and decision-support software, with two Indian patent applications pending in quantitative clinical imaging (IND 202641088451, IND 202641090786): /cardiopulmo.html, /tb-first.html, /nethra.html.
Working to a deficiency deadline on a CER, PMCF plan, PSUR or SSCP? Reach Clinoble about subcontract capacity.