Note that SEPs include items that were previously referred to as Adverse Events as well as other reportable problems that could occur in the conduct of a protocol.
By working through the appropriate items in the chart below, an investigator should be able to determine how a potentially reportable event should be classified, if it must be reported and, if so, how to report the event to the IRB.
1. Is the event/problem is On-Site or Off-Site?
|
On-site (internal/local) event/problem: an event/problem experienced by subjects enrolled by a UB investigator or UB affiliated investigator or experienced by subjects enrolled in studies for which a UB IRB acts as the IRB of record Off-site (external) event/problem: an event/problem experienced by subjects enrolled by investigators at other institutions engaged in the research project Most of the projects approved by the SBSIRB are single site and therefore all events are On-Site regardless of where they occur. Only projects that are approved as multi-site (i.e. the multi site addendum to the HS1A was completed in an IRB application with a plan for sharing information between multiple investigators working on the same project) can have Off-Site events. |
2. Is the On-site event/problem serious or non-serious?
|
To do this answer all of section 1, questions a-f on the SEP report form. If any of the answers is a “yes”, the problem is defined as serious. |
3. Did the On-Site Non-serious event/problem affect the rights or welfare of participants or did it require changes to the protocol to prevent future occurrences?
|
If an amendment needs to be requested, it must be approved by the IRB before it is implemented. These should be reported/requested as they occur. |
4. Was the Off-site event/problem serious or non-serious?
|
To do this answer all of section 1, questions a-f on the SEP report form. If any of the answers is a “yes”, the problem is defined as serious. |
5. Was the Off-Site serious event/problem anticipated or unanticipated?
|
Is the Off-Site serious problem described in the protocol and consenting document(s)? Was this event/problem expected as a natural progression of any underlying disease, disorder, or condition of the subject(s) experiencing the event/problem, and the subject’s predisposing factor profile for the event/problem? If no to both, the problem is unanticipated. If yes to either, the problem is anticipated. |
6. Was the Off-Site serious unanticipated event/problem related or possibly related?
|
Related or possibly related to the research: there is a reasonable possibility that the event/problem, incident, experience, or outcome may have been caused by the procedures involved in the research |
The approved pdf file should be printed and placed in the investigator’s indicated repository. This document must be used with the watermark and footer to produce copies of consent documents to be signed by participants when signed documentation of consent is a part of the approved protocol. It is recommended but not required that any advertisements, consent information sheets or other printed materials approved as a part of this protocol also be used with the watermark and footer present.
This document will not be signed unless an investigator needs a signed document in order to meet the requirements of research sponsors or other persons outside of the University at Buffalo. In these cases the investigator must send or bring one hard copy of this full document to the IRB administrator who will provide an appropriate signature and date.
The document will be password protected, but the file may be copied. If for any reason the researcher needs to produce an electronic file with less than the full document, pages in a copy of this file may be deleted using the Acrobat writer.
Use this form
to notify the IRB of changes to previously reported Serious Events/Problems (SEPs) including:
E-mail the form to SBSIRB@research.buffalo.edu. Follow-up reports should be sent to the SBSIRB within the same timeframes as used for initial reports.
Type of Report |
When to Report |
Deaths - except when death is the endpoint of the study |
Within 24-hours of knowledge or notification |
Life-threatening i.e., events/problems that place the subject at immediate risk of death from the event as it occurred |
Within 72-hours of knowledge or notification |
Required hospitalization or prolongation of existing hospitalization |
Within 72-hours of knowledge or notification |
Resulted in persistent or significant disability or incapacity |
Within 72-hours of knowledge or notification |
Resulted in congenital anomaly or birth defect |
Within 72-hours of knowledge or notification |
Based on appropriate clinical judgment, the event:
|
Within 72-hours of knowledge or notification |
Deviation from the approved investigational plan initiated in order to protect the life or physical well-being of a subject in an emergency situation |
Within 5 days of the emergency |
Deviation from the approved investigational plan initiated in order to eliminate an apparent hazard to a participant in an emergency situation |
Within 5 days of the emergency |
Increased Risk of Harm to subjects or others than was previously known or recognized (whether or not actual harm has occurred). Risks may be physical, psychological, economic, or social. Examples:
|
Within 10 working days of knowledge or notification |
| Breach of Confidentiality that caused harm or places subjects or others at increased risk of harm (physical, psychological, economic, or social harm (even if actual harm has not occurred). | Within 10 working days of knowledge or notification |
Significant impact on the integrity of the research data Examples:
|
Within 10 working days of knowledge or notification |
Unanticipated Adverse Device Effects Any serious adverse effect on health or safety of any life-threatening problem or death caused by, or associated with, an FDA regulated device, if that effect problem or death was not previously identified in nature, severity, or degree of incidence in the investigational plan or application, or any other unanticipated serious problem associated with a device that relates to the rights, safety, or welfare of subjects. |
Within 10 working days of knowledge or notification |
Any event/problem that would cause the sponsor to modify the investigator’s brochure, informed consent document, or would prompt other action by the IRB to assure protection of subjects. |
Within 10 working days of knowledge or notification |
Any other “Serious” Event/Problem not described above |
Within 10 working days of knowledge or notification |
When an investigator determines that a Safety Report or other notification from a collaborating site constitutes an SEP that is unanticipated and related or possibly related to participation in the research or is otherwise associated with the research, the investigator is responsible for submitting to the IRB the following information along with a copy of the off-site report (e.g., a Med-Watch, IND safety report, or other form of notification) within 5 working days of investigator knowledge or notification:
The following types of “non-serious” events/problems must be reported to the IRB using the Amendment Form, as they occur, according to the instructions in the chart below:
Non-serious events that did not effect the study or impact on the rights and welfare of the subjects are not required to be reported to the IRB.
Investigators are responsible for reporting “non-serious” events and problems according to the nature of the event/problem and according to the manner and timeframes indicated on the Chart below:
| Type of Report | When to Report | How to Report |
| “Non-serious” events/ problems that required changes in order to prevent future occurrences | As they occur. | Amendment Form |
| “Non-serious” events/ problems that impacted on subjects rights or welfare | As they occur. | Amendment Form |
| “Non-serious” events/problems that DID NOT require changes to the study and DID NOT impact on subject rights or welfare | Not necessary to report to the IRB | Not necessary to report to the IRB |
|
Chris Marks IRB Administrator Contact |