Serious Adverse Event (SAE)

A serious adverse event (SAE) is an adverse event (AE) that meets one of a fixed set of regulatory seriousness criteria set out in ICH E2A, “Clinical Safety Data Management: Definitions and Standards for Expedited Reporting” (finalized 1994), and referenced by ICH E6(R2) Good Clinical Practice. Seriousness is what triggers the heightened reporting obligations that distinguish an SAE from a routine AE — it is not a judgment about how the event feels to the subject, and it does not depend on whether the event is believed to be caused by the investigational product.

The six ICH E2A seriousness criteria

An AE qualifies as an SAE if it meets any one of the following:

• Results in death.
• Is life-threatening — the subject was, in the investigator’s judgment, at immediate risk of death from the event as it occurred (not an event that hypothetically might have caused death had it been more severe).
• Requires inpatient hospitalization, or prolongs an existing hospitalization.
• Results in persistent or significant disability or incapacity.
• Is a congenital anomaly or birth defect in the child of a subject exposed to the product.
• Is another medically important event that, based on appropriate medical judgment, may jeopardize the subject or may require medical or surgical intervention to prevent one of the other outcomes listed above — a catch-all criterion for events that don’t fit the other five but are clinically significant enough to warrant the same handling (for example, an allergic reaction treated aggressively in an emergency room without an overnight admission).

Meeting any single criterion is sufficient — an event does not need to meet more than one.

SAE is not the same as “severe,” and not the same as reportable-to-regulators

Two distinctions get confused often enough to be worth stating directly:

• Seriousness vs. severity. Seriousness (the criteria above) is a fixed regulatory category. Severity — mild, moderate, severe — is a separate clinical intensity grading, commonly captured with a scale such as CTCAE. A severe headache is not automatically an SAE. A mild-intensity event that triggers hospitalization is an SAE, because hospitalization is one of the seriousness criteria, independent of how the event felt clinically.
• SAE vs. SUSAR. Every SAE must be reported by the investigator to the sponsor, but not every SAE is expedited-reportable to a regulatory authority. Expedited reporting to FDA, EMA, and other authorities is triggered specifically by a SUSAR — a Suspected Unexpected Serious Adverse Reaction: an event that is simultaneously serious, unexpected (not consistent with the current Investigator’s Brochure or approved labeling), and suspected of a causal relationship to the product. An SAE that is expected (already described in the Investigator’s Brochure) and assessed as unrelated to the product is still an SAE — the investigator still reports it to the sponsor immediately — but it does not, on its own, start the regulator-facing expedited-reporting clock the way a SUSAR does.

Worked examples

• SAE, hospitalization criterion: a subject is admitted overnight for observation after an infusion reaction. Regardless of the eventual causality assessment or how mild the reaction looked in retrospect, the inpatient admission itself satisfies the hospitalization criterion, making this an SAE.
• SAE, medically-important-event criterion, not otherwise hospitalized: a subject develops an allergic reaction treated with epinephrine in an emergency department and discharged the same day without formal admission. It doesn’t meet the hospitalization criterion literally, but the investigator judges it medically important enough that it could have required hospitalization absent intervention — it qualifies as an SAE under the sixth, catch-all criterion.

Counter-example

A subject reports moderate joint pain lasting several days, managed with over-the-counter analgesics and no medical visit. Even graded “moderate” on a severity scale, it meets none of the six seriousness criteria — no hospitalization, no life-threatening presentation, no disability, no death, no congenital anomaly, and the investigator does not judge it medically important enough to require intervention to prevent one of those outcomes. It is recorded as a non-serious AE, not an SAE.

Reporting timelines

Two separate clocks apply, and it matters which one governs a given SAE:

• Investigator to sponsor: under US regulation, an investigator must report any SAE to the sponsor immediately, regardless of the investigator’s causality opinion (21 CFR 312.64(b)). This obligation applies to every SAE, not only SUSARs.
• Sponsor to regulator, for SUSARs specifically: under 21 CFR 312.32, a sponsor must notify FDA of a fatal or life-threatening SUSAR within 7 calendar days of becoming aware of it, with a complete follow-up report due within an additional 8 days, and other SUSARs within 15 calendar days. The EU’s Clinical Trials Regulation ((EU) No 536/2014) applies the same 7-day/15-day structure for SUSAR reporting to the EudraVigilance database. Neither clock is triggered by a serious-but-expected, unrelated SAE on its own — only by the narrower SUSAR subset.

This entry defines the SAE classification itself. For the full picture of how AE, SAE, and SUSAR reporting fit together operationally — including periodic aggregate safety reporting (DSUR) and the role of an independent safety-oversight body — see Pharmacovigilance in Clinical Research: AE, SAE, and SUSAR Reporting and the base Adverse Event (AE) term.

References

• ICH E2A, “Clinical Safety Data Management: Definitions and Standards for Expedited Reporting” (1994) — ich.org efficacy guidelines
• ICH E6(R2) Good Clinical Practice — safety reporting provisions
• 21 CFR 312.32 and 21 CFR 312.64(b) — US IND safety reporting requirements
• Regulation (EU) No 536/2014 — EU Clinical Trials Regulation, SUSAR reporting to EudraVigilance