HOW CAN WE HELP YOU? Call 1-800-TRY-CHOP
In This Section
Serious Adverse Events (SAEs), Unanticipated Problems (UAPs), and Reporting Requirements
Unanticipated Problems vs Adverse Events
What else besides an AE could be an unanticipated problem?
The common feature of the events is that all potentially place subjects at risk of serious harm. Even when no actual harm occurs, if the event meets the definition of an unanticipated problem, it must be reported to the IRB. When the event goes beyond simply potential harm to where actual harm befalls a subject, then the event would be considered an adverse event. Adverse events make up the most frequently reported unanticipated problem reported to the IRB.
Decision Tree: Is this an unanticipated problem that requires prompt reporting to the IRB?
The decision tree branches and considers separately the reporting requirements for serious adverse events (SAE) from other unanticipated problems. An SAE is defined as an adverse event that:
- results in death;
- is life-threatening;
- prolongs or results in hospitalization;
- results in a persistent or significant disability;
- causes a congenital anomaly or birth defect; or
- is a medically significant event that jeopardizes the subject's health.
Which Problems Require Prompt Reporting?
Prompt reporting is required for all unanticipated problems which means those that are serious, unexpected and related to the research activity. This requirement for reporting unanticipated problems includes both CHOP-enrolled subjects and subjects enrolled at external sites.
SAE Reports from External Sites
Sponsors and cooperative study groups frequently forward all SAE reports that take place during a multi-center trial, to all site investigators regardless of whether or not the event constitutes an unanticipated problem. Many of the reports relate to subjects who are not like those participating in the trial underway at the local site. The reports often come from trials for different disease indications or from subjects of different age groups with different pre-existing medical conditions. It is often impossible for an IRB to draw any conclusions from these reports as far as how they relate to the subjects in the trial that is going on at the local site.
To help clarify which reports need to be forwarded to the IRB, the FDA has issued an extremely useful guidance document for investigators and IRBs entitled Adverse Event Reporting to IRBs — Improving Human Subject Protection . This guidance should be read by all those conducting FDA-regulated research and who receive SAE reports from sponsors. The guidance makes clear that only those reports that meet the definition of an unanticipated problem should be shared with the IRB; the investigator should store the rest in the study file. Minimizing the number of reports submitted to the IRB reduces wasted effort for both the investigators and the IRB and without increasing risk to participants.
Which external SAE reports need to be reported promptly to the IRB?
Sponsor's letters often state that the report should be filed with the IRB if required by local policy. The CHOP IRB prefers to review only those reports that meet (or at least might meet) all of the criteria for being an unanticipated problem. Investigators and study teams should store all other external reports in their study binders but need not forward these to the IRB. In the event the sponsor requires submission of the report to the IRB, this can be noted in the eIRB submission form and an acknowledgement will be sent automatically.
Reports that suggest that subjects or others are placed at a greater risk of harm then initially anticipated should be accompanied by an Action Plan that outlines the steps that will be taken to mitigate the newly identified risk(s). If the sponsor of a multicenter study does not propose any changes, it is suggestive that the event does not meet all of the criteria for an unanticipated problem. The Action Plan should include one or more of the following:
- a modification to the protocol;
- a modification to the consent form;
- a change in the study procedures; or
- changes to the the investigative team education or oversight procedures;
- a notification of current or former study participants.
The IRB has issued a Memo outlining Procedures for Reporting External SAE Reports that provides a more detailed explanation.
Timelines for Prompt Reporting of Unanticipated Problems
Events that satisfy all of the criteria for an unanticipated problem must be reported promptly to the IRB in addition to the reporting obligations to the sponsor or regulatory authorities. The reports should be sent to the CHOP IRB in accordance with the following timelines:
- Serious adverse events that involve a CHOP subject and involve the death of the subject or are considered life-threatening need to be reported to the IRB within 1 business day of discover (telephone, fax, email, eIRB) with a full report submitted in eIRB within 48 hours of the initial notification;
- All other unanticipated problems involving CHOP subjects must be reported within 7 business days of discovery; and
- All other unanticipated problems involving subjects external to CHOP must be reported within 7 business days of receipt of the report from the study sponsor, data coordinating center or overall study PI.
Frequently Asked Questions
Do I have to report all internal (occurred at CHOP) SAE's to the IRB?
Only SAEs that are unexpected and related. For example, hospitalization of children with Sickle Cell Disease for painful crisis is expected as would be death after cardiac surgery. These events do not have to be reported promptly because they do not represent unanticipated problems involving risks to subjects. Well-written protocols anticipate and delineate the likely serious events and list the ones that will not be reported as SAEs.
Do I have to report every external SAE report that the sponsor sends me?
The IRB does not want to see most of these reports; only events that are serious, unexpected and related to the research activity need to be reported. A single event, by itself, is usually insufficient to make a judgment about change in possible risks to subjects. If in the investigator's judgment, the event was expected as a result of the subject's age, existing condition, other treatment administered or another factor, there is no need to report the event. The report must be maintained in the study file.
What about the external SAE follow-up reports?
The IRB does not want to receive follow-up reports that add no additional information about possible risks to subjects.
Why do sponsors send all of these reports if they aren't of any benefit?
Sponsors believe that they are complying with the regulatory requirements. They are unwilling to classify SAEs as unrelated to the study drug or other intervention even when there are other plausible and much more likely explanations. From the IRB's perspective, a report is only useful if the sponsor believes that the event is of sufficient significance to modify the protocol, the consent form or the Investigators Brochure. Less than 1% of the SAE reports received by the IRB result in a change to the research. As a result, the IRB has issued a Memo clarifying its requirements for external SAE reports.
My sponsor requires that I send all of the SAE reports to the IRB; what do I do?
If the sponsor requires that they be sent, the IRB has issued a Memo outlining Procedures for Reporting External SAE Reports that provides a more detailed explanation. If these reports are sent to the IRB, an acknowledgement will be issued without review by the SAE subcommittee. This is not a productive use of the investigator's or the IRB's time. Hopefully, the FDA Guidance on Adverse Event Reporting to IRBs will diminish the frequency of these reports.