Serious Adverse Events and Reporting

Part of Clinical Research Coordinator (CRC) Training: Participant Safety.

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

Why this matters

A serious adverse event report is the fastest-moving document a site produces. It can change how a trial is run within days, and it can protect participants at sites you will never visit.

It is also the area where sites most often quote a requirement that does not exist. Get the layers right.

Where the deadline actually comes from

Three different layers set expectations, and only one of them is ICH.

E6(R3) section 2.7.2(b) states that all serious adverse events should be reported immediately after the investigator reasonably becomes aware of the event, and that the investigator should include an assessment of causality.

Never say "ICH requires SAE reporting within 24 hours". It does not. Your protocol does.

The same section allows an exception: in accordance with applicable regulatory requirements, the protocol may identify serious adverse events that do not require immediate reporting — for example events that are themselves trial endpoints. Under section 3.13.2(f) such arrangements must be agreed prospectively, in the protocol, and not decided at the time.

When the clock starts

The clock starts when the investigator reasonably becomes aware of the event. Not when the event happened. Not when the paperwork was finished.

This makes one habit essential: record the date and time your site became aware, in the source, at the moment you learn of the event. An inspector will compare that timestamp with the report. If you have not written it down, you cannot defend the timeline.

The workflow

1. Recognize. The event meets a seriousness criterion.
2. Record awareness. Date and time the site learned of it, and from whom.
3. Tell the investigator immediately. Do not wait for the file to be complete.
4. Gather the facts. Participant code, event description and diagnosis, onset date, seriousness criterion met, severity, relevant medical history, concomitant medications, investigational product details including last dose, treatment given, action taken with the product, and outcome to date.
5. Investigator causality assessment. Required by section 2.7.2(b) and not delegable to you.
6. Report to the sponsor by the channel and within the deadline the protocol specifies.
7. Notify the ethics committee where local rules or the protocol require it, and file the acknowledgment.
8. Follow up. Obtain discharge summaries, test results and specialist letters; submit follow-up reports as information arrives.
9. Reconcile. The event in the safety database and the event in the EDC system must match. Expect a reconciliation query and answer it from source.

Deaths and immediate hazards

Deaths have their own handling in E6(R3) section 2.7.2(c), and your protocol will specify what is required, which typically includes any additional information the sponsor requests, such as autopsy reports and terminal medical reports.

Separately, section 3.13.3 requires the sponsor to take prompt action to address immediate hazards to participants. Your site's part in that is speed: an unreported event cannot trigger anything.

What comes back to you

The sponsor assesses whether an event is a suspected unexpected serious adverse reaction, usually shortened to SUSAR: serious, suspected to be related to the product, and not consistent with the reference safety information. SUSARs are reported to regulators on regional clocks.

You will receive safety letters describing events at other sites. These are not junk mail.

• File them in the site file.
• Make sure the investigator reviews them, and record that review with a date.
• Consider whether participants must be told. Sometimes a safety letter leads to a consent form amendment and re-consent.

Common failures

• The event is found in the notes weeks later by a monitor, not reported by the site.
• The seriousness criterion is not recorded, so nobody can see why it was treated as serious.
• Causality is left blank because the investigator was unavailable, and stays blank.
• The site's date of awareness was never written down.
• The event exists in the safety database but not in EDC, or the two disagree.
• Follow-up information is obtained but never submitted.

In practice

On a Tuesday at 16:00, a relative telephones Northside Clinic to say that a VT-201 participant was admitted to hospital on Sunday with gastrointestinal bleeding.

Nadia writes down the date and time of the call immediately, and who called. The clock starts Tuesday at 16:00, not Sunday.

She tells Dr. Osei within the hour. He reviews what is known, records his causality assessment, and the report goes to Vantis Pharma on Tuesday evening — within the 24 hours the protocol specifies.

Over the following week Nadia obtains the discharge summary and the endoscopy report with the participant's permission, and submits a follow-up report. The sponsor assesses expectedness against the reference safety information and decides whether this is a SUSAR.

Three weeks later a data query asks why the adverse event end date in EDC differs from the safety report. Nadia checks source, finds the discharge date was updated after the first report, and answers with the document reference.

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

Key takeaways

• ICH E6(R3) section 2.7.2(b) requires serious adverse events to be reported to the sponsor immediately after the investigator reasonably becomes aware, and states no number of hours.
• The common 24-hour deadline is a protocol or sponsor convention, and 7-day or 15-day expedited clocks are regional regulation; neither may be attributed to ICH.
• The clock starts at site awareness, which is why the date and time of awareness must be recorded in source the moment the site learns of an event.
• The investigator must provide a causality assessment with the report, and this cannot be delegated to the coordinator.
• Safety letters from other sites must be filed, reviewed by the investigator with a dated record, and assessed for whether participants need to be told.