Aggregate Reporting · Section 8.12
~3 min read · The Drug Safety Coach — Global PV Career Course
Key points
Full text
This module traced the aggregate report from its structural reorientation under ICH E2C(R2) — PSUR to PBRER, safety summary to integrated benefit-risk evaluation — through the specific mechanics that make it possible to compile one at all: the data lock point that gives it a defined boundary, and the imperfect but necessary exposure estimation that gives its case counts actual meaning. From there it worked through how findings get synthesised into the report’s narrative sections, and how everything converges into the benefit-risk analysis that’s the document’s entire reason for existing in its current form.
The DSUR comparison placed the PBRER in its proper context — one stage in a product’s continuous safety-monitoring lifecycle, not an isolated report type — while regional variation and common quality findings grounded the module in the practical reality that harmonisation is real but incomplete, and that a defensible report requires rigor at every supporting section, not just eloquence in the final conclusion.
Key references: ICH E2C(R2) (Periodic Benefit-Risk Evaluation Report), ICH E2F (Development Safety Update Report), GVP Module VII (Periodic Safety Update Report), CIOMS Working Group XIV Final Report.
Key Concept
"An aggregate report is only as honest as its weakest supporting section. You can write a beautifully argued benefit-risk conclusion on top of a sloppy exposure estimate and inconsistent data tabulations — and it will still be wrong. The discipline runs through the whole document, not just the paragraph regulators actually quote." — Vinay Kumar
Quick check
Test yourself before moving on — no pressure, just click an answer.
1. Why does this module’s closing view describe the benefit-risk analysis as only as strong as its supporting sections?