Published on 23/12/2025
Understanding the Differences Between DSUR and SUSAR Reporting
Introduction: Why Both DSUR and SUSAR Reporting Matter
In clinical research, Drug Safety Update Reports (DSURs) and Suspected Unexpected Serious Adverse Reaction (SUSAR) reports are critical tools for communicating safety information. Both serve different but complementary functions: SUSARs ensure rapid notification of serious safety concerns, while DSURs provide regulators with an aggregate, annual overview of the evolving safety profile of an investigational product. Together, these reporting requirements form the foundation of global pharmacovigilance, enabling regulators to assess both immediate risks and long-term trends.
The ICH E2A guideline governs expedited SUSAR reporting, whereas ICH E2F provides the framework for DSUR preparation. Misunderstanding the differences between the two can result in duplicate reporting, compliance gaps, or inspection findings. This article provides a structured comparison of SUSAR and DSUR requirements, including timelines, content, case studies, challenges, and best practices for compliance.
Defining SUSAR Reporting
SUSARs are adverse events that meet three criteria: serious, unexpected, and suspected to be related to the investigational product. Regulatory authorities require expedited submission to ensure rapid signal detection. Key aspects include:
- Timeline: Fatal or life-threatening SUSARs must be reported within 7 days; other SUSARs within 15 days.
- Format: Typically
For example, in an oncology trial, a case of unexpected fatal neutropenic sepsis would qualify as a SUSAR requiring expedited submission within 7 days to EMA via EudraVigilance.
Defining DSUR Reporting
DSURs are comprehensive annual reports summarizing cumulative safety information from all ongoing clinical trials involving an investigational product. Features include:
- Content: Safety overview, cumulative SUSAR data, aggregate AE/SAE analyses, risk–benefit evaluation, and actions taken.
- Frequency: Typically submitted annually, with a data lock point (DLP) based on the sponsor’s development program.
- Recipients: Primarily regulators (FDA, EMA, MHRA, PMDA, etc.), not ethics committees.
- Format: Structured according to ICH E2F requirements, often integrated with Periodic Benefit–Risk Evaluation Reports (PBRERs).
For instance, a DSUR for an immunotherapy program would summarize cumulative immune-mediated adverse events across Phase I–III trials, contextualized with benefit–risk analysis.
Case Studies Highlighting Differences
Case Study 1 – Oncology Trial: A SUSAR of unexpected pulmonary embolism was submitted within 15 days under E2A. In the DSUR, the sponsor summarized all thromboembolic events observed during the reporting year, analyzing frequency, severity, and relationship to treatment.
Case Study 2 – Vaccine Development: Multiple myocarditis SUSARs were submitted within expedited timelines. The DSUR later included a cumulative review of myocarditis risk, supported by subgroup analysis by age and sex.
Case Study 3 – Multinational Cardiovascular Program: SUSARs of arrhythmias were reported rapidly, while DSURs contextualized arrhythmia patterns across different doses and populations, supporting dose adjustments in later trials.
Key Differences Between DSUR and SUSAR Reporting
| Aspect | SUSAR Reporting | DSUR Reporting |
|---|---|---|
| Purpose | Rapid communication of new safety risks | Comprehensive review of cumulative safety data |
| Timeline | 7 or 15 days | Annually |
| Recipients | Regulators, ECs, investigators | Regulators only |
| Format | CIOMS / ICH E2B(R3) | ICH E2F (structured report) |
| Scope | Individual case reports | Aggregate program-wide data |
Challenges in Aligning DSUR and SUSAR Processes
Sponsors often struggle to reconcile SUSAR and DSUR workflows. Challenges include:
- Data reconciliation: Ensuring all SUSARs submitted during the year are reflected accurately in the DSUR.
- Consistency: Narratives in expedited reports may differ from aggregate analyses in DSURs.
- Resource intensity: Preparing DSURs requires significant cross-functional input (clinical, safety, biostatistics).
- Regulatory variability: While ICH E2F harmonized DSURs, some regions (e.g., US FDA) have specific modifications.
For example, during an MHRA inspection, discrepancies were identified between SUSAR counts in CIOMS forms and DSUR cumulative tables, leading to major findings.
Best Practices for Sponsors
To align SUSAR and DSUR reporting, sponsors should adopt best practices:
- Maintain a central safety database to reconcile expedited and periodic reporting.
- Develop SOPs integrating SUSAR and DSUR processes.
- Conduct regular reconciliation checks before DSUR submission.
- Train pharmacovigilance and clinical staff on differences between SUSAR and DSUR reporting.
- Leverage automation to generate cumulative tables and safety narratives for DSURs.
Regulatory Implications of Poor Differentiation
Inadequate differentiation or poor reconciliation between SUSAR and DSUR reports can lead to:
- Inspection findings: Regulators may cite sponsors for inconsistent reporting.
- Delayed trial approvals: Incomplete DSURs may delay authorization renewals.
- Safety signal gaps: Failure to integrate expedited and cumulative reporting undermines signal detection.
- Reputational risks: Regulatory confidence in sponsor safety systems may erode.
Key Takeaways
SUSARs and DSURs are complementary pillars of clinical trial safety reporting. While SUSARs provide rapid, case-level insights, DSURs deliver program-level, aggregate safety evaluation. Sponsors must:
- Understand the timelines and formats of both reporting systems.
- Ensure consistency between expedited SUSAR submissions and DSUR summaries.
- Implement cross-functional SOPs, reconciliation processes, and training programs.
By mastering both SUSAR and DSUR reporting, sponsors can maintain compliance, protect participants, and strengthen regulatory confidence in global clinical development programs.