How to Write a Pharmacovigilance Case Narrative (With Template)

To write a pharmacovigilance case narrative, describe the case as a concise clinical story in time order: the patient, the suspect drug and its dates, the adverse event and its course, treatment, outcome and follow-up. Remove identifying details, then check that the narrative matches the coded ICSR fields.
This guide explains how to write a pharmacovigilance case narrative from start to finish. It covers required content, a standard structure, a reusable template, a worked example and the mistakes that most often cause reviewers to send a narrative back. It is written for safety associates, case processors and regulatory staff, and for graduates preparing for their first drug safety role.
What goes into a pharmacovigilance case narrative?
A case narrative is the free-text clinical summary that accompanies an individual case safety report (ICSR). EU guidance requires a case narrative for all cases except non-serious ones, and it should be provided where possible [1]. In this context, 'where possible' means the primary source has supplied enough information to prepare a concise clinical summary of the case [1].
Build These Skills Now
Programs from ZANE ProEd Academy that directly address the skill gaps discussed above.
The narrative must present the patient's experience in a logical time sequence. It should cover the clinical course, therapeutic measures, outcome and any follow-up information obtained, and it should summarise any relevant autopsy or post-mortem findings [1]. The narrative also has to be consistent with the structured ICSR data elements, so the same facts should appear in both places [1].
In practice, a complete narrative draws on the following content:
- Patient: age or age group, sex and relevant medical history, with no name, initials or other identifiers.
- Products: suspect and concomitant medicines, doses, routes, start and stop dates and indications.
- Adverse event: onset date, signs and symptoms, seriousness criteria and key investigations with dates and results.
- Management: treatment given, and what happened when the suspect drug was stopped or restarted.
- Outcome: recovered, recovering, not recovered, fatal or unknown, and the date of the outcome where known.
- Reporter comment: the reporter's causality view, where the source provides one.
The narrative must not identify the patient or the healthcare professionals and treatment centres involved [1]. Keep those details in the source document and the case file, not in the narrative text.
Each ICSR also carries structured identifiers, such as the sender's case safety report unique identifier and the worldwide unique case identification number [2]. The narrative does not replace these fields, but it must agree with them.
What is the standard narrative structure?
EU guidance points to the CIOMS Working Group V report as an example of a standard narrative template [1]. Most organisations adapt that model into a fixed order of sections, so that any reviewer can find the same information in the same place. The order below is a common working pattern rather than a mandated layout.
- Opening sentence: age, sex, the suspect drug, the adverse event and the date of onset.
- Medical history: relevant conditions, allergies and risk factors that bear on the event.
- Drug history: the suspect drug and any concomitant products, with doses, routes, dates and indications.
- Event description and chronology: the clinical course in date order, including investigations and results.
- Management and dechallenge or rechallenge: treatment given and what happened when the drug was stopped or restarted.
- Outcome: the status at the last contact, with the date.
- Reporter comment: causality view, if provided, and any clinical reasoning the reporter gave.
- Follow-up status: what information is still awaited and whether a follow-up request has been raised.
The table below shows what each section should contain and what the reader should be able to answer after reading it.
| Section | What to write | Question the reader should be able to answer |
|---|---|---|
| Opening sentence | Age, sex, suspect drug, event, onset date | What happened, to whom, and with which product? |
| Medical history | Relevant conditions and risk factors only | Did anything in the patient's background make the event more likely? |
| Drug history | Doses, routes, start and stop dates, indications | When was the drug taken and why? |
| Chronology | Dated events and investigation results | What was the order of events? |
| Management | Treatment and dechallenge or rechallenge result | What was done, and did the event change? |
| Outcome | Status and date at last contact | Where does the patient stand now? |
| Follow-up | Missing information and requests raised | What is still unknown? |
Worked example
The example below uses invented facts to show the structure and tone. Treat it as a pattern, not as text to copy.
A 62-year-old woman with type 2 diabetes and hypertension started drug X 10 mg orally once daily on 3 March for hypertension. On 17 March she developed a dry cough. On 21 March she was admitted with swelling of the lips and tongue, and the suspect drug was stopped on admission. Treatment with an antihistamine and a corticosteroid was given, and the swelling had resolved by 23 March. Her serum potassium on admission was within the reference range. The outcome at last contact was recovered. The reporting physician considered a relationship with drug X possible. A follow-up request has been sent for the discharge summary.
Notice that the narrative runs in date order, gives the dechallenge result, states the outcome with a date, and records what is still outstanding. It contains no name, no hospital name and no reporter identity.
Step-by-step: drafting the narrative
- Read the source document and list every dated fact, with its source.
- Build a timeline from the earliest exposure to the last contact.
- Mark the seriousness criteria and the key clinical findings.
- Draft the narrative in the section order above, one fact per sentence where possible.
- Remove all direct and indirect identifiers.
- Check that dates, doses, outcome and terms agree with the coded ICSR fields, including the MedDRA terms.
- Run a quality check for missing dates, unsupported statements and unexplained abbreviations, then record any follow-up requests.
For the surrounding workflow, see ICSR Case Processing Steps: Workflow and Worked Example. It shows where the narrative fits between intake and case closure.
What are common narrative writing mistakes?
Most narrative defects come from three sources: facts that are missing or unsupported, a chronology that is hard to follow, and content that does not belong in a regulatory narrative. Reviewers usually catch these during quality checks, but a clean narrative from the start saves rework.
| Mistake | Why it matters | How to fix it |
|---|---|---|
| Narrative does not match coded data | Inconsistency between the narrative and E2B fields undermines the report [1] | Cross-check dates, doses, outcome and terms before closing the case |
| Identifiers left in the text | Narratives must not identify the patient or healthcare professionals [1] | Replace names with a neutral description such as a 62-year-old woman |
| Events out of time order | The reader cannot judge dechallenge or timing | Rebuild the timeline and rewrite in date order |
| Vague terms such as 'some improvement' | The outcome cannot be coded or assessed | State the status and the date it was recorded |
| Unexplained abbreviations | Readers in other regions may not understand them | Spell out the term on first use |
| Speculation presented as fact | It misleads causality assessment | Attribute views to the reporter and state what is not known |
Before the narrative is finalised, check whether the case should be nullified rather than updated. EU guidance gives examples, including a duplicate of a case previously sent by the same sender, a wrong worldwide unique case identification number, an adverse reaction that began before the suspect drug was taken, and confirmation that the patient did not receive the drug [1]. In those cases the case is nullified, and the narrative should not be written as an active case.
Narratives also appear in periodic safety update reports, but the rules differ there. In a PSUR, case narratives are clinical evaluations of important or illustrative cases in the risk evaluation section, and the CIOMS narrative text itself is not normally reproduced [4]. Write a separate clinical evaluation for that purpose rather than pasting the ICSR narrative.
Routine pharmacovigilance covers the collection of suspected adverse reaction information and the preparation of expedited reports and PSURs [3]. Good narratives are the basis for both, which is why the same discipline applies to every case.
Key takeaways
- Write the narrative in time order, covering history, drug exposure, the event, management, outcome and follow-up.
- EU guidance expects a narrative for all cases except non-serious ones, provided enough primary source information exists [1].
- Use a fixed section order so reviewers can find each fact quickly, following a CIOMS-style template [1].
- Never include identifiers for the patient or healthcare professionals in the narrative [1].
- Check that every date, dose and outcome in the narrative agrees with the coded ICSR data [1].
- Use narratives in PSURs as clinical evaluations of important or illustrative cases, not as pasted ICSR text [4].
Build These Skills Now
Programs from ZANE ProEd Academy that directly address the skill gaps discussed above.
Where can I practise writing case narratives hands-on?
Reading a template is not the same as drafting a narrative from a messy source document. The ZANE ProEd Pharmacovigilance Narrative Writing Certification gives you practice in narrative writing basics, source document review, causality assessment and MedDRA coding, alongside ICSR quality checks.
Frequently asked questions
Does every ICSR need a narrative?
No. EU guidance requires a narrative for all cases except non-serious ones [1]. For serious cases, the narrative should be provided where the primary source supports a concise clinical summary [1].
How long should a case narrative be?
Length should match the clinical complexity of the case and the information available. Sources do not set a fixed word count, so aim for a summary that a reviewer can follow without the source document.
What should I do when information is missing?
State in the narrative what is still unknown, and record a follow-up request to the primary source. Do not fill gaps with assumptions or reporter opinions presented as facts.
Can I reuse the ICSR narrative in a PSUR?
Not as a straight copy. A PSUR should include clinical evaluations of important or illustrative cases where they are integral to the analysis of a signal or safety concern, and the CIOMS narrative text itself need not be reproduced [4].
Sources
- EMA Good Pharmacovigilance Practices (GVP) Module VI: Collection, management and submission of reports of suspected adverse reactions (Rev 2). EMA.
- ICH E2B(R3): Electronic Transmission of Individual Case Safety Reports (ICSRs): Data Elements and Message Specification (R3). ICH.
- ICH E2E: Pharmacovigilance Planning (Step 4 (2004)). ICH.
- EMA Good Pharmacovigilance Practices (GVP) Module VII: Periodic safety update report (Rev 1). EMA.
Build These Skills Now
Programs from ZANE ProEd Academy that directly address the skill gaps discussed above.
Follow Zane ProEd on Google
Preferred SourceAdd our publication as a preferred source to get the latest clinical research guides, industry updates, and career intel directly in your Google Top Stories & AI Overviews.