Understanding Global Variability in SUSAR Definitions

Introduction: Why SUSAR Definitions Differ Across the Globe

Suspected Unexpected Serious Adverse Reactions (SUSARs) are a cornerstone of pharmacovigilance in clinical trials. Yet, despite harmonization attempts under ICH E2A and CIOMS, definitions and interpretations of SUSARs vary significantly across regulatory regions. This variability creates complexity for sponsors conducting multinational trials, where a single adverse event may be classified differently depending on the jurisdiction. Misclassification or inconsistent reporting can result in inspection findings, delayed approvals, or regulatory sanctions.

Understanding global differences is essential for compliance and efficient trial management. This tutorial explores how various authorities define SUSARs, the implications of variability, challenges faced by sponsors, case study examples, and best practices for harmonizing approaches across regions.

Core Elements of a SUSAR Definition

While terminology varies, most regulators agree on three defining criteria for a SUSAR:

• Serious: The event results in death, is life-threatening, requires hospitalization, causes disability, or is otherwise medically important.
• Unexpected: The nature or severity of the event is not consistent with the known safety profile in the Investigator’s Brochure (IB) or Summary of Product Characteristics (SmPC).
• Suspected relationship: A reasonable possibility exists that the investigational product (IP) caused the event.

Despite this common framework, interpretation of “unexpected” and “suspected” differs globally, leading to divergent reporting obligations.

Regional Regulatory Perspectives on SUSARs

Examples of differences across major regulatory regions include:

• FDA (US): Focuses on “reasonable possibility” of causality. Requires expedited reporting of any unexpected serious suspected adverse reaction, whether observed domestically or abroad, within 7 or 15 days.
• EMA (EU): Defines SUSARs with emphasis on comparison to the Reference Safety Information (RSI) in the IB. Requires electronic submission via EudraVigilance.
• MHRA (UK): Aligns with EU principles but requires parallel submissions to Research Ethics Committees.
• PMDA (Japan): Requires detailed causality justification and case narratives; timelines generally align with ICH but involve country-specific templates.
• DCGI (India): Requires SUSAR reporting to both regulators and institutional ethics committees, often within 14 days.
• Health Canada: Requires immediate notification of fatal/life-threatening SUSARs, with less prescriptive causality language compared to EMA.

These differences illustrate how a case classified as “serious unexpected adverse reaction” in the EU may not meet SUSAR criteria in the US, complicating global trial safety oversight.

Case Studies Illustrating Variability

Case Study 1 – Oncology Trial: A Grade 3 neutropenia case was classified as a SUSAR in the EU (not listed in RSI) but not in the US (considered within expected chemotherapy risks). Sponsors reconciled by reporting to both but annotating the classification difference in submissions.

Case Study 2 – Vaccine Trial: Myocarditis events were expedited as SUSARs in the EU but reported as “unanticipated problems” in the US. Ethics committees required plain-language summaries, adding to workload.

Case Study 3 – Cardiovascular Device Trial: Device-related adverse events overlapped with SUSAR reporting rules inconsistently across EU and Asian regions, requiring sponsor SOP adjustments.

Challenges Arising from Global Variability

Sponsors managing international trials face challenges including:

• Operational burden: Different forms, timelines, and submission portals across jurisdictions.
• Inconsistent causality judgments: What one authority deems “related” another may not.
• Database complexity: Reconciling definitions across pharmacovigilance and clinical data management systems.
• Inspection readiness: Regulators expect consistent justification for handling SUSARs across multiple regions.

These challenges are compounded in large-scale oncology or vaccine programs where SUSAR volume is high and reporting windows are short.

Best Practices for Managing SUSAR Variability

To manage differences across jurisdictions, sponsors should implement best practices such as:

• Develop global SOPs with annexes for country-specific SUSAR requirements.
• Use centralized pharmacovigilance databases that flag discrepancies in classification.
• Maintain dual reporting strategies where regulatory definitions diverge.
• Provide training modules for investigators on regional differences in SUSAR definitions.
• Engage regulatory intelligence teams to track evolving requirements in real time.

For example, a sponsor running a global oncology trial created a harmonized template that included FDA, EMA, and MHRA criteria side-by-side, helping investigators classify SUSARs consistently across sites.

Regulatory Implications of Poor Harmonization

Failure to address variability in SUSAR definitions can lead to:

• Regulatory findings: Authorities may cite sponsors for inconsistent or delayed SUSAR reporting.
• Increased risk to participants: Delayed recognition of emerging safety issues undermines trial oversight.
• Operational inefficiency: Redundant or conflicting submissions increase workload and costs.
• Delayed approvals: Authorities may withhold trial continuation or marketing authorizations pending safety clarification.

Key Takeaways

SUSAR definitions are broadly aligned across regulators but differ in interpretation and operational application. To ensure compliance in global trials, sponsors must:

• Understand regional differences in SUSAR criteria and timelines.
• Adopt global SOPs that integrate country-specific nuances.
• Reconcile classification discrepancies across systems and submissions.
• Train investigators and pharmacovigilance staff on variable definitions.

By proactively managing variability, trial teams can ensure accurate and timely SUSAR reporting worldwide, strengthen pharmacovigilance, and protect participants across jurisdictions.

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.