What’s the shortest reporting window you’ve had to meet for serious unexpected events — 24 hours to sponsor, then 7 days for the full follow-up? On a Phase II oncology study in 2022, we pre-populated MedWatch 3500A fields from the EDC to hit the clock without compromising data quality; curious what tricks others used to keep patients safe while staying compliant…
On a Phase Ib CNS study, we built an SAE fast-lane in the EDC that auto-fired a stub E2B to the sponsor within 2 hours using a pre-approved “minimum dataset” and documenting the phone PI attestation as the “time of initial awareness”; the full CIOMS went out in 72 hours. The only gotcha was ring-fencing PHI and disabling auto-attachments so source docs didn’t leak early. I’m curious whether you’ve used verbal PI attestation to stop the clock while maintaining auditability.
We had a 6‑hour sponsor clock on a cell therapy pilot and made it by adding an EMR smart‑phrase that auto‑pulls last vitals, labs, and concomitants into a time‑stamped one‑paragraph SAE note we pasted straight into the initial ICSR. Small caveat: we locked the phrasing to “facts only” and deferred assessments to the follow‑up to avoid versioning headaches. Anyone tried this vs EDC pre‑pop, @DataSafetyNerd?
Shortest was a 12‑hour clock, , and the only way we hit it was pre‑delegating after‑hours SAE submission to the sub‑I and giving them a mobile “3500A‑lite” REDCap form that spit out a time‑stamped PDF if the EDC hiccuped. We also set a 30‑minute Teams page to pharmacy and the safety nurse to confirm lot and seriousness before sending, then the PI cosigned by morning. @henry7246 did you ever try pre‑delegation like that, or did your auto‑stub cover overnight gaps?
8-hour clock on a device feasibility; we used an SAE pager rotation and a 15-line Teams template and train staff to ‘send now, reconcile later’ so the initial goes to the sponsor in minutes, then we build out the 3500A from source the same day — it felt like a fire drill but worked. Small caveat: we freeze the AE verbatim and dosing status at notification after a 60-second PI check to prevent drift, which keeps compliance tidy.
Think ‘SAE go-bag’ in eSource — demographics, product/lot, and safety contacts prefilled plus a macro that drops an ICH E2A narrative shell — so the on-call just marks the time, adds the event, and sends; caveat: we still require a 10‑min sub‑I check right after to keep us honest. @emmthom did you bake phone-in initials into your SOP?
Any tips standardizing abbreviations? ‘Pre-populated MedWatch 3500A’ here too; EDC hotkey auto-emails sponsor.
We ran a ‘minimum dataset’ rule: as soon as we had patient initials, event term, suspect product, and reporter, we fired an E2B(R3) stub to the sponsor to hit the ‘24h to sponsor/7d follow-up’. Does their safety team accept a gateway or API? EDC then backfilled the MedWatch 3500A via XML so the narrative was written once.
Follow-the-sun safety rota with SMS escalation; ‘zero-hour’ mobile stub — @Jae, do you have 24/7 coverage?
Shortest was a 12‑hour-to-sponsor clock on a vaccine study; we put a “batphone” in the ward and trained nurses to call the sponsor PV line immediately so the hotline call log anchored the ‘clock starts at awareness,’ then uploaded a one-page stub to the portal minutes later. @lhill81 have you had sponsors accept voice-first notice as time-zero, or did they insist on email/gateway?