The Workbench · Craft

The notified body keeps its own report on your CER

This blog has already covered how MDR Article 61 narrowed the clinical evaluation's equivalence route, and how an FDA acceptance checklist only confirms a document's presence, not its content. A clinical evaluation report sits at an odd meeting point between those two lessons. A manufacturer builds one document, submits it, and often assumes the notified body's review happens somewhere inside that same document's own margins. It doesn't. The reviewer keeps a separate report of its own, built to a separate structure, and a CER written without that second document in mind is aimed at the wrong reader.

A second report the manufacturer doesn't write

MDR Article 61 requires a manufacturer's clinical evaluation to conform with the general safety and performance requirements, documented in a clinical evaluation report the notified body then has to review as part of conformity assessment. What that review produces is its own artifact: a clinical evaluation assessment report, the document a notified body's own reviewers write to record their conclusions about the manufacturer's CER, not a mark-up of the CER itself. The Medical Device Coordination Group published a template for that document in mid-2020, MDCG 2020-13, and while the template isn't binding on any notified body, its structure has become the de facto shape most reviewers now use to record an assessment — which makes it worth reading for what it reveals about what's actually being checked, not for what it asks a manufacturer to submit.

Not a CER template, and treating it as one misreads both documents

MDCG 2020-13 is easy to mistake for a drafting guide, since its section headings track a CER's own subject matter closely — device description and classification, the clinical evaluation plan, the state of the art. It isn't one. MEDDEV 2.7/1 Rev. 4 remains the methodology a CER's own literature search and appraisal get built and checked against; MDCG 2020-13 is the separate document a reviewer fills in afterward, recording an independent judgment rather than restating the manufacturer's own conclusions. A regulatory affairs team that reorganizes its CER around the assessment template's own headings has copied the reviewer's filing structure without gaining anything the reviewer is actually looking for.

The reviewers get checked too, on both sides of the file

One thing the assessment template asks for has no equivalent in most manufacturers' own CER habits: a section documenting who conducted the notified body's own review, their qualifications, and any conflict of interest. That requirement doesn't appear in isolation. Annex XIV Part A's own clinical evaluation duty is meant to be carried out with documented objectivity, and MEDDEV 2.7/1 Rev. 4's methodology has long expected a CER to name its own evaluators, their relevant clinical or scientific qualifications, and a statement that no undisclosed relationship compromises their independence. A CER that reaches a well-supported benefit-risk conclusion, attached to an evaluator section that's thin, unnamed, or silent on independence, is handing a reviewer whose own assessment template asks the identical question about itself a reason to doubt the conclusion before reading past the first page.

The conclusion isn't a restatement, it's an independent finding

The assessment report's own benefit-risk section isn't a summary of what the CER already said. It's the notified body's own judgment on whether the clinical evidence, as presented, actually supports conformity with Annex I's general safety and performance requirements — including whether an equivalence argument survives the technical, biological, and clinical test this blog has already covered, and whether the state-of-the-art comparison holds up against what the reviewer's own domain knowledge suggests it should. A manufacturer rarely sees the assessment report itself, but its outcome surfaces as a deficiency letter or a request for clarification, and a CER built only to satisfy its own internal logic, without anticipating that a second, independently reasoned document sits behind the review, is usually where those requests originate.

Where this meets the file

A clinical evaluation report outline needs its own evaluator section — names, qualifications, and a documented independence statement — carried as a distinct, complete part of the file rather than a footnote assumed to be self-evident, precisely because it's one of the concrete items a reviewer's own assessment template checks independent of the clinical conclusion itself. A CER outline built around that structure, alongside the launch catalog's other clinical-documentation templates, is previewed there now. If your program documents its evaluators differently, the shelf takes that correction directly.

The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.

All Workbench notes