The SAE That Arrived on a Friday Afternoon
It is 4:40 pm Friday. A site coordinator calls the safety hotline to report that Subject 2011 in your Phase III sepsis trial was hospitalized 36 hours ago with acute respiratory failure. The subject is on active IP. The coordinator says the PI is unavailable until Monday and "wanted to wait until he could review it." The site's own SOP says SAEs are reported to the sponsor within 24 hours of site awareness. The coordinator became aware Thursday morning. The subject's randomization code is blinded; the Medical Monitor is reachable by phone tonight. You also learn the subject had a similar respiratory event 8 months ago, before enrollment, which was not captured on the medical history form.
1. Walk through your reporting obligations and timeline.
Read the worked answer
The clock started Thursday morning - when the site became aware, not when the PI was available. The site is now ~36 hours past awareness and past its own 24-hour SOP. That is a site deviation to document, but your obligation is triggered by your awareness, which is now.
Tonight (Friday):
- Contact the Medical Monitor - this is why he is reachable. Get a preliminary causality and expectedness assessment. You cannot finalize without the PI, but you can begin.
- Open the SAE record with the information you have: onset, event term (acute respiratory failure), subject on active IP, blinded. Do not wait for a complete narrative to start the clock on your side.
- Determine the regulatory reporting pathway once causality/expectedness are assessed:
- If suspected + unexpected + serious → IND safety report to FDA within 15 calendar days (7 days if fatal or life-threatening).
- Fatal/life-threatening suspected unexpected events → 7-day clock.
- Notify the IRB per its policy and all participating investigators if it's an IND safety report.
- Unblinding decision: Do not unblind reflexively. The Medical Monitor decides whether unblinding is needed for the safety assessment; if it is, follow the blind-break SOP and document who unblinded and why.
Monday: PI completes the causality assessment and the narrative is finalized. The regulatory clock, however, did not wait for Monday.
2. How do you handle the missing pre-enrollment respiratory event, and what does it change?
Read the worked answer
It changes the expectedness and causality analysis, and it's a separate finding.
- For the SAE assessment: A prior similar respiratory event means the current event may be a recurrence of underlying disease rather than drug-related. That informs the Medical Monitor's causality judgment - but it does not let you downgrade reporting on your own. The assessment is documented by the investigator and Medical Monitor; you facilitate, you don't decide.
- For the protocol/deviation side: A pre-existing condition omitted from medical history is an eligibility and data-integrity issue. Was the subject eligible? Did the omission affect randomization or stratification? This needs a deviation report and a review of whether the subject should continue.
- For the site: The omission plus the delayed SAE report suggest a site-level quality problem. Issue a finding, require a CAPA, and consider whether the site needs retraining on SAE reporting and medical history capture.
Do not let the missing history become a reason to delay the SAE report. Report what you know, flag the history as pending, and update the narrative when the PI confirms. A late report with a caveat is better than a withheld report.
Judgment point: The PI's instinct to "wait until he could review it" is the exact failure mode SAE timelines exist to prevent. Your job is to make clear - to the site and in your documentation - that awareness triggers the clock, not investigator availability.