How to Manage Unexpected SAEs in Ongoing Clinical Trials

Published on 21/12/2025

Effective Management of Unexpected SAEs in Ongoing Clinical Trials

Unexpected Serious Adverse Events (SAEs) can arise at any point during a clinical trial and often require immediate, coordinated, and compliant action by both investigators and sponsors. These unanticipated events not only pose risk to participant safety but also challenge the robustness of safety oversight and regulatory reporting processes. This guide offers a structured approach for identifying, assessing, and managing unexpected SAEs during ongoing trials in compliance with USFDA, EMA, and ICH E2A guidelines.

Table of Contents

What Constitutes an Unexpected SAE?

According to ICH guidelines, an SAE is considered unexpected if its nature or severity is not consistent with the applicable product information, such as the Investigator Brochure (IB) or Summary of Product Characteristics (SmPC). This includes:

New adverse reactions not previously reported
Known adverse reactions with increased severity
SAEs occurring in new populations (e.g., pediatrics)

For example, if a trial for a new anti-diabetic agent results in cases of unexpected myocardial infarctions, such events must be urgently reviewed and classified for regulatory action.

Identifying Unexpected SAEs:

Site staff are usually the first to observe and document unexpected events. Their responsibilities include:

Completing SAE forms within 24 hours of awareness
Documenting

medical history, concomitant medications, and clinical course

Providing discharge summaries, test results, and physician notes

The sponsor or designee must then evaluate whether the event is truly unexpected based on available safety data.

Initial Assessment and Classification:

Verify seriousness: Does the event meet ICH SAE criteria?
Assess causality: Relatedness to the Investigational Product (IP)
Determine expectedness: Refer to IB or SmPC
Evaluate whether it qualifies as a SUSAR (Suspected Unexpected Serious Adverse Reaction)

If classified as a SUSAR, it triggers expedited reporting timelines and global regulatory action.

Regulatory Reporting Timelines:

SAE Classification	Timeline	Regulatory Body
Fatal or Life-threatening SUSAR	7 calendar days	CDSCO, EMA, USFDA
Other SUSARs	15 calendar days	All regions
Expected SAEs	Periodic reports (e.g., DSUR)	All regions

Each regulatory body requires different formats—such as E2B XML, CIOMS forms, or online portal entries.

Immediate Actions for Unexpected SAE Management:

1. Rapid Internal Communication

Notify medical monitor within 12 hours of receipt
Trigger safety review team meeting (telecon or email chain)
Initiate unblinding if warranted and predefined in the protocol

2. Data Entry and Documentation

Use validated safety databases for SAE tracking. Required data fields include:

Event term and seriousness criteria
Causality assessment (investigator and sponsor)
Expectedness evaluation outcome
Narrative summary and coding using MedDRA

Support systems like StabilityStudies.in can help maintain version-controlled documentation for audit readiness.

3. Reporting to Authorities

Follow country-specific guidelines:

India: Submit Form SAE-1 with IEC approval and sponsor’s causality assessment to CDSCO
EU: Use EudraVigilance portal for SUSAR submission
USA: File IND safety report via Form FDA 3500A

Investigator Responsibilities in Ongoing Trials:

Report any unexpected SAE immediately to sponsor and EC
Provide updated SAE documentation upon follow-up
Document discussion in source notes and CRFs
Maintain compliance with trial-specific safety reporting timelines

Refer to Pharma SOP documentation for templates on SAE management workflows at site level.

Global Harmonization and Escalation Strategy:

Multinational trials must harmonize safety communication:

Centralize safety signal management at sponsor HQ
Local affiliates to handle region-specific submissions
Use escalation protocols to alert QA, Regulatory, and Medical teams

Safety Signal Management and Follow-Up:

Unexpected SAEs may signal a larger risk profile. Sponsors must:

Perform cumulative data analysis for emerging trends
Update Investigator Brochure and protocol if needed
Escalate to Data Monitoring Committee (DMC) for unblinded review

Best Practices for Managing Unexpected SAEs:

Maintain version-controlled safety management plans
Train sites regularly on SAE definitions and reporting timelines
Use validated safety databases with reconciliation tools
Implement a checklist for expedited reporting compliance
Document all safety-related decisions and communications

Audit and Inspection Readiness:

Ensure the following documents are readily available for regulatory inspection:

SAE forms and follow-up logs
Causality assessment records
Regulatory submission confirmations
Corrective and Preventive Action (CAPA) plans if deviations occurred

Use insights from GMP audit checklist to enhance readiness.

Conclusion:

Managing unexpected SAEs during ongoing trials requires preparedness, cross-functional coordination, and regulatory vigilance. By implementing a clear strategy that spans identification, documentation, classification, and reporting, sponsors and investigators can ensure participant safety and regulatory compliance across all trial regions.