Narrative Writing for Case Processing & Aggregate Reports · Section 5.6
~7 min read · The Drug Safety Coach — Global PV Career Course
Key points
Weak phrasing vs. strong phrasing — and why the fix matters
| Weak | Strong | Why the fix matters |
|---|---|---|
| "The reaction was clearly caused by the drug." | "The reporter considered the event related to the drug." | Keeps causality as a reported assessment, not the narrative writer’s own conclusion |
| "Patient had a bad reaction and was fine after." | "The patient developed a Grade 2 rash, treated with an antihistamine, with full resolution within 5 days." | Replaces vague, unquantified language with specific, verifiable clinical detail |
| "After the event (which started a few days after the second event described below)..." | Events reordered into the actual chronological sequence before writing | Forces the reader to reconstruct the timeline themselves — the narrative should do that work, not the reader |
| "Patient experienced pruritus, urticaria, angioedema." | "The patient developed itching, hives, and facial/lip swelling within 30 minutes of the dose." | Reads as a clinical account rather than a list of MedDRA terms with commas between them |
Full text
Experienced reviewers don’t read every narrative equally carefully — they’ve learned to scan for a small number of recurring error patterns, because those patterns account for a disproportionate share of the narratives that get sent back for rework. Causality creep, covered in the previous lesson, is one. Vague quantification is another: phrases like "a bad reaction," "significant improvement," or "a high fever" sound descriptive but convey almost no verifiable information — what grade of reaction, improvement measured how, a fever of what temperature. Nearly always, the source document actually contains the specific number or grade, and it simply didn’t make it into the narrative.
Out-of-order events are the chronology problem from the previous lesson showing up as a specific, recognisable pattern: a narrative that has to reference something "described below" or "as mentioned earlier" is a narrative admitting, in its own phrasing, that the events weren’t reordered before writing. A reviewer sees this immediately, because a well-sequenced narrative never needs to point backward or forward at itself — everything is already in the order the reader needs it.
MedDRA-term listing, from the previous lesson, is the fourth recurring pattern: a narrative that reads like coded terms with commas between them rather than a clinical description. All four of these patterns share something in common — they’re not really writing-style problems, they’re signs that a step in the process got skipped: causality wasn’t separated from description, specific clinical detail wasn’t pulled from the source, events weren’t reordered before drafting, or the narrative was drafted directly from the coding screen instead of from the clinical picture.
That’s exactly why fixing the pattern matters more than fixing the individual sentence. A writer who understands why "clearly caused by" is a problem will catch it themselves in the next case; a writer who’s just told to change one sentence in one narrative will make the same substitution error again next week under a different phrasing. Reviewers who train junior writers tend to name the pattern explicitly — "this is causality creep," "this is MedDRA-term listing" — precisely so the lesson generalises past the specific case in front of them.
Quick check
Test yourself before moving on — no pressure, just click an answer.
1. Why do experienced reviewers scan for a small set of recurring error patterns rather than reading every narrative with equal scrutiny?
2. A narrative reads "the second event (described below) preceded the first event." What error pattern does this signal?