SAE Reporting Timeline Overview
Timely reporting of Serious Adverse Events (SAEs) is critical for participant safety and regulatory compliance. This quick reference provides the essential timelines and requirements you need to ensure compliant SAE reporting.
Definition: What Qualifies as an SAE?
An adverse event is considered serious if it meets any of the following criteria:
| Criterion | Description |
|---|---|
| Death | Results in death |
| Life-threatening | Places the participant at immediate risk of death |
| Hospitalization | Requires inpatient hospitalization or prolongs existing hospitalization |
| Disability | Results in persistent or significant incapacity or substantial disruption of normal life functions |
| Congenital anomaly | Results in a congenital anomaly or birth defect |
| Important medical event | Requires intervention to prevent one of the outcomes above |
Investigator Reporting Timelines
Investigator to Sponsor notification requirements:
| Event Type | Timeline | Notes |
|---|---|---|
| Fatal or life-threatening SAE | Immediately, within 24 hours | Phone notification followed by written report |
| All other SAEs | Within 24-72 hours | Per protocol requirements; 24 hours is preferred |
| Follow-up information | As available | Ongoing until resolution or stabilization |
Key Actions for Investigators:
- Document the event in source documents immediately upon awareness
- Complete the SAE report form with all available information
- Report to the sponsor regardless of perceived causality
- Notify the IRB/Ethics Committee per local requirements
- Provide follow-up reports until resolution
Sponsor Reporting Timelines
Sponsor reporting to regulatory authorities:
| Report Type | Timeline | Applicable Events |
|---|---|---|
| IND Safety Report (FDA) | 7 calendar days | Fatal or life-threatening unexpected suspected adverse reactions |
| IND Safety Report (FDA) | 15 calendar days | All other unexpected serious suspected adverse reactions |
| SUSAR to EMA | 7 days (initial) | Fatal or life-threatening SUSARs |
| SUSAR to EMA | 15 days | All other SUSARs |
| Annual Safety Report | Within 60 days of DIBD | Comprehensive annual safety update |
Definitions:
- SUSAR: Suspected Unexpected Serious Adverse Reaction
- DIBD: Development International Birth Date (anniversary of first regulatory approval to conduct trials)
- IND: Investigational New Drug application
Ethics Committee / IRB Notification
| Event Type | Timeline | Notes |
|---|---|---|
| Unanticipated problems involving risk | Promptly, per IRB requirements | Typically within 5-10 business days |
| Deaths | Within 24-48 hours | Per local IRB policy |
| Serious, unexpected, related events | Within 10 business days | Or per IRB-specified timeline |
| Protocol deviations affecting safety | Promptly | Usually within 5 business days |
Expedited vs. Aggregate Reporting
Expedited Reporting Required When:
- Event is serious AND
- Event is unexpected (not in IB or consent) AND
- Event is possibly related to the investigational product
Aggregate Reporting (Annual Safety Reports):
- Summary of all SAEs
- Updated benefit-risk assessment
- Line listings by system organ class
- Narrative summaries of significant events
Documentation Requirements
Each SAE report must include:
- Participant identifier (not name)
- Event description and onset date
- Severity and seriousness criteria met
- Causality assessment
- Action taken with investigational product
- Outcome and resolution date (if applicable)
- Reporter information
Clock Start Times
| Scenario | Clock Starts When |
|---|---|
| Investigator reporting | Investigator becomes aware of the event |
| Sponsor reporting | Sponsor receives minimum information for valid report |
| Minimum information | Identifiable patient, identifiable reporter, suspect product, serious adverse event |
Common Pitfalls to Avoid
- Delayed initial notification: Report immediately, even with incomplete information
- Waiting for causality determination: Report regardless of perceived relationship
- Incomplete follow-up: Continue reporting until resolution
- Missing clock start documentation: Record date/time of awareness
- Inconsistent terminology: Use MedDRA coding for consistency
Regional Variations
| Region | Primary Authority | Key Requirement |
|---|---|---|
| United States | FDA | 21 CFR 312.32 |
| European Union | EMA/National Authorities | Regulation EU 536/2014 |
| United Kingdom | MHRA | UK SI 2004/1031 |
| Japan | PMDA | J-GCP, PAL |
| Canada | Health Canada | FDR C.05.014 |
Always verify current local requirements as timelines may vary by jurisdiction.
