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.