patient ID, event term, causality)

Request additional documents (e.g., discharge summary, labs)

Determine if the SAE qualifies as a SUSAR

2. Causality and Expectedness Assessment:

Sponsors are responsible for reviewing the investigator’s causality assessment and classifying the event as:

• Related or unrelated to the investigational product
• Expected or unexpected based on the Investigator Brochure or product label

For unexpected, related SAEs (i.e., SUSARs), expedited reporting is required under ICH E2A.

3. Expedited Reporting Timelines:

SAE Type	Timeline	Applicable Regions
SUSAR – Fatal/Life-Threatening	Within 7 calendar days	USFDA, EMA, CDSCO, Health Canada
SUSAR – Other	Within 15 calendar days	All regions
SAE – Not Related or Expected	Include in DSUR	Periodic safety reports

4. Submitting to Regulatory Authorities:

Sponsors must use region-specific portals or formats to report SAEs:

• US: FDA’s IND Safety Reports (Form FDA 3500A)
• EU: EudraVigilance database via EVWEB
• India: CDSCO’s online SAE submission system
• Australia: TGA SAE submission via online forms
• Brazil: ANVISA reporting portal

Refer to templates and tools from Pharma SOPs to prepare accurate and validated safety submissions.

5. IRB and Ethics Committee Notification:

Sponsors must ensure that investigators notify the relevant EC/IRB within 7–15 days. In global trials, timelines may differ across countries and must be clearly outlined in the protocol and site-specific agreements.

6. Maintaining the SAE Database:

A validated pharmacovigilance database must be maintained that includes:

• All SAE entries (initial and follow-up)
• Event details, severity, outcome
• Relatedness, expectedness
• Reporter information
• Regulatory submission status

Tools like StabilityStudies.in can support automated SAE tracking, follow-up alerts, and log reconciliation.

7. Aggregate SAE Review and Signal Detection:

• Periodically analyze SAE data across sites and studies
• Conduct Data Monitoring Committee (DMC) reviews if applicable
• Evaluate trends for product safety signals
• Prepare Development Safety Update Reports (DSURs) annually

8. Sponsor Responsibilities in Multinational Trials:

In global studies, sponsors must coordinate reporting in compliance with all local regulations:

• Maintain master SAE tracker by country
• Translate documents where required
• Account for time zone differences in reporting windows
• Harmonize safety reporting with CRO partners and affiliates

Consult with regulatory specialists from Pharma Regulatory for country-specific SAE rules and escalation pathways.

9. Training and Oversight Obligations:

• Train all sites on SAE definitions and timelines during SIVs
• Ensure SAE SOPs are available at all sites
• Conduct routine monitoring of SAE reporting compliance
• Escalate repeated non-compliance to Quality or Risk Management

10. Audit and Inspection Readiness:

Sponsors must retain full documentation supporting SAE submissions for inspection by regulators. Key documents include:

• SAE source documents
• Signed SAE forms
• Submission receipts to authorities
• Safety review meeting minutes
• Corrective and Preventive Action (CAPA) logs, if applicable

Common Pitfalls in Sponsor SAE Management:

• Delayed assessment or reporting due to poor data flow
• Inadequate causality documentation
• Failure to reconcile SAE data across databases
• Inconsistent timelines across study regions

Conclusion:

Sponsor obligations in global SAE management extend far beyond receiving reports from sites. They encompass validation, assessment, reporting, follow-up, documentation, and global harmonization. A structured and well-trained pharmacovigilance system—combined with reliable tools and SOPs—ensures timely reporting and regulatory compliance, ultimately safeguarding patient safety and clinical trial integrity.