Common narrative mistakes in clinical evaluations

As an experienced clinical evaluation writer, I see patterns that repeatedly trigger questions from reviewers, such as:

• Data technically complete, but the storyline is missing, and the reviewer must piece the story together across sections.
• Benefits described in strong marketing language (“significant improvement”) without quantification or without linking back to pre-defined clinical claims and acceptance criteria.
• Risks treated as a checklist, not as part of an actual benefit-risk comparison to patients in the real-world setting.
• Post‑market experience summarized as “no significant issues identified” without linking findings to the original safety and performance claims.
• Conclusions repeating intended use and study results, but not making any scientific analysis of the data.

All of these are narrative problems, not purely data problems. The good news is that they can often be fixed without generating new data, but by reshaping how existing data are presented. Here are some tips on how to do so.

Clarify the core storyline before writing.

Start with a short “story brief”:

• • • • What is the unmet need and what change does the device bring?
      • Which evidence is strongest, and where are the gaps?
      • What key message must a reviewer walk away with?

Map data to the story.

• Review clinical studies, PMS, PMCF, and literature, then organize them around the main clinical claims and the specific risks to be addressed. This ensures you are anwering the critical questions a reviewer is likely to ask.

  •  

  Draft the benefit-risk.

  • • Don't just list benefits and risks in isolation. A strong narrative links them. Ensure every clinical claim is backed by traceable data, and that your wording is precise. Avoid marketing fluff while staying aligned with MDR expectations. The goal is to lead the reviewer through a logical argument that starts with the clinical context and ends with a definitive, evidence-based conclusion. 

    • Turn technical language into readable arguments.

    • 
      Notified body reviewers are experts, but they are also human. You can help them by:
      

      • Interpreting tables and figures rather than just showing them. 
        • • Spelling out limitations and their practical impact.
            • Streamlining cross‑references (to risk management, PMS, PMCF, IFU) so they support the story rather than clutter it.

Prepare for questions and updates.

• • • A good narrative anticipates challenges. Address known data limitations or "gray areas" head-on within the text rather than waiting for the reviewer to find them. Furthermore, think of your CER as a living document. Explain how incoming PMS and PMCF data will refine this story over time, ensuring the narrative remains robust for future updates. 

A simple first step in using those tips is looking at one of your existing or draft CERs and asking the following questions.

1. Can someone unfamiliar with the device understand, within a few pages, exactly why it is worth using, despite its risks?
2. Is it obvious which data points are central to the conclusion?
3. Would a critical reviewer, under time pressure, come to the same benefit-risk conclusion?

If the answer is “not yet,” that is where a structured storytelling approach, and the right support, can make a noticeable difference. Qserve can help you to tell the best story about your devices. Please reach out to us for any further information!