Usage Examples
- The site called the SAE in at 2 a.m. and the outcome was fatal and unexpected, so we are on the 7-day clock, not the 15-day one.
- It was serious on the hospitalization criterion but expected per the IB, so it goes in the annual report rather than an IND safety report.
- SAE reconciliation found four events in the CRF that never reached the safety database.
What is SAE (Serious Adverse Event)?
An SAE is any adverse event or suspected adverse reaction that results in death, a life-threatening event, inpatient hospitalization or its prolongation, persistent or significant incapacity, or a congenital anomaly, in the view of either the investigator or sponsor.
An SAE is the trip-wire that converts a routine safety observation into a reportable event with a clock attached. A regulator cannot wait for a completed causality analysis to learn that a subject died or was hospitalized on an investigational drug. The seriousness classification exists to separate the events that must reach FDA in days from those that can wait for a periodic report.
An SAE covers five outcomes under 21 CFR 312.32(a): death, a life-threatening event, inpatient hospitalization or its prolongation, persistent or significant incapacity, and congenital anomaly, plus important medical events requiring intervention to prevent one of those. An SAE does not require that the drug caused it. Causality is a separate judgment, expectedness is a third, and seriousness is not severity.
An SAE moves through a two-step chain in practice. The investigator reports it to the sponsor immediately, whether or not it looks drug-related, with a causality assessment attached. The sponsor then decides whether the event is also unexpected and a suspected adverse reaction, and that determination, not the site's call, is what starts the 15-day or 7-day clock.
Not to be confused with
- Adverse Event
- an adverse event becomes an SAE only when it meets one of the outcome criteria in 21 CFR 312.32(a). Most never do. The classification is what decides whether an expedited clock starts or the event simply accrues to the periodic report.
- Severe adverse event
- severity describes intensity (a severe headache); seriousness is defined purely by outcome. A severe event is frequently not an SAE, and a moderate one that causes an inpatient admission is.
- SUSAR
- a SUSAR is the narrower subset that is serious, unexpected, and a suspected adverse reaction. Only that subset drives the 7- and 15-day FDA notifications; a serious but expected event is still an SAE and still reportable to the sponsor.
- Serious adverse drug experience
- the postmarketing counterpart in 21 CFR 314.80 for approved products. Same outcome list, different pathway: serious and unexpected cases go in as 15-day Alert reports from the application holder, not as IND safety reports.
The obligations split between the site, the sponsor's IND phase, and the postmarketing phase.
What you must do
- 1Report to the sponsor immediately any serious adverse event, whether or not considered drug related, with an assessment of whether there is a reasonable possibility the drug caused it21 CFR 312.64(b)
- 2Classify an event as serious whenever either the investigator or the sponsor judges it to result in death, a life-threatening event, inpatient hospitalization or prolongation, persistent or significant incapacity, or a congenital anomaly, and apply the important-medical-event judgment to events that meet none of those literally21 CFR 312.32(a)
- 3Notify FDA and all participating investigators in an IND safety report no later than 15 calendar days after the sponsor determines the information qualifies for reporting21 CFR 312.32(c)(1)
- 4Notify FDA of any unexpected fatal or life-threatening suspected adverse reaction no later than 7 calendar days after the sponsor's initial receipt of the information21 CFR 312.32(c)(2)
- 5After approval, submit each serious and unexpected adverse drug experience, foreign or domestic, no later than 15 calendar days from the applicant's initial receipt of the information21 CFR 314.80(c)(1)(i)
Common mistakes
Running both expedited clocks from the same date
the 15-day clock starts when the sponsor determines the information qualifies for reporting; the 7-day fatal or life-threatening clock starts at the sponsor's initial receipt of the information. Teams that manage one date get the 7-day report late, and lateness is visible in the submission's own timestamps.
Letting the site filter SAEs by causality
investigators must report every serious adverse event to the sponsor whether or not it is considered drug related. Sites that screen out "obviously unrelated" events deprive the sponsor of the aggregate data behind the increased-rate analysis, and the gap surfaces at reconciliation or during an inspection of the safety database.
Treating the severity grade as the seriousness decision
grading an event mild, moderate, or severe on the CRF answers a different question than 21 CFR 312.32(a) asks. Seriousness is determined against the outcome list by either the investigator or the sponsor, and a moderate event that puts a subject in a hospital bed is an SAE.
When This Matters
- The site called the SAE in at 2 a.m. and the outcome was fatal and unexpected, so we are on the 7-day clock, not the 15-day one.
- It was serious on the hospitalization criterion but expected per the IB, so it goes in the annual report rather than an IND safety report.
- SAE reconciliation found four events in the CRF that never reached the safety database.
Frequently Asked Questions
An adverse event is serious when it results in death, a life-threatening event, inpatient hospitalization or prolongation of an existing hospitalization, persistent or significant incapacity, or a congenital anomaly. Important medical events also count when medical judgment says they may jeopardize the subject and require intervention to prevent one of those outcomes.
