The safety reporting pipeline: who generates safety data, who processes it, and who receives it

What happens after the coordinator clicks "submit"

A participant in a Phase III oncology trial develops grade 3 hepatotoxicity on a Tuesday afternoon. The clinical research coordinator documents the event. The investigator assesses causality. Within 24 hours, the sponsor receives an initial serious adverse event report. Within 15 calendar days -- sometimes sooner, depending on the regulatory framework -- the sponsor determines whether this event qualifies as a suspected unexpected serious adverse reaction and, if so, transmits an expedited report to the relevant regulatory authority. Meanwhile, the study site must ensure the IRB receives notification if required by the protocol or the IRB's own reporting policies.

That sequence, from bedside observation to regulatory authority desk, is the safety reporting pipeline. And somewhere in that pipeline -- at the junction where information flows outward from the site to multiple destinations simultaneously -- sits the regulatory coordinator.

This lesson maps that pipeline end to end. Not the clinical judgments within it (those belong to the investigator) and not the per-event documentation that feeds it (that belongs to the CRC). What we are mapping here is the system -- the architecture of information flow that the RC must understand, manage, and protect from failure. Because when this pipeline breaks, the consequences range from regulatory findings to compromised participant safety. Often both.

Tracing a serious adverse event from bedside to regulatory authority

Before we dissect the pipeline into its component parts, I want you to hold a single event in your mind and follow it through the entire system. This is the mental model that will anchor everything else in the course.

A participant enrolled in a multi-site clinical trial experiences a serious adverse event -- an unexpected hospitalization. Here is what happens, step by step, at the investigator site:

Step 1. The clinical research coordinator becomes aware of the event (through direct observation, participant contact, or medical record review) and documents it according to the protocol's safety reporting requirements. The CRC captures the clinical details: onset date, description, severity, outcome, and any concomitant medications or relevant medical history.

The investigator reviews the CRC's documentation and makes the medical assessments that only a physician-investigator can make: Is this event serious? Is it expected based on the Reference Safety Information in the Investigator's Brochure? Is there a reasonable possibility of a causal relationship to the investigational product? Per ICH E6(R3) Annex 1, Section 2.7.2(b), the investigator should include an assessment of causality, and per Section 2.7.2(d), the investigator retains overall responsibility for participant safety even when delegating safety reporting activities. These medical assessments require physician qualifications and should not be performed by non-physician site staff.

The six stakeholders: what each one generates, processes, and receives

The pipeline has six stakeholders, and each one occupies a distinct role. I have found that the most common source of confusion among new regulatory coordinators is treating this pipeline as a linear chain when it is, in fact, a network with branching paths. The information does not simply pass from one person to the next in sequence. It branches. It sometimes loops back. And at the RC's position, it must be routed to multiple destinations simultaneously.

Let me be precise about what each stakeholder does within the pipeline.

Information flows: what travels between stakeholders

Understanding the stakeholders is necessary but not sufficient. The RC must also understand what information moves along each connection in the pipeline. This is not academic -- when a monitor asks "Can you show me documentation that the PI received and reviewed this safety letter?", the RC who understands the information flows can produce that documentation immediately.

The three critical handoff points

A pipeline is only as strong as its weakest joint. In safety reporting, the joints are the handoff points -- the moments where information must transition from one person's responsibility to another's. Each handoff requires documentation that proves the information was transferred, received, and acted upon.

I want to be direct about this: in my experience reviewing inspection findings across hundreds of investigator sites, the single most common category of safety reporting deficiency is not the clinical content of the report. It is the handoff. Information was generated but not transmitted. Information was transmitted but not documented. Information was received but not acted upon. The pipeline leaked at the joints.

There are three handoff points that the RC must understand -- and, in many cases, directly manage.

Handoff 1: CRC to investigator

The CRC documents the event. The investigator must review that documentation and add the medical assessment. This handoff requires:

What must transfer: Complete event documentation -- clinical description, onset date, severity, outcome, relevant medical history, and concomitant medications. The investigator cannot assess causality without this information.

Documentation requirement: Evidence that the investigator received the CRC's documentation, reviewed it, and rendered a medical judgment. This typically takes the form of a signed and dated SAE report form that includes both the CRC's clinical narrative and the investigator's causality assessment.

When the CRC completes the event documentation but the investigator does not review it promptly. Per Section 2.7.2(b), SAEs should be reported to the sponsor "immediately (after the investigator reasonably becomes aware of the event)." A delay at this handoff directly delays sponsor reporting and, consequently, delays the entire downstream pipeline.

When the pipeline breaks: three failure scenarios

Understanding the pipeline is one thing. Understanding what happens when it breaks is another. Not all failures carry the same consequences. Some create regulatory findings. Some compromise participant safety. And some -- the most serious -- do both. The RC who can distinguish between these failure types is better equipped to build systems that prevent the most consequential ones.

Failure 1: Delayed follow-up report to the sponsor (regulatory finding)

An initial SAE report is submitted to the sponsor within 24 hours. But the hospital discharge summary, which contains important outcome information, arrives at the site three weeks later and is filed in the medical record without being forwarded to the sponsor as a follow-up report.

What broke: Handoff 2. The follow-up information was available at the site but not transmitted to the sponsor.

Regulatory consequence: This is a documentation and reporting deficiency. Per Section 2.7.2(b), subsequent information should be submitted as follow-up reports "as necessary." A monitor or auditor reviewing the site's safety records would identify this gap. It would likely appear as a finding on a monitoring visit report and, in an inspection, could appear as a Form 483 observation.

In most cases, minimal. The initial report was timely, so the sponsor was aware of the event. The delayed follow-up affects the completeness of the sponsor's safety database but does not, by itself, compromise participant safety at the reporting site.

The RC's position in the pipeline

By now you can see where the RC sits: at the coordination junction. The RC does not generate the safety data (the CRC does that) and does not make the medical assessments (the investigator does that). The RC ensures that once safety information exists and has been medically assessed, it reaches every destination it needs to reach, on time, with documentation proving it got there.

This is, in my view, one of the most underappreciated roles in clinical research. The RC's contribution is invisible when the pipeline works and catastrophic when it does not. A well-functioning safety reporting pipeline is evidence that an RC is doing their job. You will never see a headline reading "Regulatory coordinator ensures timely IRB notification of SUSAR." But you will see FDA warning letters citing failure to do exactly that.

In the next lesson, we will draw the precise boundaries between the RC's responsibilities, the CRC's responsibilities, and the investigator's responsibilities in this pipeline. Before you can build the infrastructure to manage safety reporting across a portfolio, you need to know -- with precision -- which parts of the pipeline are yours.