Sign inJoin Free
DashboardSign out
Regulatory Coordinator
Full course · Safety Reporting Coordination
Regulatory Coordinator
Full course · Safety Reporting Coordination
Free Lesson Preview
Module 1: Lesson 1

Construct annual safety summaries that aggregate AE data, enrollment status, deviation trends, and sponsor communications into each IRB's required format, design a portfolio-level annual reporting calendar, and evaluate common deficiencies that delay continuing review approval.
The previous three lessons taught you to manage safety events one at a time. A serious adverse event occurs -- you classify it, determine reportability, prepare the submission, track it through the IRB's response cycle. That event-driven workflow is essential. But it is incomplete.
Once a year -- sometimes more frequently -- the IRB steps back from individual events and asks a different question entirely. Not "what happened to this participant?" but "given everything that has happened across all participants, should this study continue?"
That question is answered by the annual safety summary, and the data it contains is the single most important body of information the IRB uses to make its continuing review determination. An incomplete summary does not just create a compliance finding. It delays continuing review approval. And a delayed approval stops enrollment -- sometimes for weeks, sometimes indefinitely, depending on the IRB's queue and the severity of the deficiency.
I have seen this happen more often than I would like to admit. A site with an otherwise excellent compliance record submits an annual safety summary that omits a class of adverse events because the data pull used the wrong date range. The IRB returns the submission with a query. The query takes two weeks to resolve. Continuing review approval is delayed by a month. Enrollment is suspended for 34 days. Three participants who would have been screened during that window are lost to a competing trial. The scientific and commercial consequences of that month-long delay vastly exceed anything the individual event reports could have caused.
This lesson teaches you to build the annual safety summary correctly the first time. It also teaches you something the event-by-event lessons could not: how to manage the reporting calendar across an entire portfolio, so that you are never surprised by a continuing review deadline.
By the end of this lesson, you will be able to:
Continue with the Regulatory Coordinator track
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full courseFree Lesson Preview
Module 1: Lesson 1

Construct annual safety summaries that aggregate AE data, enrollment status, deviation trends, and sponsor communications into each IRB's required format, design a portfolio-level annual reporting calendar, and evaluate common deficiencies that delay continuing review approval.
The previous three lessons taught you to manage safety events one at a time. A serious adverse event occurs -- you classify it, determine reportability, prepare the submission, track it through the IRB's response cycle. That event-driven workflow is essential. But it is incomplete.
Once a year -- sometimes more frequently -- the IRB steps back from individual events and asks a different question entirely. Not "what happened to this participant?" but "given everything that has happened across all participants, should this study continue?"
That question is answered by the annual safety summary, and the data it contains is the single most important body of information the IRB uses to make its continuing review determination. An incomplete summary does not just create a compliance finding. It delays continuing review approval. And a delayed approval stops enrollment -- sometimes for weeks, sometimes indefinitely, depending on the IRB's queue and the severity of the deficiency.
I have seen this happen more often than I would like to admit. A site with an otherwise excellent compliance record submits an annual safety summary that omits a class of adverse events because the data pull used the wrong date range. The IRB returns the submission with a query. The query takes two weeks to resolve. Continuing review approval is delayed by a month. Enrollment is suspended for 34 days. Three participants who would have been screened during that window are lost to a competing trial. The scientific and commercial consequences of that month-long delay vastly exceed anything the individual event reports could have caused.
This lesson teaches you to build the annual safety summary correctly the first time. It also teaches you something the event-by-event lessons could not: how to manage the reporting calendar across an entire portfolio, so that you are never surprised by a continuing review deadline.
By the end of this lesson, you will be able to:
Continue with the Regulatory Coordinator track
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full course