Regulatory Coordinator

Full course · Safety Reporting Coordination

Investigator notification and acknowledgment: ensuring the PI reviews what must be reviewed — Safety Reporting Coordination

Investigator notification and acknowledgment: ensuring the PI reviews what must be reviewed

Design an investigator notification workflow that routes sponsor safety communications to the correct PI, escalates unacknowledged items on defined timelines, and documents the notification-acknowledgment cycle per ICH E6(R3) Sections 2.7.2(d) and 3.13.2(d).

22 min

Three investigators, 14 studies, and a Wednesday afternoon

Picture a site running 14 active clinical trials under three principal investigators. On a single Wednesday in April, the RC's inbox contains nine sponsor safety communications: two IND Safety Reports for one investigator's oncology trials, an Investigator's Brochure update affecting three studies under two different investigators, a DSMB continuation recommendation for a cardiovascular outcomes study, and three IND Safety Reports for studies spanning two of the three investigators.

Each of those nine communications has been through the four-gate triage from Lesson 2. Each has an intake log entry and a tracking ID from Lesson 3. The system knows what arrived, when, from whom, and what actions are required.

But here is the question the system cannot answer by itself: has the right investigator actually seen each communication? Has the principal investigator for the cardiovascular study reviewed the DSMB recommendation? Has the oncology PI read the two IND Safety Reports containing new safety signals in the drug class she is administering to 23 enrolled participants? And if she has read them -- can you prove it?

This is the problem of investigator notification and acknowledgment. It sounds administrative. It is not. The investigator's review of sponsor safety communications is a regulatory obligation grounded in ICH E6(R3) Annex 1, Section 2.7.2(d), which requires that the investigator be informed of safety findings that could affect participant safety. The site's ability to demonstrate that this notification occurred -- and that the investigator acknowledged it -- is a fundamental element of the regulatory record. A tracking system full of communications triaged and logged but never documented as reviewed by the investigator is a system that looks complete from the RC's perspective but fails the regulatory test.

In Lesson 3, you built the intake log and status tracking workflow with six defined stages. Stage 3 -- "Notified" -- is where the investigator enters the workflow. This lesson operationalizes that stage. It builds the routing logic, the acknowledgment documentation, the escalation timelines, and the contingency procedures that ensure every communication reaches the correct investigator at the appropriate urgency level -- and that the site can prove it.

What you will learn3 objectives

By the end of this lesson, you will be able to:

Design an investigator notification workflow that routes sponsor safety communications to the correct PI, escalates unacknowledged items, and documents the notification-acknowledgment cycle
Apply the distinction between communications requiring investigator medical review and those requiring only investigator awareness, calibrating notification urgency accordingly
Construct contingency procedures for investigator notification when the PI is unavailable, ensuring urgent communications reach a qualified sub-investigator

Progress saves itself — finish reading and this lesson completes

Continue with the Regulatory Coordinator track

Three investigators, 14 studies, and a Wednesday afternoon