Route new incident reports to the right team
Every few minutes, WebRun checks RLDatix for newly logged incidents, reads the description to classify severity and type, assigns each one to the right department queue, and posts the on-call manager a Slack alert with the details.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically triage and route new patient safety incidents?
WebRun watches RLDatix for newly logged incidents every few minutes, reads each report to classify its type and severity, and assigns it to the right department queue. It then posts a Slack alert to that team, at-mentioning the on-call manager for anything moderate harm or higher, so no new incident sits unseen.
- New incidents reach the right department within minutes of being logged
- Moderate and severe harm events page the on-call manager automatically
- No incident report sits unseen in a shared queue overnight
Built for patient safety officers · hospital risk managers · clinical quality teams · nursing unit managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.rldatix.comin a real browser with your saved login - no setup, no API keys. -
1
RLDatix - read and classify new incidents
rldatix.com How to Automate RLDatix
WebRun opens RLDatix to read and classify new incidents. - Open RLDatix RLD360 and filter incident reports to newly submitted
- Read each report's description, location, and harm level
- Classify the type, such as fall, medication, equipment, or behavioral, and assign the correct department queue
- Tag the severity so the alert step can prioritize
Done when Every new incident has a type, a severity tag, and an assigned department queue.
-
2
Slack - alert the right team
slack.com How to Automate Slack
WebRun opens Slack to alert the right team. - Post the incident summary, severity, and location to the assigned department's channel
- At-mention the on-call manager for anything tagged moderate harm or higher
- Leave routine, low-harm reports in the queue without paging anyone
Done when The right team has seen every new incident in Slack, with urgent ones flagged.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Does it decide how serious an incident is on its own?
It reads the report and applies your organization's severity definitions to suggest a harm level and queue, but a person always makes the final clinical call. No facts in the report are changed.
Will it page anyone in the middle of the night?
Only for incidents tagged moderate harm or higher. Routine, low-harm reports wait quietly in the queue until the team's normal working hours.
What happens to incidents it can't classify confidently?
It routes anything ambiguous to a general safety queue and flags it for manual review instead of guessing at a department.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.