01 · The Question
If the research did not cause the event, do you still have to report it?
A participant becomes ill during a study, but the investigator thinks the illness is probably unrelated to participation. Should the event still be documented? Does it need to be sent to the sponsor? What about the IRB or REC? If it is clearly unrelated, can the research team simply ignore it?
The difficulty is that researchers often use the word report for several different actions. Recording an event in study records, notifying a sponsor or monitoring entity, promptly reporting an unanticipated problem to an IRB or REC, and submitting a regulatory safety report are not necessarily governed by the same criteria.
Causality therefore matters, but not at the same point in every reporting pathway.
02 · The Short Answer
No single causality rule applies to every type of adverse-event reporting
In Brief
No. An adverse event does not have to be caused by the research merely to qualify as an adverse event, and some study procedures require adverse events to be recorded or communicated even when causality is uncertain or unlikely. However, relatedness can be a required criterion for particular expedited or unanticipated-problem reporting pathways.
The correct question is therefore not simply “Was it caused by the research?” Ask what reporting obligation you are evaluating, which rules govern it, and whether seriousness, expectedness, relatedness, or other criteria must also be satisfied.
03 · What You Need to Know
Why causality and reportability must be assessed separately
An adverse event does not inherently mean a research-caused event
The starting point is the definition of an adverse event in research . OHRP uses the term broadly for an unfavorable medical occurrence temporally associated with participation, whether or not it is considered related to the research. FDA similarly defines an adverse event in the IND context as an untoward medical occurrence associated with drug use in humans, whether or not considered drug related.
So the label adverse event does not answer the causality question. An AE can be related, possibly related, unlikely to be related, or unrelated, depending on the framework and the evidence available.
“Reportable” does not describe one destination
This is where much of the confusion begins. Researchers may be required to capture or communicate safety information through several channels.
Action
Possible recipient or location
Does causality always have to be established first?
Record an AE
Case report form, research record, or safety database
No. Follow the protocol's AE collection rules.
Notify a study monitoring entity
Sponsor, coordinating center, medical monitor, DSMB or DMC
Not necessarily. Requirements are study-specific.
Report an unanticipated problem
IRB or REC and other required entities
Related or possibly related is a key criterion under the OHRP framework.
Submit an expedited IND safety report
FDA and participating investigators
For a serious and unexpected suspected adverse reaction, FDA requires evidence suggesting a causal relationship.
Consequently, saying “this AE is not reportable” without identifying the reporting pathway can be misleading. An event may not qualify for one expedited report but may still need to be documented, communicated elsewhere, followed clinically, or included in other safety information.
OHRP does not require every adverse event to be promptly reported to the IRB
For HHS-regulated research under OHRP's framework, the key issue is whether an adverse event constitutes an unanticipated problem involving risks to subjects or others .
OHRP describes an unanticipated problem as an incident, experience, or outcome that is unexpected, related or possibly related to participation in the research, and suggests that the research places participants or others at greater risk of harm than was previously known or recognized. All three criteria are required under that framework.
For relatedness, OHRP uses a “reasonable possibility” threshold for possibly related events. It recognizes that causality can be difficult to determine and that judgments commonly fall along a continuum rather than into an immediately obvious yes-or-no answer.
OHRP explicitly states that many individual AEs are unrelated to research participation and therefore fail the relatedness criterion for an unanticipated problem. Those events do not require prompt reporting under that particular HHS unanticipated-problem requirement merely because they are AEs.
But an unrelated event may still need to go to a monitoring entity
Not qualifying as an unanticipated problem does not necessarily end the matter. OHRP states that, regardless of whether an internal AE is determined to be an unanticipated problem, investigators must ensure that it is reported to a monitoring entity such as the sponsor, coordinating or statistical center, independent medical monitor, or DSMB/DMC when required by the monitoring provisions of the IRB-approved protocol or institutional policy.
This illustrates why “unrelated” should not be translated automatically into “do nothing.” The protocol may require broader safety collection than the threshold used for prompt IRB reporting.
FDA distinguishes an adverse event from a suspected adverse reaction
FDA's IND framework provides another useful example of why causality changes the reporting category rather than the basic existence of an AE.
FDA defines an adverse event without requiring drug relatedness. A suspected adverse reaction , however, is an AE for which there is a reasonable possibility that the drug caused the event. For IND safety reporting, FDA explains that reasonable possibility means there is evidence suggesting a causal relationship.
Adverse event
The occurrence itself. Drug causality is not required by the FDA AE definition.
Suspected adverse reaction
An AE for which evidence suggests a reasonable possibility that the drug caused the event.
For the expedited IND safety-reporting pathway for a serious and unexpected suspected adverse reaction, seriousness and unexpectedness alone are therefore insufficient. The sponsor also needs evidence suggesting causality.
Causality is not always obvious from one participant
Some events have alternative explanations. A participant may have an underlying disease that itself causes the outcome. The event may be common in the study population regardless of treatment. A concomitant medication may be responsible. An unrelated accident may occur during follow-up.
FDA's current IND guidance recognizes that causal evidence can sometimes emerge from patterns rather than from one isolated case. Its examples include aggregate analyses showing that events occurring naturally in the study population appear more frequently in the treatment group than in a concurrent or historical control group.
This is one reason researchers should avoid making causal judgments solely from chronology. “It happened afterward” and “the research caused it” are not equivalent statements.
Uncertainty should not be silently converted into “unrelated”
OHRP acknowledges that determining relatedness or possible relatedness can be difficult. Its threshold of reasonable possibility is deliberately different from requiring proof that the research caused an event.
The study should specify who performs this assessment and how categories are assigned. The question of who decides whether an adverse event is related to the research is therefore more than administrative detail. It affects the consistency and defensibility of safety decisions.
Watch Out
Do not use “probably unrelated” as a universal exemption from documentation or reporting. Different obligations use different thresholds. Check the protocol and the requirements of the relevant sponsor, IRB or REC, institution, funder, and regulator before deciding that no further action is required.
04 · A Practical Example
An SAE can be unrelated and still matter to the study
Hypothetical Example
A participant is hospitalized during follow-up
A participant in a clinical trial is admitted to hospital after injuries sustained in a road accident. The investigator learns about the hospitalization during a scheduled follow-up call. Available information provides no reason to believe that the investigational product or any study procedure contributed to the accident.
Identify the event
Under the hypothetical protocol, the occurrence falls within the study's AE collection period.
Assess relatedness
The available evidence indicates that the accident and resulting injuries are unrelated to the research.
Apply the correct reporting rules
The research team documents and communicates the SAE according to the hypothetical protocol. Its unrelated status may mean it does not satisfy a separate reporting pathway that requires research relatedness, but that does not erase the SAE or its required study documentation.
The important distinction is that serious , related , and reportable through a particular pathway are separate determinations.
06 · What This Means for You
Ask “reportable to whom?” before deciding that an event is not reportable
When an AE occurs, avoid making one global reportability decision. Work through the obligations separately.
A practical reporting framework
If an occurrence meets the study's AE definition
Document it according to the protocol even if causality has not yet been established.
If the protocol requires AEs or SAEs to be communicated to the sponsor or monitoring entity
Follow that requirement regardless of whether a different external reporting threshold has been met.
If you are evaluating an OHRP unanticipated problem
Assess unexpectedness, relatedness or possible relatedness, and whether the event indicates greater risk than previously known.
If you are evaluating an FDA IND safety report for a serious and unexpected suspected adverse reaction
Determine whether there is evidence suggesting a causal relationship in addition to seriousness and unexpectedness.
If the governing requirements are unclear
Consult the approved protocol and current requirements of the sponsor, IRB or REC, institution, and applicable regulator rather than applying a generic rule.
The detailed timing and destinations for these reports vary considerably. Once you know what kind of event you have, determine when the adverse event needs to be reported under the requirements governing your study.
07 · A Quick Checklist
Before deciding that an adverse event is not reportable
For each adverse event, check:
Does the occurrence meet the AE definition and collection period specified in the protocol?
Have you documented the event even if its cause is still uncertain?
Has seriousness been assessed separately from relatedness?
Has the appropriate person assessed whether there is a reasonable possibility that the research contributed to the event?
Does the protocol require notification to a sponsor, coordinating center, medical monitor, or DSMB/DMC?
Does the event meet the criteria for an unanticipated problem under the applicable oversight framework?
If an FDA IND safety report is being considered, have the applicable seriousness, unexpectedness, and causal-evidence requirements been evaluated?
Have you checked current study-specific, institutional, sponsor, and regulatory reporting requirements rather than assuming one rule applies everywhere?
09 · The Bottom Line
An event can matter even before you know what caused it
The Bottom Line
An adverse event does not have to be caused by the research simply to be an adverse event, and lack of proven causality does not automatically mean that the event can be ignored or left undocumented.
Relatedness becomes decisive for some reporting pathways but not all of them. Separate AE documentation, sponsor or monitoring requirements, IRB or REC reporting, and regulatory safety reporting, then apply the specific criteria governing each one.
11 · Cite this Guide
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.
Recommended (Field Guide)
APA
MLA
Chicago
Copy Citation