Automated Clinical Trial Results Routing
Every few minutes, WebRun checks RealTime-CTMS for newly recorded lab or visit results, identifies any out-of-range or clinically notable values, routes an internal alert to the PI and coordinator in Slack, and logs each result routing event in Google Sheets. No subject health data leaves the internal system.
How do I automatically route out-of-range lab results to the right person at a clinical research site?
WebRun checks RealTime-CTMS every few minutes for newly recorded lab and visit results, flags out-of-range values against protocol ranges, and routes an internal Slack alert to the PI or coordinator with no subject identifiers included. Every routing event is logged in Google Sheets for audit purposes.
- Out-of-range results reach the right staff within minutes of being recorded
- No subject identifiers sent outside RealTime-CTMS in automated alerts
- A full audit log of every result routed is maintained automatically in Google Sheets
Built for principal investigators · clinical research coordinators · research site managers · site medical staff
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
realtime-ctms.com/loginin a real browser with your saved login - no setup, no API keys. -
1
RealTime-CTMS - detect newly recorded results and flag out-of-range values
realtime-ctms.com
WebRun opens RealTime-CTMS to detect newly recorded results and flag out-of-range values. - Open RealTime-CTMS and check for lab or visit results recorded in the last few minutes
- Compare each result against the protocol-defined normal ranges for the visit and study
- Flag results that are out of range or marked as clinically significant
Done when Every newly recorded result is categorized as within range or flagged for clinical review.
-
2
Slack - route internal alert to PI and coordinator
slack.com
WebRun opens Slack to route internal alert to PI and coordinator. - Post an internal alert to the designated PI and coordinator Slack channel for each flagged result
- Include the study name, visit type, which parameter is out of range, and the assigned coordinator
- Do not include the subject's name, date of birth, or other direct identifiers in the Slack message
Done when The PI and coordinator have an internal Slack alert for every flagged result, with no PHI in the message.
-
3
Google Sheets - log each result routing event for audit
google.com
WebRun opens Google Sheets to log each result routing event for audit. - Append a row to the Results Routing Log in Google Sheets for each result processed
- Record the study, visit type, flag status, routing timestamp, and which staff were alerted
- Mark the row Resolved once the PI acknowledges the alert in Slack
Done when The routing log is updated with a record of every result flagged and routed in this run.
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 send subject health data outside the organization?
No. Slack alerts include only the study name, visit type, and flagged parameter, with no direct subject identifiers. All detailed health data stays within RealTime-CTMS.
What counts as an out-of-range result?
It compares each result against the normal reference ranges defined in the study protocol and stored in RealTime-CTMS. The clinical determination is always made by the PI or coordinator who reviews the alert.
Will it escalate critical results differently from minor flags?
Yes. Results marked as clinically significant in RealTime-CTMS are routed directly to the PI channel in Slack, while minor out-of-range values go to the coordinator channel only.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.