The 24-Hour Clock That Started on a Friday
A Phase II oncology study is enrolling at a community site. On Friday 14 March, sub-investigator Dr. Okafor documents in the source that subject 1042 was admitted the previous evening with febrile neutropenia (ANC 0.4 x 10^9/L, temperature 38.6 C) and ALT 4.8 x ULN; the last dose of study drug was taken on 11 March. The coordinator who normally handles safety reports is on medical leave, so the SAE form is faxed to the sponsor on Monday 17 March at 09:00. The protocol lists febrile neutropenia as an adverse event of special interest and requires SAE reporting within 24 hours of site awareness. The IRB's written policy requires reporting of unanticipated problems within five working days. The investigator tells the CRA, "It's probably the drug, but he's back on it next week."
1. When did the site's reporting clock start, and what are the consequences of the 17 March fax? What must the CRA do now?
Read the worked answer
The clock runs from site awareness, not from when the event clinically began. Any site staff member learning of the event triggers it; here that is 13 or 14 March, not 17 March. A 24-hour protocol window therefore closed on 15 March at the latest, making the 17 March fax roughly two days late.
- A late SAE report is a protocol deviation. It must be entered in the deviation log with root cause (uncovered absence of the trained safety reporter) and a PI-signed assessment of impact on subject safety and data validity.
- The reason explains but does not excuse the delay. The site needs a corrective action: trained backup reporter, after-hours sponsor contact route, and a documented handover when the primary coordinator is out.
- The CRA verifies the sponsor acknowledged receipt, records the finding in the monitoring report, and confirms a follow-up report is scheduled.
- Critically, the CRA should request a backlog review of all subjects for the leave period to check whether other events, AESIs, or concomitant medication changes went unreported. One missed report is a deviation; an unchecked backload is a site-quality problem.
- Confirm the event was also entered in EDC within the required window, since the paper form and the database must agree.
2. The investigator plans to restart study drug next week. How should the CRA handle causality, expectedness, and the restart?
Read the worked answer
Three different judgments are being conflated and each belongs to a different party.
Causality is the investigator's call, documented on the SAE form with a rationale. 'Probably the drug' is an acceptable assessment, but it must be written down and updated with dechallenge information (drug stopped 11 March, event onset 13 March). Verbal impressions have no evidentiary value.
Expectedness is judged by the sponsor against the Investigator's Brochure or reference safety information, not by the site. The site's obligation is to supply full information (drug start/stop dates, concomitant myelosuppressive agents, baseline counts) so the sponsor can classify it. Because febrile neutropenia is a protocol-defined AESI, it is reportable regardless of expectedness determination.
Restart cannot be authorised by the CRA. The CRA directs the investigator to the protocol's dose-modification and treatment-interruption rules and requires a documented discussion with the sponsor medical monitor. If the event recurs on rechallenge, that follow-up information is reportable and may change the sponsor's expectedness assessment.
Finally, if the IB or the informed consent form is updated with this information, the site must check whether re-consent is required.
3. What documentation and notifications must be complete before the next monitoring visit?
Read the worked answer
Minimum package to close the loop:
- Follow-up SAE form with outcome, discharge summary, repeat labs (including nadir and recovery ANC, LFTs), all concomitant medications, and dechallenge/rechallenge status.
- EDC AE/SAE pages updated to match the paper report; any discrepancy becomes a query and is resolved, not silently overwritten.
- Deviation log entry for the late submission, PI-assessed, with the CAPA and a target date.
- IRB submission of the unanticipated problem within the IRB's five-working-day policy, with proof of submission filed in the regulatory binder.
- Sponsor acknowledgement and the sponsor's expectedness/expedited-reporting decision filed with the SAE correspondence.
- Consent review: confirm the subject's current consent version still covers the risks described, and document any re-consent discussion.
- Monitoring report describing the finding, the escalation, and the follow-up items for the next visit, with each item tracked to closure rather than assumed resolved.