All templates

Automated RLDatix Serious Event Escalation

Every few minutes, WebRun checks RLDatix for newly tagged serious or high-harm events, texts the on-call patient safety officer through Twilio with the event and location, and posts the full detail to the safety leadership Slack channel for immediate review.

Runs on WebRun · Strict Lockdown policy
Every few minutes, so a serious event is caught within minutes of being tagged in RLDatix. WebRunorchestrates each step
1 RLDatix detect serious or high-harm events
2 Twilio text the on-call safety leader
3 Slack post full detail to leadership
In short

How do I make sure serious safety events get escalated immediately?

WebRun checks RLDatix every few minutes for events tagged serious or high harm. The moment one appears, it texts your on-call patient safety officer through Twilio with the event, unit, and harm level, and posts the full detail to your safety leadership Slack channel, so a serious event gets an immediate response instead of sitting in a queue.

  • The on-call safety officer is texted within minutes of a serious event being tagged
  • Safety leadership has full event detail in Slack before the next shift change
  • No serious or high-harm event waits for the next scheduled report

Built for patient safety officers · hospital risk managers · clinical leadership · on-call safety 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 - detect serious or high-harm events
    rldatix.com
    WebRun in RLDatix: detect serious or high-harm events
    WebRun opens RLDatix to detect serious or high-harm events.
    • Open RLDatix RLD360 and filter events to those tagged serious or high harm
    • Confirm the harm level, unit, and time of the event
    • Note whether an immediate safety measure, such as isolating equipment or a medication hold, has already been logged

    Done when Every serious or high-harm event has a confirmed harm level, unit, and time.

  3. 2
    Twilio - text the on-call safety leader
    twilio.com
    WebRun in Twilio: text the on-call safety leader
    WebRun opens Twilio to text the on-call safety leader.
    • Text the on-call patient safety officer with the event type, unit, and harm level
    • Include a direct link back to the RLDatix record
    • Repeat the page once if there is no acknowledgement within 15 minutes

    Done when The on-call safety officer has been texted and the page is logged.

  4. 3
    Slack - post full detail to leadership
    slack.com
    WebRun in Slack: post full detail to leadership
    WebRun opens Slack to post full detail to leadership.
    • Post the full event detail to the safety leadership channel
    • Include what immediate safety measures are already in place
    • Leave a thread open for leadership to coordinate the response

    Done when Safety leadership has the complete event detail in Slack for the response.

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
Every few minutes, so a serious event is caught within minutes of being tagged in RLDatix.
DeliveryHow each run's result reaches you
Escalation alert · Slack
OutputWhat each run produces - An escalation record showing the event, harm level, who was paged, and when.
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 text patients or their families?

No. It only texts your internal on-call patient safety officer through your organization's own Twilio number. It never contacts a patient or family member.

Does it report the event to regulators or accreditation bodies?

No. It only alerts your internal safety leadership. Any external reporting decision stays with your risk and compliance team.

What counts as serious or high harm?

Whatever your organization has already defined in RLDatix. WebRun reads the existing tag; it does not invent its own severity scale.

Put this on autopilot.

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