Regulatory Coordinator
Full course · Safety Reporting Coordination
Free Lesson Preview
View the Regulatory Coordinator track for current pricing and enrollment options.
View enrollment optionsAlready enrolled? Sign in
Coordinate the data assembly process for the investigator's aggregate safety review, design a structured review package with contextual information, and apply a portfolio-level schedule aligning reviews with IRB, sponsor, and investigator timelines.
In Module 3, Lesson 4, you learned to construct the annual safety summary that goes to the IRB. That report exists to answer the IRB's continuing review question: given the aggregate safety experience of this study, should it continue? The audience is a governance body making a regulatory determination. The format is whatever the IRB requires. The deadline is the continuing review date. You built the calendar, you learned the data elements, and you understood what happens when the summary is late or incomplete -- enrollment stops.
This lesson is not about that report. And I want to be direct about why the distinction matters, because I have watched coordinators confuse these two processes more often than any other overlap in the safety reporting pipeline.
This lesson teaches you to assemble the data package that goes to the investigator -- not the IRB, but the physician-scientist who must periodically step back from individual event assessments and evaluate the study's aggregate safety picture. The investigator's aggregate review is a medical assessment. The IRB's continuing review is a governance determination. They draw on overlapping data sources, but they serve fundamentally different purposes, require different contextual information, and operate on different timelines.
The IRB asks: should this study continue? The investigator asks: what does the cumulative safety data tell me about the benefit-risk profile of this investigational product at my site?
The RC assembles the data for both. But the packages are not interchangeable, and treating the investigator's aggregate review as a byproduct of the IRB summary is one of the most common -- and most consequential -- coordination failures I encounter.
What you will learn3 objectives
By the end of this lesson, you will be able to:
Progress saves itself — finish reading and this lesson completes
