When Does an Adverse Event in Research Need to Be Reported?

Does every adverse event have to be reported immediately?

A participant reports nausea. Another is unexpectedly hospitalized. A third experiences a known side effect already described in the study documents. Does each event need to go to the sponsor? The IRB or REC? A regulator? And does “report immediately” mean within hours, within a day, or within a regulatory deadline such as seven or fifteen calendar days?

There is no universal adverse-event reporting deadline because adverse-event reporting is not one single process. The protocol may require collection of one set of events. Serious adverse events may follow another pathway. Unanticipated problems may require prompt reporting to an IRB or REC. Particular regulatory safety reports may have their own criteria and deadlines.

The practical question is therefore not merely “Is this an AE?” It is “What kind of event is this, who needs to know about it, and what rule sets the deadline?”

Report the event according to the pathway that applies to it

Adverse-event reporting depends on what you are reporting and to whom

Start by separating recording from external reporting

An adverse event may first need to be documented in study records or a case report form. That does not necessarily mean the same event must immediately be submitted separately to every oversight body.

ICH E6(R3), for example, states that adverse events and abnormal test results required for safety evaluations under the protocol should be reported to the sponsor according to the protocol's reporting requirements and time periods. It also notes that unfavorable medical events occurring before administration of an investigational product, such as during screening, should be considered and reported when required by the protocol.

This makes the approved protocol a critical operational source. Researchers should know before enrollment begins which events are collected, when collection starts and ends, where they are documented, and which events require escalation.

Not every AE needs immediate sponsor reporting

For non-serious adverse events in clinical trials, the protocol commonly determines what must be reported to the sponsor and on what timetable. ICH E6(R3) does not impose one universal immediate-reporting rule for every AE. Instead, protocol-required AEs and abnormal test results are reported according to the requirements and periods specified in the protocol.

The fact that an event is not subject to immediate notification does not mean that it can be omitted from required study documentation.

Serious adverse events generally require rapid notification to the sponsor

The reporting expectation changes substantially when an event meets serious adverse event criteria.

Under ICH E6(R3), all SAEs should generally be reported to the sponsor immediately after the investigator reasonably becomes aware of the event. The investigator should include an assessment of causality, and necessary subsequent information should be provided in follow-up reports. The guideline also recognizes that, in accordance with applicable regulatory requirements, a protocol may identify certain SAEs that do not require immediate reporting, such as particular deaths or other events that are study endpoints.

Prompt IRB reporting is not synonymous with reporting every AE

For non-exempt human-subjects research conducted or supported by HHS, OHRP distinguishes adverse events generally from unanticipated problems involving risks to subjects or others.

OHRP states that only a small subset of adverse events are unanticipated problems that must be reported under the HHS framework. An adverse event generally qualifies when it is unexpected, related or possibly related to research participation, and suggests that the research places participants or others at greater risk of harm than was previously known or recognized. When all three criteria are met, the event must be reported promptly to the appropriate entities under the applicable HHS requirements.

This means that a routine expected AE should not automatically be treated as an unanticipated problem simply because it happened. Similarly, an AE clearly caused by an unrelated circumstance may fail the relatedness criterion even if its medical outcome is serious.

“Promptly” does not have one universal number of days under the OHRP framework

OHRP explains that the appropriate reporting time depends on the nature of the unanticipated problem, the severity of the implications for participant safety, and the type of information involved. The institution's written procedures should specify the required timeframe for reporting unanticipated problems.

The practical consequence is important: researchers should not invent a generic “five-day IRB rule” or “ten-day IRB rule” and apply it everywhere. The governing institutional procedures and IRB or REC requirements should be checked directly.

FDA IND safety reporting uses specific criteria and deadlines

For studies conducted under a U.S. Investigational New Drug application, the sponsor has separate regulatory safety-reporting responsibilities under 21 CFR 312.32. These should not be confused with the investigator's initial SAE notification to the sponsor.

FDA currently states that qualifying potential serious risks under the applicable IND safety-reporting provisions must be reported by the sponsor to FDA and all participating investigators as soon as possible and no later than 15 calendar days after the sponsor determines that the information qualifies for reporting. Unexpected fatal or life-threatening suspected adverse reactions must be reported as soon as possible and no later than 7 calendar days after the sponsor initially receives the information.

These timelines belong to different actors and different reporting pathways. A site's obligation to notify a sponsor of an SAE should not be confused with the sponsor's subsequent regulatory deadline for an IND safety report.

Serious does not automatically mean expedited regulatory reporting

An SAE may require immediate communication from an investigator to a sponsor, but that does not mean the event automatically satisfies every regulator's expedited safety-reporting criteria.

For FDA IND reporting, for example, one important pathway concerns serious and unexpected suspected adverse reactions. FDA's terminology requires evidence suggesting a causal relationship between the drug and the event for an AE to be considered a suspected adverse reaction. Thus seriousness, unexpectedness, and causal evidence perform different functions in determining regulatory reportability.

This is why causality and adverse-event reporting should not be collapsed into a single yes-or-no decision.

Expected events may still need to be recorded or reported

“Expected” does not mean “ignore.” An event can be expected and still require protocol documentation or sponsor notification. It may also be serious and therefore fall under an SAE reporting procedure even though its nature is already known.

Expectedness becomes particularly important for certain expedited regulatory pathways and for determining whether an event represents an unanticipated problem. It does not erase whatever collection and reporting obligations the protocol independently imposes.

Unrelated events may also have reporting obligations

Similarly, an investigator's judgment that an event is unrelated does not necessarily eliminate every reporting requirement. OHRP states that an internal AE should still be reported to a monitoring entity when required by the IRB-approved protocol or institutional policy, regardless of whether the investigator determines that it is an unanticipated problem.

ICH E6(R3) likewise expects an investigator's SAE report to the sponsor to include a causality assessment rather than limiting initial SAE communication only to events already judged related.

External adverse-event reports require meaningful assessment

In multicenter research, investigators may receive safety reports about events occurring at other sites. OHRP cautions that isolated external AE reports often contain too little information for a local investigator or IRB to determine whether the event is unexpected, related, or evidence of increased risk.

Under OHRP's framework, only external adverse events identified as satisfying all three unanticipated-problem criteria require prompt submission by the investigator to the IRB as unanticipated problems. OHRP recommends that distributed reports explain why an event or series of events has been determined to be an unanticipated problem and describe proposed corrective actions.

New information can change an earlier reporting decision

Safety assessment is not always finished with the first report. A causal relationship may become clearer, an initially isolated event may become a pattern, or follow-up information may reveal greater seriousness than first recognized.

FDA requires sponsors to promptly investigate safety information and submit relevant follow-up information concerning previously submitted IND safety reports. If investigation shows that an event initially considered non-reportable actually qualifies, the sponsor must submit the required safety report within the applicable timeframe after that determination.

Similarly, OHRP notes that a monitoring entity may recognize an unanticipated problem from an unexpectedly high frequency of events even when individual investigators could not identify the signal from isolated cases.

One event can trigger different clocks for different recipients

The same incident can therefore generate several actions without those actions sharing the same recipient, decision-maker, form, or deadline.

Common mistakes about adverse-event reporting

Build the reporting decision around the recipient and governing rule

The safest operational approach is not to memorize one number. Instead, know the reporting pathways before the study starts and identify which pathway applies when an event occurs.

After a particularly consequential event, reporting may be only the beginning. Researchers may also need to protect current participants, revise consent information, reassess study procedures, or determine what should happen after a serious participant-safety incident.

When an adverse event occurs, check each reporting pathway

Frequently asked questions about adverse-event reporting

There is no single adverse-event reporting clock

How to Cite This Guide

This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.