Aggregate Reporting in Pharmacovigilance: 10 Things You Should Know

Aggregate reports are more than scheduled summaries of adverse event data. They bring safety, exposure and benefit information together to support decisions about a medicine’s evolving benefit-risk profile.

For heads of pharmacovigilance, QPPVs and regulatory affairs leaders, the challenge is to produce reports that are timely, consistent across regions and useful for action. Here are 10 practical points to keep in view.

1. Aggregate reports support decisions across a product’s lifecycle

A PSUR or PBRER evaluates safety information at defined intervals after marketing authorisation. It places new findings in the context of cumulative evidence, exposure and, where relevant, efficacy or effectiveness.

A DSUR has a different purpose: it reviews safety information for a drug under clinical development. If development continues after a product is marketed, both DSUR and post-authorisation reporting obligations may apply.

Practical takeaway: Maintain a reporting map by product, indication, development status and market. Don’t assume that one report replaces another across jurisdictions.

2. PSUR and PBRER are related, but not identical terms

The ICH E2C(R2) PBRER format puts explicit emphasis on evaluating benefits alongside risks. In India, the 2024 Pharmacovigilance Guidance Document for Marketing Authorization Holders says PSURs may be prepared in Schedule Y format or as an ICH E2C(R2) PBRER.

The format and local requirements still matter. The ICH guideline notes that reporting frequency is subject to national or regional rules, which may differ between markets.

Practical takeaway: Confirm the accepted format, scope and schedule for each product and authority. Use the ICH E2C(R2) guideline as a reference for PBRER content, alongside applicable local requirements.

3. India’s PSUR schedule has defined clocks

Under the CDSCO/PvPI guidance, PSURs for new drugs are submitted every six months for the first two years after approval, then annually for the subsequent two years. The Licensing Authority may extend the total reporting period when considered necessary in the interest of public health.

The report is due within 30 calendar days after the last day of the reporting period. The guidance says PSURs should be submitted online through the SUGAM portal. Check the product-specific due dates shown in SUGAM as well as internal trackers.

These requirements apply in the context of the rules for new drugs; they should not be treated as a universal PSUR schedule for every product in India.

Practical takeaway: Assign an accountable owner for each reporting date, and build in time for data reconciliation, review and submission checks.

4. A good report depends on a reliable data cut

The data lock point (DLP) defines the cut-off for information included in a report. A clear DLP helps teams reconcile cases, exposure estimates, literature, clinical studies and safety actions across functions and partners.

ICH E2C(R2) sets a general interval of 70 calendar days after the DLP for six- or 12-month PBRERs, and 90 days for reports covering more than 12 months. These are ICH recommendations; regional requirements may differ. The ICH E2F DSUR guideline specifies a 60-calendar-day submission interval after the DSUR DLP.

Practical takeaway: Maintain one global safety calendar, but configure the submission clock by report type and jurisdiction. Reconcile the final dataset to the same DLP before authoring begins.

5. Exposure data help put case counts in context

A count of reports alone cannot describe how frequently an event occurs. Where data allow, aggregate reporting should set cases alongside an estimate of patient exposure, explain how the estimate was calculated and identify its limitations.

For a PBRER, the ICH guidance describes presenting exposure information such as patient numbers, patient-time or, where necessary, other suitable measures. Subgroup estimates can help where a signal relates to a particular age group, indication, dose or region.

Practical takeaway: Agree exposure definitions with commercial, epidemiology and data teams before the reporting cycle. Document assumptions, sources and method changes so trends can be interpreted consistently.

6. Signal management should be visible in the report

An aggregate report should show how new, ongoing and closed signals were handled. A statistical finding is not, by itself, a validated signal; clinical assessment and scientific interpretation are needed.

The ICH PBRER format includes a signal overview and evaluation, with attention to source, key evidence, status and actions. The report should connect the evaluation to decisions such as further investigation, changes to product information or risk minimisation.

Practical takeaway: Keep a traceable record of each signal’s detection date, validation, assessment, decision owner, conclusion and follow-up. The EMA GVP Module IX on signal management provides additional process guidance.

7. Link emerging risks to the risk management plan

A risk management plan (RMP) is not a static attachment. In India’s MAH guidance, the RMP is described as a dynamic document, updated through the product lifecycle. It records safety concerns, planned pharmacovigilance activities and risk-minimisation measures.

Aggregate report findings can indicate that a safety concern needs further characterisation or that an existing measure should be reviewed. The report’s conclusion should explain whether product information, monitoring activities or risk controls require action.

Practical takeaway: Compare the report’s conclusions against the current RMP and open commitments. Record whether each action is complete, ongoing, proposed or not required, and why.

8. Inspection readiness includes the reporting process

In the EU, GVP Module III Revision 2 took effect on 10 September 2026. It strengthens the risk-based approach to inspection planning and reflects updated legal provisions on subcontracted pharmacovigilance activities. Inspectors may examine PSUR completeness, data accuracy, signal evaluation, submission timeliness, RMP implementation and relevant agreements.

The amended rules also make subcontractor oversight particularly important. The MAH remains responsible for meeting its obligations, even when work is delegated.

Practical takeaway: Keep the evidence behind each report easy to retrieve: source datasets, reconciliation records, review comments, approvals, submission receipts and partner responsibilities. See the EMA GVP page for current modules and documents.

9. Track reporting-system changes separately from aggregate-report deadlines

From 1 October 2026, postmarketing ICSRs for specified human drugs, biological products and combination products submitted to FDA through ESG NextGen must use E2B(R3). This is an individual case submission requirement, not a new PBRER or PSUR deadline. FDA says submissions through the Safety Reporting Portal are not affected by this specific ESG NextGen requirement.

In India, the latest PvPI profile located reports 1,075 ADR Monitoring Centres as of September 2025. On 21 September 2026, the Indian Pharmacopoeia Commission announced the iOS version of the ADR-PvPI 2.0 app, with reporting features covering drugs, vaccines and medical devices. These developments add to the reporting landscape, but do not replace an MAH’s own regulatory reporting responsibilities.

Practical takeaway: Maintain separate change controls for aggregate reporting and ICSR transmission. Check the FDA’s AEMS electronic submissions page and the IPC ADR-PvPI 2.0 announcement for details.

10. Treat the report as a governance deliverable

A report can meet its submission date and still fail to support a clear decision if its evidence is fragmented or its conclusions are hard to follow. Senior review should test whether the report explains what changed, how the benefit-risk profile was assessed and what action follows.

This requires coordination among PV, regulatory affairs, clinical safety, epidemiology, medical, quality and external partners. Clear roles and timely escalation matter, particularly when a report identifies a potential impact on product information or an RMP commitment.

Practical takeaway: Before approval, ask reviewers to check three things: the data are reconciled; the interpretation is supported; and every proposed action has an owner and due date.

Discuss aggregate reporting with PV leaders in Chennai

These issues (reporting timelines, signal assessment, RMP alignment and inspection readiness) are practical operational questions for senior safety teams across India, Europe and the USA.

Pharmacovigilance India 2027 is a one-day conference in Chennai on 29 July 2027. Its draft programme includes sessions on signal management, inspection readiness, PvPI and CDSCO, and operational delivery. The event is designed for senior PV decision-makers, including heads of safety, QPPVs and regulatory leaders.