Sign inJoin Free
DashboardSign out
Regulatory Coordinator2 of 6
Free Lesson Preview
Module 1: Lesson 1
Clinical holds, information requests, and safety reports: when regulatory authority actions reach your site
Analyzes regulatory authority actions affecting the investigator site, designs a site-level clinical hold response protocol, and evaluates the RC's coordination role versus PI and sponsor decision-making authority during regulatory events.
The call that changes the afternoon
It starts with a phone call or an email from the sponsor's medical monitor. Sometimes it arrives at 2:00 PM on a Tuesday, with plenty of time to respond. Sometimes -- and this is the scenario that tests your systems -- it arrives at 4:30 PM on a Friday.
The message is concise: the FDA has placed a clinical hold on the IND. Or: the FDA has requested additional safety information. Or: new safety data requires immediate notification to all investigators.
What happens next at your site depends on two things. First, whether you have a response protocol that tells you exactly what to do, in what order, and by whom. Second, whether you understand where your coordination authority ends and the principal investigator's decision-making authority begins. The RC who confuses these boundaries during a regulatory event creates problems that outlast the event itself.
This lesson is not about what clinical holds are. You already know that. This lesson is about what happens at your site when one arrives -- the operational coordination, the authority boundaries, the documentation trail, and the portfolio implications when a regulatory action on one study consumes the RC's attention at the expense of the other 14.
What you will learn
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