Last week, our community was abuzz with discussions on managing clinical trials more efficiently. Conversations focused on practical challenges, such as the shortest safety clocks experienced by professionals, and the nuances of TMF retention timelines. There was also a notable emphasis on the evolution of risk-based monitoring and its implications for current practices. Members shared insights on navigating protocol changes and the integration of technology in participant communication.
This Week’s Hot Topics
Shortest safety clock you’ve managed
Members are sharing their experiences with managing safety clocks under tight timelines. This is sparking a lot of practical advice on how to handle time-sensitive safety assessments. Read more here
When does the TMF retention clock start
This discussion is clarifying the often-confusing timelines for TMF retention, a crucial aspect for compliance and audits. Read more here
Which ICH E6 revision added RBM
There’s a deep dive into the specific ICH E6 revisions that introduced risk-based monitoring, a key shift in clinical trial management. Read more here
Helping participants through protocol changes
Participants are discussing strategies to effectively guide trial participants through protocol amendments, ensuring clarity and compliance. Read more here
Streamlining SMS outreach and eConsent
The forum is exploring how to make participant communication more efficient using SMS and eConsent, highlighting best practices and potential pitfalls. Read more here
Looking forward to another week of engaging discussions. Feel free to jump into these topics and share your experiences or learn from others.
On a 24-hour “safety clock,” the trick that’s saved us is auto-routing SAE alerts from the EDC to a rotating on‑call phone so the person on pager can submit the initial report within 2 hours. We also use a pre-approved one‑page minimal dataset to get the clock stopped fast, then backfill details, but watch that auto-exports don’t flood the TMF — we only file the final follow-up.
Building on @sthomp48, we run a follow‑the‑sun handoff plus a pre‑approved minimal SAE template in the EDC so whoever’s awake can file the bare essentials fast, and an RBM KRI pings if site‑to‑entry lag tops 90 minutes. Tiny caveat: set a TMF ‘hot folder’ so those SAE emails auto‑file to the right spot — nothing tanks the timer like hunting PDFs.
We cut misses by adding a ‘panic button’ in our eSource that grabs the four minimum elements and timestamps, then auto-creates a draft ICSR; if the app hiccups, a voicemail‑to‑text line opens the case — a fire alarm for SAEs. Caveat: privacy/QA had to vet the voice vendor first. @scarlett52, have you tried something like this?