Preparing and submitting IRB safety reports: timelines, formats, and completeness standards
Apply IRB-specific timeline requirements to a multi-IRB portfolio, design a pre-submission quality checklist, and construct a submission tracking workflow that links to essential records per ICH E6(R3) Appendix C.
The clock started before you opened this lesson
It is Thursday at 2:15 in the afternoon, and the regulatory coordinator's inbox contains three items that cannot wait until Monday.
The first is a serious adverse event from a cardiovascular trial overseen by a central commercial IRB. The investigator determined yesterday that the event meets all three prongs of the OHRP test -- it is an unanticipated problem. The IRB requires unanticipated problem reports within five business days of the investigator's determination. That deadline is next Thursday.
The second is a protocol deviation from an oncology trial overseen by the site's institutional IRB. A participant received a prohibited concomitant medication for two weeks before the study team discovered it. The institutional IRB requires deviation reports within 10 calendar days. That deadline is next Saturday -- but the IRB portal closes at 5:00 PM on Fridays, which means the functional deadline is eight days from now.
The third is a follow-up report on a previously submitted serious adverse event for a metabolic disease trial overseen by a second central IRB. The IRB requested additional information 12 days ago. Their policy states that follow-up information must be submitted within 15 calendar days. That deadline is Tuesday.
Three reports. Three IRBs. Three different timelines. Three different submission formats. And the Tuesday deadline has one problem the RC noticed only this morning: the investigator's updated assessment -- required for the follow-up submission -- has not been signed.
This is not an unusual Thursday. This is a Thursday for a regulatory coordinator managing a portfolio of 12 or 15 studies. The question is not whether these situations arise. The question is whether the systems you have built allow you to handle them without error.
Lesson 1 classified the four categories of IRB safety reporting. Lesson 2 taught you how to determine whether a specific event is reportable. This lesson teaches the mechanics of what comes next: preparing the report, submitting it correctly, meeting the timeline, and documenting the submission so that the record is complete and auditable. These are not glamorous skills. They are the skills that prevent compliance failures.
What you will learn
By the end of this lesson, you will be able to: