EMA recorded 87 deficiencies during CHMP-requested pharmacovigilance inspections in 2024, including four PSUR-related findings. Three of those PSUR findings were graded major, showing why periodic reporting controls matter. In 2026, aggregate reporting in pharmacovigilance remains central to lifecycle benefit-risk oversight. Therefore, teams must understand PSUR, PBRER, and DSUR requirements, data lock points, and submission timelines. Strong reporting also helps teams prepare for regulatory review and pharmacovigilance inspections.
Table of Contents
What Is Aggregate Reporting in Pharmacovigilance?
Aggregate reporting in pharmacovigilance brings cumulative safety data into one structured periodic review. Teams assess adverse events, patient exposure, emerging signals, and benefit-risk information from multiple sources. Therefore, the process helps companies identify changing safety patterns that individual case reports may not reveal. It also supports regulatory communication throughout the product lifecycle. By combining clinical, post-marketing, literature, and regulatory data, aggregate reports give authorities a broader view of a medicine’s evolving safety profile.
Why Can Aggregate Reporting Become an Inspection Risk?
Aggregate reporting can become an inspection risk when teams miss timelines, use incomplete datasets, or fail to reconcile safety information across systems. Weak documentation can also make benefit-risk conclusions difficult to defend. Therefore, regulators may question whether the company maintains effective oversight of its pharmacovigilance obligations. In addition, missed submissions or unsupported conclusions can trigger compliance findings. Strong governance, clear responsibilities, and documented reconciliation help reduce these risks.
The Aggregate Reporting Control Chain: From Data Cutoff to Regulatory Decision
Effective aggregate reporting depends on a controlled process that connects the data cutoff with the final regulatory submission. Teams must collect complete safety data, reconcile information across sources, assess signals, and document benefit-risk conclusions. Therefore, weaknesses at one stage can affect the accuracy of the entire report. Strong controls also help teams meet reporting timelines and provide regulators with clear, traceable evidence for safety decisions.
The following four areas show where teams should strengthen controls across PSUR, PBRER, and DSUR preparation:
- Control PSUR Timing Before Report Writing Starts (Available PDF)
- Build the PBRER Around Evidence, Not a Template (Available PDF)
- Keep DSUR Safety Review Connected to the Development Programme (Available PDF)
- Prevent Repeat Reporting Failures Before Inspection (Available PDF)
The infographic shows how the aggregate reporting control chain moves from the data lock point through reconciliation, signal review, benefit-risk assessment, and regulatory submission.
Control PSUR Timing Before Report Writing Starts (Available PDF)
PSUR preparation depends on correct data lock points, reporting frequency, and regulatory submission deadlines. Confirming these requirements early helps teams avoid incomplete reporting periods and late submissions.
Build the PBRER Around Evidence, Not a Template (Available PDF)
A PBRER should integrate cumulative safety, exposure, efficacy, signals, and benefit-risk evidence. Its conclusions should reflect the available data and uncertainties rather than simply follow a fixed reporting template.
Download PERIODIC BENEFIT-RISK EVALUATION REPORT (PBRER) E2C(R2) Here
Keep DSUR Safety Review Connected to the Development Programme (Available PDF)
A DSUR evaluates emerging safety information across the entire clinical development programme. It links cumulative exposure, safety findings, important risks, and regulatory actions with ongoing development decisions.
Prevent Repeat Reporting Failures Before Inspection (Available PDF)
Repeated reporting failures can indicate weaknesses in oversight, CAPA, reconciliation, or compliance monitoring. Strong corrective actions and documented follow-up help prevent the same deficiencies from appearing during future inspections.
Download Pharmacovigilance Inspection Metrics Report April 2020 – March 2021 Here
Which Aggregate Report Applies at Each Lifecycle Stage?
The correct aggregate report depends on where the product sits in its lifecycle and which regulatory framework applies. DSURs mainly support safety oversight during clinical development, while PSURs and PBRERs evaluate cumulative information after marketing approval. However, the boundaries can overlap when clinical development continues after approval. In the EU, the term PSUR remains the legal terminology, while its format and content are based on the ICH PBRER framework.
The table shows how PSUR, PBRER, and DSUR differ by purpose, lifecycle stage, data cutoff, submission timing, analytical focus, and regulatory responsibility.
| Report | Regulatory Purpose | Lifecycle Stage | Data Cutoff | Submission Timing | Analytical Focus | Accountable Organisation |
|---|---|---|---|---|---|---|
|
PSUR |
Periodically reassess whether the benefit-risk balance of an authorised medicine has changed. |
Post-authorisation; required according to applicable EU requirements and the EURD list. |
DLP follows the applicable EU reference date and reporting schedule or other regulatory requirement. |
70 days after DLP for intervals up to 12 months; 90 days for intervals over 12 months. |
New and cumulative safety information, exposure, signals, risks, benefits, and overall benefit-risk balance. |
Marketing Authorisation Holder (MAH). (European Medicines Agency (EMA))
|
|
PBRER |
Provide a harmonised periodic and critical evaluation of a marketed product’s evolving benefit-risk profile. |
Post-approval, including approved medicines that remain under further study. |
DLP is generally harmonised around the International Birth Date (IBD), the first marketing approval worldwide. |
ICH recommends 70 days for 6- or 12-month intervals and 90 days for intervals longer than 12 months. Regional rules may differ. |
Cumulative safety and exposure, signals, efficacy/effectiveness, risk evaluation, benefit evaluation, and integrated benefit-risk analysis. |
Marketing Authorisation Holder (MAH); responsibilities between partners should be documented. (ICH Database)
|
|
DSUR |
Provide regulators with an annual review of the safety of an investigational drug across its development programme. |
Clinical development; it can continue alongside post-marketing reporting when studies continue after approval. |
Annual period based on the Development International Birth Date (DIBD); DLP is normally the last day of that one-year period. |
No later than 60 calendar days after the DLP. |
Cumulative clinical-trial exposure, serious adverse events, emerging risks, important safety findings, regulatory actions, and implications for development. |
Clinical trial sponsor, even if report preparation is delegated to another party. (ICH Database)
|
The infographic shows how PSUR, PBRER, and DSUR address different regulatory questions while connecting development safety with post-marketing benefit-risk evaluation.
What Must Be Reconciled Before Final Sign-Off?
Before final sign-off, teams should confirm that all major safety sources, exposure data, signal assessments, and regulatory assumptions agree. They should also reconcile case data, literature findings, clinical information, previous commitments, and reporting timelines. Therefore, any mismatch should be investigated and documented before approval. A structured reconciliation process helps prevent omissions, inconsistent conclusions, and avoidable inspection findings in aggregate safety reports.
Final Words
Recent EMA inspection data show that 29 major findings, representing 33.33% of all findings, were recorded during CHMP-requested human pharmacovigilance inspections in 2024. This trend shows that regulators continue to test whether safety systems remain controlled, traceable, and reliable. Therefore, aggregate reporting in pharmacovigilance should function as an ongoing quality process rather than a periodic writing exercise. Strong reconciliation, clear benefit-risk reasoning, and timely submissions help teams demonstrate control when inspectors examine the system.
Quality Management System
We work with pharmaceutical teams to design, implement, and run effective Quality Management Systems, covering change control, CAPA, deviations, and audits to support consistent GMP compliance.
FAQ
Inspectors may check whether PSUR data are complete, traceable, reconciled, and consistent with safety databases, signals, exposure estimates, and benefit-risk conclusions. They may also examine submission compliance, governance, and documented quality controls.
Unresolved differences can lead to missing cases, inconsistent safety conclusions, or inspection findings. Therefore, teams should investigate, justify, and document material discrepancies before final approval.
ICH E2F requires the DSUR to be submitted no later than 60 calendar days after the data lock point. The report should cover the annual development period based on the Development International Birth Date.
References
Marco Klinger is Head of Quality Services at Zamann Pharma Support, where he leads consulting teams through complex regulatory and quality-driven projects. He brings more than 15 years of hands-on compliance experience across regulated industries. His work includes close collaboration with companies such as Reckitt, Sanofi, Biotech, Biotest, and others. Marco has deep expertise in medical device development, aseptic manufacturing, and the design, implementation, and management of complete quality management systems within GMP-regulated environments.