Adverse Event and SAE Reporting in Clinical Trials: One Decision Tree, Two Reporting Tracks

At a glance

• “Serious” is a defined regulatory category, not a synonym for “severe.” An event is serious only if it meets one of six outcome criteria, regardless of how bad it looks.
• Expedited reporting is driven by three things together: seriousness, unexpectedness, and a reasonable possibility that the drug caused it. A serious-but-expected event is usually not expedited.
• There are two reporting tracks people collapse into one: investigator to sponsor (timeline set by the protocol), and sponsor to FDA and IRB/IEC (timelines set by regulation).
• The FDA clocks are concrete: 7 calendar days for an unexpected fatal or life-threatening suspected adverse reaction, and 15 calendar days for other serious, unexpected suspected reactions.
• Two common errors: equating serious with severe, and assuming every SAE is expedited. Both over- or under-report.

”Serious” is a definition, not an adjective

The most expensive mistake in safety reporting is treating “serious” as a judgment of how bad an event felt. It is a defined category. ICH E2A defines a serious adverse event or reaction as any untoward medical occurrence that at any dose results in death, is life-threatening, requires inpatient hospitalisation or prolongation of existing hospitalisation, results in persistent or significant disability or incapacity, or is a congenital anomaly or birth defect (ICH E2A, Definition of Serious). A mild rash that puts someone in hospital overnight is serious. A ferocious headache that resolves at home is not, however severe it felt.

Two clarifications matter. First, “life-threatening” has a precise meaning: it refers to an event in which the patient was at risk of death at the time of the event, and not an event which hypothetically might have caused death if it were more severe (ICH E2A, Definition of Serious). Second, FDA aligns the same threshold to either judge: an adverse event is life-threatening if, in the view of either the investigator or the sponsor, its occurrence places the patient at immediate risk of death (FDA IND safety reporting, §312.32(a)). If either party thinks it qualifies, it qualifies.

What actually triggers expedited reporting: three things at once

Seriousness alone does not put an event on the fast track. Expedited reporting turns on three conditions together. ICH E2A is explicit that all adverse drug reactions that are both serious and unexpected are subject to expedited reporting, and that non-serious adverse reactions, whether expected or not, will ordinarily not be subject to expedited reporting (ICH E2A, Single Cases of Serious, Unexpected ADRs). The third condition, causality, is built into the term “reaction”: FDA defines a suspected adverse reaction as any adverse event for which there is a reasonable possibility that the drug caused the event, and for IND safety reporting “reasonable possibility” means there is evidence to suggest a causal relationship (FDA IND safety reporting, §312.32(a)). FDA notes this causality standard is consistent with ICH E2A, so the two frameworks point the same way rather than conflicting.

Put together, the decision tree is: serious? unexpected (not already in the reference safety information)? a reasonable possibility the drug caused it? If yes to all three, it is expedited. If it is serious but expected, or serious but clearly unrelated, it is documented and rolled into periodic safety reporting rather than rushed out as an individual case.

Two tracks, two sets of clocks

The single biggest source of confusion is collapsing two distinct reporting relationships into one timeline.

Investigator to sponsor. This timeline is set by the protocol, not by a universal regulatory clock. ICH E6(R3) provides that reporting by investigators to the sponsor should be prospectively agreed and described in the clinical trial protocol (ICH E6(R3) §3.13.2). In practice protocols require SAEs to be reported to the sponsor immediately, commonly within 24 hours of the site becoming aware, but the binding number is the one in your protocol. Read it.

Sponsor to FDA and IRB/IEC. These clocks are regulatory and specific. The requirement for reporting any unexpected fatal or life-threatening suspected adverse reaction to FDA is no later than 7 calendar days after the sponsor’s initial receipt of the information (FDA IND safety reporting, §312.32(c)(2)). For the rest, ICH E2A sets the familiar 15-day window: serious, unexpected reactions that are not fatal or life-threatening must be filed as soon as possible but no later than 15 calendar days after first knowledge by the sponsor that the case meets the minimum criteria for expedited reporting (ICH E2A, Reporting Time Frames).

Track	Who to whom	Clock
Investigator to sponsor	Site reports SAEs to sponsor	Per the protocol (commonly immediate / 24h)
Sponsor to FDA	Unexpected fatal or life-threatening suspected reaction	7 calendar days
Sponsor to FDA	Other serious, unexpected suspected reaction	15 calendar days
Sponsor to investigators and IRB/IEC	SUSARs and urgent safety issues	With urgency, per applicable regulatory requirements

On that last row, ICH E6(R3) states the sponsor should review relevant safety information in a timely manner (ICH E6(R3) §3.13.1), and that the reporting of SUSARs to investigators and IRBs/IECs should be undertaken in a manner that reflects the urgency of action required, in accordance with applicable regulatory requirements (ICH E6(R3) §3.13.2). Separately, the investigator or institution should promptly report SUSARs to the IRB/IEC in accordance with applicable regulatory requirements (ICH E6(R3) §1.4.8). The shape is a relay: site to sponsor on the protocol clock, then sponsor outward on the regulatory clocks.

Worked logic, in order

1. Is it serious? Apply the six criteria, not your gut. Serious is not severe.
2. Is it unexpected? Compare against the reference safety information (the Investigator’s Brochure or equivalent). Already-listed reactions are expected.
3. Is there a reasonable possibility the drug caused it? Evidence suggesting a causal relationship makes it a suspected adverse reaction.
4. If all three: expedite. Fatal or life-threatening and unexpected goes on the 7-day clock; other serious-unexpected on the 15-day clock.
5. If not all three: document and aggregate. It still goes in the record and periodic reporting; it just is not an individual expedited case.

The “medically important” catch-all

The six seriousness criteria are not the whole boundary. There is a deliberate catch-all for events that are grave without fitting a listed outcome. FDA’s definition extends seriousness to important medical events that may not result in death, be life-threatening, or require hospitalization, when, based on appropriate medical judgment, they may jeopardize the patient or subject and may require medical or surgical intervention to prevent one of the outcomes listed in the definition (FDA IND safety reporting, medically important events). ICH E2A frames the same idea from the reporting side: medical and scientific judgment should be exercised in deciding whether expedited reporting is appropriate in other situations, such as important medical events that may not be immediately life-threatening or result in death or hospitalization but may jeopardize the patient or require intervention to prevent one of the listed outcomes (ICH E2A, serious adverse event).

The classic examples are bronchospasm treated in an emergency room without admission, a blood dyscrasia caught and corrected, or a seizure that did not lead to hospitalization. None ticks a literal seriousness box, yet each is exactly the kind of signal regulators want surfaced. So the practical rule is that the six criteria are a floor, not a ceiling: an event that clears none of them can still be serious if reasoned medical judgment says it could have led to a listed outcome without intervention. Teams that apply the criteria mechanically, asking only “was there a death, a hospitalization, a disability,” will under-classify exactly the events the catch-all exists to capture.

This is also why the seriousness assessment is a clinical judgment that should sit with someone qualified to make it, not a checkbox handed to whoever is entering data. The same event can be non-serious in one context and serious in another depending on what it threatened and what it took to manage. Getting that judgment right is upstream of everything else in this article: misjudge seriousness, and the expedited-reporting decision and its clock are wrong before they even begin.

Where teams get it wrong

• Equating serious with severe. Severity grades how bad an event is; seriousness is a defined category about outcome. They are independent. A grade 3 event may not be serious; a grade 1 event that causes hospitalisation is.
• Assuming every SAE is expedited. Expedited reporting needs serious and unexpected and suspected-related, together (ICH E2A). Expected serious events are not individually expedited.
• Treating the two tracks as one clock. The investigator-to-sponsor timeline is the protocol’s; the sponsor-to-FDA timelines are 7 and 15 calendar days. Missing either is a finding.
• Letting one party downgrade life-threatening. If either the investigator or the sponsor judges an event life-threatening, it is, for reporting purposes (FDA IND safety reporting, §312.32(a)).

Safety reporting handled well is a clean relay: classify the event against the definition, test it against the three expedited conditions, and route it on the right clock to the right recipient. The confusion that produces findings is almost always a collapsed definition or a collapsed timeline.

Sources

• ICH E2A Clinical Safety Data Management: Definitions and Standards for Expedited Reporting
• FDA, Safety Reporting Requirements for INDs and BA/BE Studies (21 CFR 312.32 guidance), 2012
• ICH E6(R3) Good Clinical Practice, version R3