Understanding SUSARs and Their Reporting Requirements in Clinical Trials

Introduction: Why SUSARs Matter in Clinical Trials

In global clinical research, adverse event (AE) reporting is central to ensuring participant safety and regulatory compliance. Among the categories of AEs, one of the most critical is the Suspected Unexpected Serious Adverse Reaction (SUSAR). Regulatory authorities such as the FDA, EMA, MHRA, and global ICH guidelines require sponsors and investigators to identify and report SUSARs within strict timelines. Mismanagement of SUSAR reporting can result in delayed safety communication, missed signals, regulatory penalties, and even trial suspension.

Unlike standard AEs or serious adverse events (SAEs), SUSARs are both serious and unexpected, with a suspected causal relationship to the investigational product (IP). This dual classification makes them high-priority for expedited reporting to regulators, ethics committees, and investigators. This tutorial provides an in-depth guide on what constitutes a SUSAR, how to identify it, and when to report it, supported by case studies, regulatory guidance, and best practices.

Defining a SUSAR: Breaking Down the Components

A SUSAR is defined by three key criteria:

• Serious: The event meets seriousness criteria such as death, life-threatening outcome, hospitalization, disability, congenital anomaly, or other medically important conditions.
• Unexpected: The event is not consistent with the known safety profile of the IP, as outlined in the Investigator’s Brochure (IB) or product label (SmPC/PI).
• Suspected: There is a reasonable possibility that the IP caused the event, determined by causality assessment from the investigator or sponsor.

For example, if a participant in an oncology trial experiences a myocardial infarction that is not described in the IB and is assessed as possibly related to the study drug, the case qualifies as a SUSAR.

When to Report a SUSAR: Regulatory Requirements

Authorities enforce expedited reporting timelines for SUSARs:

• Fatal or life-threatening SUSARs: Must be reported within 7 calendar days of awareness, with follow-up information within 8 days.
• Other SUSARs: Must be reported within 15 calendar days of awareness.

For instance, under ICH E2A, sponsors are required to ensure expedited communication of SUSARs across all participating sites and regulatory authorities. The EU Clinical Trial Regulation (EU-CTR) enforces similar requirements via EudraVigilance, while the FDA requires IND safety reports containing SUSARs to be submitted electronically.

The rationale behind expedited timelines is to ensure rapid communication of emerging risks, enabling ethics committees and regulators to evaluate whether trial continuation remains safe for participants.

Case Study: Identifying a SUSAR in Practice

Consider a Phase II cardiovascular trial where a participant developed acute pancreatitis. The event was serious due to hospitalization. It was unexpected, as pancreatitis was not listed in the IB. Investigators suspected a causal relationship because the event occurred soon after drug administration and no alternative explanation was evident. The sponsor classified the event as a SUSAR and reported it to regulators within 7 days. This ensured compliance and demonstrated vigilance in patient safety monitoring.

Distinguishing SUSARs from SAEs and AESIs

One of the common challenges investigators face is differentiating SUSARs from other categories:

• SAE (Serious Adverse Event): Serious but not necessarily unexpected or related to the IP.
• AESI (Adverse Event of Special Interest): May not meet seriousness criteria but is of special concern for the IP class (e.g., QT prolongation for antiarrhythmic drugs).
• SUSAR: Must be serious, unexpected, and suspected to be related to the IP.

Understanding these distinctions ensures appropriate prioritization and timely regulatory reporting.

Global Regulatory Framework for SUSAR Reporting

Different regions maintain harmonized but distinct frameworks:

• FDA (US): Requires IND safety reports including SUSARs, submitted via the electronic gateway.
• EMA (EU): Mandates submission through EudraVigilance.
• MHRA (UK): Requires SUSARs to be reported through its MHRA safety portal.
• DCGI/CTRI (India): Mandates submission of SUSARs to the regulator and registration in CTRI systems.
• PMDA (Japan): Requires adherence to ICH guidelines with country-specific forms.

Despite broad harmonization under ICH, country-specific nuances mean sponsors must establish region-specific SOPs to remain compliant.

Challenges in Identifying and Reporting SUSARs

Practical challenges include:

• Unclear causality: Investigators may hesitate to classify an event as related without strong evidence, risking delays.
• Complex multi-country trials: Reconciling timelines across regions increases administrative burden.
• Incomplete data: Early reports may lack laboratory or imaging confirmation, requiring follow-up updates.
• System limitations: Inadequate eCRF design may fail to flag potential SUSARs promptly.

For example, in a large oncology program, multiple SAEs were initially misclassified as expected due to inadequate cross-checks with the IB. A sponsor audit revealed the gaps, leading to a corrective action plan with retraining and improved eCRF prompts.

Best Practices for SUSAR Identification and Reporting

Sponsors and investigators can adopt several strategies to strengthen SUSAR reporting:

• Provide training modules for investigators on distinguishing SUSARs from SAEs and AESIs.
• Embed real-time edit checks in eCRFs to flag potential SUSARs for sponsor review.
• Develop SOPs specifying timelines, responsibilities, and escalation pathways.
• Maintain a centralized pharmacovigilance team to review and confirm SUSAR classification.
• Reconcile SUSAR data across pharmacovigilance systems and regulatory submissions regularly.

For example, in a Phase III immunology trial, implementation of a centralized safety review committee reduced SUSAR misclassification by 35% and improved regulatory compliance.

Regulatory Implications of Poor SUSAR Reporting

Failure to identify and report SUSARs accurately can have significant consequences:

• Inspection findings: Regulators may cite major or critical deficiencies during inspections.
• Delayed submissions: Late SUSAR reporting can delay trial continuation or approvals.
• Patient safety risks: Failure to detect emerging risks undermines ethical oversight.
• Reputation damage: Sponsors with repeated SUSAR deficiencies may face stricter regulatory scrutiny.

Ensuring timely and accurate SUSAR reporting is therefore both a compliance obligation and a patient safety imperative.

Key Takeaways

SUSARs represent one of the most critical categories of safety reporting in clinical trials. To ensure compliance and patient safety, sponsors and investigators should:

• Understand the criteria that define a SUSAR (serious, unexpected, suspected).
• Report SUSARs within regulatory timelines (7 or 15 days).
• Document causality rationale and reconcile data across systems.
• Adopt SOPs, training, and centralized reviews to minimize misclassification.

By applying these practices, trial teams can improve regulatory compliance, enhance pharmacovigilance, and most importantly, protect participants enrolled in clinical research.

Understanding the Difference Between SAEs and SUSARs in Clinical Trials

Defining SAE and SUSAR

Serious Adverse Events (SAEs) and Suspected Unexpected Serious Adverse Reactions (SUSARs) are fundamental categories in clinical trial safety reporting. While both represent critical safety events, their definitions and reporting obligations differ.

An SAE is any untoward medical occurrence that at any dose results in death, is life-threatening, requires inpatient hospitalization or prolongation of existing hospitalization, results in disability/incapacity, or causes a congenital anomaly. Additionally, “important medical events” that may not meet these criteria but require medical intervention can also qualify as SAEs.

A SUSAR goes one step further. It is an SAE that is also suspected to be related to the investigational product and unexpected based on the current Investigator’s Brochure (IB) or approved labeling. In other words, SUSAR = Serious + Related + Unexpected. This three-part test is crucial in pharmacovigilance and is the driver of expedited reporting obligations.

While SAEs are always documented, not all SAEs become SUSARs. For example, a hospitalization due to disease progression in oncology may be an SAE but not a SUSAR because it is expected and unrelated. Conversely, a novel immune-mediated toxicity not listed in the IB could qualify as a SUSAR if related and serious.

Regulatory Framework for SAE vs SUSAR

Global regulators provide aligned but locally adapted rules:

• FDA (21 CFR 312.32): SUSARs require expedited reporting: 7 days for fatal/life-threatening cases, 15 days for others. SAEs are reported in IND annual safety updates if not expedited.
• EMA (EudraLex Volume 10, CTR 536/2014): Requires expedited reporting of SUSARs via EudraVigilance. All other SAEs are documented in trial safety reports.
• MHRA (UK): Aligns with EMA but requires local pharmacovigilance compliance under post-Brexit rules.
• CDSCO (India): Investigators must notify SAEs within 24 hours; sponsors submit causality analysis. SUSARs trigger expedited reporting with review by Ethics Committees and Expert Committees.

In all regions, expedited reporting applies only to SUSARs, not all SAEs. This ensures regulatory focus on unexpected, potentially new risks while avoiding unnecessary signal inflation from expected toxicities.

Case Examples: SAE vs SUSAR

Case-based analysis is the best way to illustrate the differences:

• Case 1: Patient on cisplatin develops nephrotoxicity requiring hospitalization. This is an SAE (serious, hospitalization, related) but expected (nephrotoxicity listed in IB). Classification: SAE, not SUSAR.
• Case 2: Patient on checkpoint inhibitor develops myocarditis requiring ICU admission. This is serious, related, and not described in IB. Classification: SUSAR → expedited 7-day report.
• Case 3: Patient with lung cancer dies due to tumor progression. Serious outcome (death), but not related to drug. Classification: SAE, not SUSAR.

These examples show that SAE classification is broader, while SUSARs are a regulatory subset demanding rapid notification.

Decision Tree: From SAE to SUSAR

The following decision tree helps investigators and sponsors classify events consistently:

1. Step 1: Is the event serious? (death, hospitalization, etc.) → If no, remain AE.
2. Step 2: Is it related to investigational product? → If no, remain SAE only.
3. Step 3: Is it unexpected vs IB/SmPC? → If yes, then SUSAR.

This three-step logic ensures that SUSARs are correctly identified and reported without overburdening systems with expected SAEs. To support decision-making, EDC systems should include mandatory fields for seriousness, causality, and expectedness, with edit checks to generate SUSAR triggers automatically.

Oncology-Specific Perspectives

Oncology trials provide frequent borderline cases between SAE and SUSAR. For example:

• Expected SAE: Febrile neutropenia requiring hospitalization with cisplatin (listed toxicity) → SAE, not SUSAR.
• Unexpected SAE → SUSAR: Autoimmune encephalitis in immunotherapy trial → not listed, serious, related → SUSAR.
• Disease progression: Tumor growth causing hospitalization → SAE but unrelated → not SUSAR.

These oncology examples highlight why accurate expectedness determination is critical. Sponsors must update the IB regularly to include emerging toxicities and prevent over-reporting SUSARs unnecessarily.

Documentation and Narrative Requirements

SUSARs require comprehensive narratives that include:

• Patient demographics and baseline risk factors.
• Dosing details (cycle, day, dose modifications).
• Chronology of AE onset, labs, imaging, interventions.
• Causality rationale from investigator and sponsor.
• Expectedness justification referencing IB/SmPC.
• Outcome and follow-up data.

SAE narratives must also be detailed but may not require expedited submission unless they meet SUSAR criteria. Regulators expect all SUSAR narratives to be consistent across CRF, EDC, and safety database entries.

Global Timelines for SUSAR Reporting

Expedited SUSAR reporting timelines differ slightly across regions but are broadly harmonized:

• Fatal/Life-threatening SUSARs: 7 calendar days from sponsor awareness (FDA, EMA, MHRA, CDSCO).
• Other SUSARs: 15 calendar days.
• SAEs not qualifying as SUSARs: Documented in periodic reports (DSUR, PSUR).

Sponsors must maintain a SUSAR line listing and reconciliation log to ensure timely submissions and avoid discrepancies. Many regulatory inspections focus on whether timelines were met and whether documentation demonstrates sponsor oversight.

Inspection Readiness: Common Issues

Frequent inspection findings include:

• Investigators confusing SAEs with SUSARs.
• Lack of justification for expectedness in narratives.
• Delayed expedited SUSAR submissions due to causality disagreements.
• Mismatches between safety database and CRF entries.

To avoid these, sponsors should implement SOPs that define SUSAR classification, train investigators with case-based exercises, and perform monthly reconciliation between clinical and safety data.

Key Takeaways for Professionals

Distinguishing between SAEs and SUSARs is vital for trial compliance and patient safety. Professionals should remember:

• All SUSARs are SAEs, but not all SAEs are SUSARs.
• SUSAR classification requires seriousness + relatedness + unexpectedness.
• Regulators mandate expedited reporting of SUSARs with strict timelines.
• Accurate expectedness assessment is critical, especially in oncology trials.
• Documentation and narrative alignment across systems is essential for inspection readiness.

By applying structured classification, robust documentation, and timely reporting, sponsors and investigators ensure compliance with FDA, EMA, MHRA, and CDSCO requirements while protecting patient safety worldwide.