All templates
For patient safety officers, hospital risk managers & clinical leadership

Keep sentinel event follow-up on track for 72 hours

For the full 72 hours after a sentinel event is declared in RLDatix, WebRun checks every few hours which required initial-response steps, such as the safety huddle, interim safety measures, and offering the family a conversation, are still outstanding, emails and texts the responsible owners through Outlook and Twilio, and posts a Slack status update to leadership.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Checks every few hours during the 72 hours after a sentinel event is declared. WebRun
1 RLDatix track required 72-hour steps
2 Outlook email owners of outstanding steps
3 Twilio text leadership as the deadline nears
4 Slack post the status to leadership
Run a sample
In short

How do I track the 72-hour follow-up after a sentinel event?

For the full 72 hours after a sentinel event is declared in RLDatix, WebRun checks every few hours which required steps, like the safety huddle, interim safety measures, and the family conversation offer, are still outstanding. It emails and texts the responsible owners through Outlook and Twilio and posts a Slack status update, so nothing in the window is missed.

  • Every required 72-hour step is tracked without a manual checklist
  • Leadership is texted only if the window is closing with steps still open
  • Nothing in the mandatory response window is missed or forgotten

Built for patient safety officers · hospital risk managers · clinical leadership · quality and compliance teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.rldatix.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    RLDatix - track required 72-hour steps
    rldatix.com How to Automate RLDatix
    WebRun in RLDatix: track required 72-hour steps
    WebRun opens RLDatix to track required 72-hour steps.
    • Open RLDatix RLD360 and find events declared sentinel
    • Check the status of each required initial-response step: safety huddle held, interim safety measures logged, family conversation offered, immediate action plan documented
    • Calculate hours remaining in the 72-hour window

    Done when Every required step's status and the hours remaining are captured.

  3. 2
    Outlook - email owners of outstanding steps
    microsoft.com How to Automate Outlook
    WebRun in Outlook: email owners of outstanding steps
    WebRun opens Outlook to email owners of outstanding steps.
    • Draft and send a reminder email through Outlook to the owner of each outstanding step
    • Name the specific step and the hours remaining
    • Stop reminding once a step is marked complete in RLDatix

    Done when Every outstanding step's owner has been emailed a reminder.

  4. 3
    Twilio - text leadership as the deadline nears
    twilio.com How to Automate Twilio
    WebRun in Twilio: text leadership as the deadline nears
    WebRun opens Twilio to text leadership as the deadline nears.
    • Text the patient safety leader when fewer than 12 hours remain with steps still outstanding
    • Name exactly which steps are incomplete
    • Send only one text per remaining step, not a repeat every check

    Done when Leadership has been texted if the window is closing with steps still open.

  5. 4
    Slack - post the status to leadership
    slack.com How to Automate Slack
    WebRun in Slack: post the status to leadership
    WebRun opens Slack to post the status to leadership.
    • Post a status update to the safety leadership channel showing which steps are done and which remain
    • Note that any external notification to an accrediting body stays a decision for your risk and compliance team
    • Keep posting until every required step shows complete

    Done when Leadership can see the full 72-hour checklist status in Slack at a glance.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.rldatix.com
ScheduleRuns automatically on this cadence
Checks every few hours during the 72 hours after a sentinel event is declared.
DeliveryHow each run's result reaches you
Checklist status · Slack
OutputWhat each run produces - A 72-hour checklist status showing each required step, its owner, and whether it is complete.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it file the sentinel event report with the Joint Commission or a state agency?

No. It only tracks your internal 72-hour response checklist and nudges owners. Any external filing or notification stays a decision for your risk and compliance team.

Does it contact the patient's family?

No. It only tracks whether your team has logged that a family conversation was offered. WebRun never contacts a patient or family member itself.

What happens after the 72 hours are up?

It stops checking once the window closes. Ongoing root-cause analysis and longer-term actions are tracked by the separate RCA action item reminders.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.