Timelines and Responsibilities for Safety Reporting

Part of Good Clinical Practice (GCP) — ICH E6(R3): Safety Reporting and Pharmacovigilance.

About 7 minutes. Free, in your language, no account needed.

Why this matters

A late safety report delays a signal that could protect participants at every other site in the trial. Late reporting is also one of the findings inspectors look for first, because the dates are easy to check. Many sites are taught a single number and cannot say where it comes from.

Three layers of obligation — keep them separate

Safety reporting timelines come from three different places. Confusing them is the most common error in GCP training.

Never say "ICH E6(R3) requires SAE reporting within 24 hours". It does not. The guideline says immediately, and your protocol turns that into an operational deadline.

What the investigator must report

E6(R3) §2.7.2(a) covers routine safety data. Adverse events and abnormal test results required for safety evaluations "should be reported to the sponsor according to the reporting requirements and within the time periods specified in the protocol". The same paragraph adds that unfavorable medical events occurring before investigational product administration, for example during screening, should be considered and reported to the sponsor if the protocol requires it.

E6(R3) §2.7.2(b) covers serious events:

"All serious adverse events (SAEs) should be reported immediately (after the investigator reasonably becomes aware of the event) to the sponsor. The investigator should also include an assessment of causality."

Two details matter. The clock starts when the investigator reasonably becomes aware, not when the event occurred. And a causality assessment must accompany the report.

The same paragraph allows an exception. In accordance with applicable regulatory requirements, the protocol may identify SAEs that do not require immediate reporting, for example deaths or other events that are trial endpoints. Follow-up reports are submitted as necessary.

E6(R3) §2.7.2(c) covers deaths. The investigator supplies the sponsor, the IRB/IEC and, where applicable, the regulatory authority with any additional requested information, such as autopsy reports and terminal medical reports, when it becomes available.

E6(R3) §2.7.2(d) covers delegation. The investigator may delegate safety reporting activities to qualified site staff, but retains overall responsibility for participant safety and for compliance with the reporting requirements. Responsibility cannot be delegated.

What the sponsor must do

Review (§3.13.1). The sponsor should aggregate, as appropriate, and review relevant safety information in a timely manner, including unfavorable medical events occurring before investigational product administration. The review may lead to updates of the protocol, the Investigator's Brochure and the informed consent materials. The sponsor also assesses whether emerging safety information may affect a participant's willingness to continue, and communicates such information to participants, investigators, IRBs/IECs and regulatory authorities.

Reporting (§3.13.2). The named obligations are:

• (a) Submit safety updates and periodic reports to regulatory authorities, including changes to the Investigator's Brochure, as required by applicable regulatory requirements.
• (b) Expedite reporting of all suspected, unexpected and serious adverse reactions (SUSARs) to regulatory authorities, in line with applicable requirements and with ICH E2A.
• (c) Assess expectedness against the applicable product information, for example the reference safety information (RSI) in the Investigator's Brochure. The guideline points to ICH E2F for more about the RSI.
• (d) Report SUSARs to investigators and IRBs/IECs "in a manner that reflects the urgency of action required". In some regions, periodic reporting of line listings with an overall safety assessment may be appropriate.
• (e) Report urgent safety issues requiring immediate attention or action to the IRB/IEC and/or regulatory authorities and investigators "without undue delay".
• (f) Agree any alternative safety reporting arrangements prospectively with the regulatory authority and, if applicable, the IRB/IEC, and describe them in the protocol. The example given is SAEs that are efficacy or safety endpoints, which would not be subject to unblinding and expedited reporting. The guideline cross-refers to ICH E2A and ICH E19.

Paragraph (f) is worth pausing on. In a trial where death is the primary endpoint, reporting every death as an expedited SAE would add noise and could break the blind. E6(R3) permits a different arrangement, but only if it is agreed with the authority in advance and written into the protocol. A site cannot invent this arrangement locally.

Immediate hazard

E6(R3) §3.13.3 requires the sponsor to take prompt action to address immediate hazards to participants, to determine the causes, and to take appropriate remedial action. The sponsor considers whether the protocol needs amendment. Information on the hazard and any amendment is submitted to the IRB/IEC and/or regulatory authorities by the investigator, the institution or the sponsor, according to applicable regulatory requirements.

On the site side, E6(R3) §2.5.4 allows the investigator to deviate from the protocol only where necessary to eliminate an immediate hazard, and requires the sponsor to be informed promptly.

In practice

Priya is a coordinator. On Tuesday at 16:00 a participant's spouse telephones to say the participant was admitted to another hospital on Sunday with gastrointestinal bleeding.

The clock starts on Tuesday at 16:00, when the site reasonably became aware. It does not start on Sunday. Priya records the date and time of awareness in the source, because that is what an inspector will check the report against.

The site then follows a seven-step workflow:

1. Identify — confirm the event meets a seriousness criterion. Inpatient hospitalization does.
2. Document — participant code, event description, onset date, date of awareness, severity, seriousness criterion, medical history, concomitant medications, action taken and outcome.
3. Notify the investigator — Dr. Sarah reviews the case and makes the causality assessment required by §2.7.2(b). She does not delegate the medical judgment.
4. Report to the sponsor — immediately, using the channel and deadline the protocol specifies. This protocol says within 24 hours of awareness, so the report goes on Tuesday evening.
5. Follow up — obtain the discharge summary and endoscopy report; submit a follow-up report.
6. Review and analyze — the sponsor assesses expectedness against the RSI and decides whether this is a SUSAR requiring expedited reporting to authorities.
7. Maintain communication — the site keeps the participant informed and reconciles the safety database against the data acquisition tool.

Notice which layer supplied the 24 hours. The protocol did. E6(R3) supplied the word "immediately".

Report the date you knew, not the date you finished the paperwork.

Key takeaways

• E6(R3) §2.7.2(b) requires all SAEs to be reported to the sponsor immediately after the investigator reasonably becomes aware, and it states no number of hours.
• The common 24-hour SAE deadline is a protocol or sponsor convention, and the 7-day and 15-day expedited clocks are regional regulation; neither may be attributed to ICH E6(R3).
• The investigator must include an assessment of causality with every SAE report, and may delegate reporting tasks while retaining overall responsibility.
• A protocol may exempt specified SAEs from immediate reporting, for example events that are trial endpoints, but under §3.13.2(f) such arrangements must be agreed prospectively with the regulatory authority and described in the protocol.
• The sponsor expedites SUSAR reporting in line with ICH E2A, assesses expectedness against the reference safety information described in ICH E2F, and reports urgent safety issues without undue delay.
• Under §3.13.3 the sponsor must act promptly on an immediate hazard, determine its causes, take remedial action and consider whether the protocol requires amendment.