The safety reporting ecosystem from the RC's chair

4 lessons · 3 hours

Required

Conceptual illustration of the safety reporting pipeline showing six stakeholders connected by directional flows of safety information from initial documentation to regulatory destinations

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

Map the complete safety reporting pipeline at an investigator site, tracing how safety information flows from initial documentation through investigator assessment to sponsor, IRB, and regulatory authority destinations.

Preview22 min

Conceptual illustration of three distinct safety reporting roles -- CRC documentation, investigator medical assessment, and RC regulatory coordination -- converging at a single safety event with clear boundary lines separating their domains

1.2 The RC's specific responsibilities vs. the CRC's and the investigator's: drawing clear lines

24 min

Delineate the three distinct safety reporting roles at an investigator site and apply ICH E6(R3) delegation provisions to determine which activities the RC coordinates, which the CRC executes, and which only the investigator can perform.

24 min

Conceptual illustration of three regulatory frameworks (ICH E6(R3), 21 CFR 312.32, 45 CFR 46) converging on a single investigator site, with overlapping obligation zones meeting at the regulatory coordinator's desk

1.3 Regulatory requirements driving site-level safety reporting: ICH E6(R3), 21 CFR 312.32, and 45 CFR 46

Preview25 min

Analyze the three regulatory frameworks that generate site-level safety reporting obligations, mapping each requirement to specific RC tasks and constructing a regulatory requirements matrix for daily reference.

Preview25 min

Conceptual illustration of safety reporting infrastructure showing a central tracking system with status indicators, alert thresholds, and three-tier escalation pathways connecting multiple study nodes

1.4 Building the safety reporting infrastructure: systems, timelines, and escalation paths

24 min

Design the tracking systems, alert thresholds, and escalation protocols that translate regulatory obligations into operational infrastructure capable of preventing safety reporting failures across a multi-study portfolio.

24 min

Safety Reporting Coordination

What you'll be able to do

6 comprehensive modules

The safety reporting ecosystem from the RC's chair

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

1.2 The RC's specific responsibilities vs. the CRC's and the investigator's: drawing clear lines

1.3 Regulatory requirements driving site-level safety reporting: ICH E6(R3), 21 CFR 312.32, and 45 CFR 46

1.4 Building the safety reporting infrastructure: systems, timelines, and escalation paths

Processing sponsor safety communications

2.1 Types of sponsor safety communications: IND safety reports, IB updates, DSMB recommendations, and dear investigator letters

IRB safety reporting and unanticipated problems

3.1 What the IRB wants to know: unanticipated problems, serious adverse events, protocol deviations, and safety summaries

Investigator safety assessment coordination

4.1 Supporting the investigator's safety assessment: what information they need and when they need it

Safety reporting across the portfolio

5.1 The safety reporting calendar: mapping reporting deadlines across the portfolio

Safety communication deliverables and process improvement

6.1 Writing effective safety communications: clarity, completeness, and urgency calibration

Ready to begin Safety Reporting Coordination?

Safety Reporting Coordination

What you'll be able to do

6 comprehensive modules

The safety reporting ecosystem from the RC's chair

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

1.2 The RC's specific responsibilities vs. the CRC's and the investigator's: drawing clear lines

1.3 Regulatory requirements driving site-level safety reporting: ICH E6(R3), 21 CFR 312.32, and 45 CFR 46

1.4 Building the safety reporting infrastructure: systems, timelines, and escalation paths

Processing sponsor safety communications

2.1 Types of sponsor safety communications: IND safety reports, IB updates, DSMB recommendations, and dear investigator letters

IRB safety reporting and unanticipated problems

3.1 What the IRB wants to know: unanticipated problems, serious adverse events, protocol deviations, and safety summaries

Investigator safety assessment coordination

4.1 Supporting the investigator's safety assessment: what information they need and when they need it

Safety reporting across the portfolio

5.1 The safety reporting calendar: mapping reporting deadlines across the portfolio

Safety communication deliverables and process improvement

6.1 Writing effective safety communications: clarity, completeness, and urgency calibration

Ready to begin Safety Reporting Coordination?

2.2 Triage and review: determining which communications require investigator action, IRB submission, or consent revision

2.3 Managing the volume: tracking systems for inbound safety communications across the portfolio

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

3.2 Reportable events definitions: the OHRP framework and how IRBs interpret it

3.3 Preparing and submitting IRB safety reports: timelines, formats, and completeness standards

3.4 Annual safety summaries and periodic reporting: the data the IRB uses to decide whether your study continues

4.2 Documenting the investigator's medical judgment: creating traceable records of causality and expectedness assessments

4.3 Annual and cumulative safety reviews: preparing the data for the investigator's aggregate safety assessment

4.4 Managing investigator availability: what happens when the PI is unreachable and a safety report is due

5.2 Cross-study safety trends: when the same safety signal appears in multiple studies at your site

5.3 Safety reporting metrics: tracking timeliness, completeness, and compliance across the portfolio

5.4 Building a safety reporting culture at the site: the RC's role in making safety everyone's priority

6.2 Safety reporting process audits: identifying gaps before they become findings

6.3 Trend analysis and process improvement: using your own data to make safety reporting better

6.4 The RC as safety reporting champion: leading by example and building institutional commitment

2.2 Triage and review: determining which communications require investigator action, IRB submission, or consent revision

2.3 Managing the volume: tracking systems for inbound safety communications across the portfolio

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

3.2 Reportable events definitions: the OHRP framework and how IRBs interpret it

3.3 Preparing and submitting IRB safety reports: timelines, formats, and completeness standards

3.4 Annual safety summaries and periodic reporting: the data the IRB uses to decide whether your study continues

4.2 Documenting the investigator's medical judgment: creating traceable records of causality and expectedness assessments

4.3 Annual and cumulative safety reviews: preparing the data for the investigator's aggregate safety assessment

4.4 Managing investigator availability: what happens when the PI is unreachable and a safety report is due

5.2 Cross-study safety trends: when the same safety signal appears in multiple studies at your site

5.3 Safety reporting metrics: tracking timeliness, completeness, and compliance across the portfolio

5.4 Building a safety reporting culture at the site: the RC's role in making safety everyone's priority

6.2 Safety reporting process audits: identifying gaps before they become findings

6.3 Trend analysis and process improvement: using your own data to make safety reporting better

6.4 The RC as safety reporting champion: leading by example and building institutional commitment