How to Write Aggregate Safety Reports
Introduction
Aggregate safety reports represent the highest level of pharmacovigilance assessment. Unlike individual case review, aggregate reporting requires reviewers to integrate diverse sources of evidence, evaluate scientific uncertainty and determine whether the cumulative understanding of a medicinal product has changed over time.
Although different report types have different regulatory objectives, they share common scientific principles. Experienced aggregate physicians therefore apply a consistent approach regardless of whether they are preparing a PBRER, DSUR, PADER or another aggregate report.
This article introduces those universal principles.
The Purpose of Aggregate Reports
Aggregate reports are not collections of safety information.
They are scientific evaluations.
Their purpose is to explain:
- what new evidence has emerged;
- how that evidence changes current knowledge;
- whether previous conclusions remain appropriate;
- whether additional pharmacovigilance or regulatory actions are required.
The emphasis should always remain on interpretation rather than description.
The Four Levels of Pharmacovigilance Thinking
Every aggregate report should progress through four distinct stages.
Level 1 — Observation
What happened?
Examples include:
- new ICSRs;
- literature publications;
- clinical trial findings;
- PASS results.
Level 2 — Interpretation
What do the observations mean?
The reviewer evaluates:
- causality;
- consistency;
- biological plausibility;
- uncertainty;
- clinical relevance.
Level 3 — Knowledge Evolution
What has changed since the previous assessment?
This is the question that distinguishes aggregate reporting from routine pharmacovigilance.
The reviewer evaluates whether cumulative knowledge has evolved.
Level 4 — Regulatory Action
Does the new understanding require action?
Possible consequences include:
- product information updates;
- RMP revisions;
- PASS;
- additional pharmacovigilance activities;
- regulatory submissions.
The Regulatory Chain of Reasoning
Every conclusion within an aggregate report should be traceable through a logical chain of scientific reasoning.
Individual Cases
↓
Cumulative Data
↓
Signal Detection
↓
Signal Evaluation
↓
Risk Evaluation
↓
Integrated Benefit-Risk Evaluation
↓
Overall Conclusion
↓
Regulatory Actions
↓
Product Information
↓
Risk Management
No regulatory action should exist without supporting scientific evidence.
Likewise, every important scientific conclusion should be traceable back to objective data.