Automated Clinisys Add-On Test Follow-Ups
Every morning, WebRun opens Clinisys, finds pending add-on test requests and checks each one against the original specimen's remaining stability window, drafts a status update to the ordering provider's office for your team to review, and queues a text for anything closing within the hour.
How do I follow up on pending add-on test requests before the specimen expires?
Every morning, WebRun checks Clinisys for pending add-on test requests and compares each against the original specimen's remaining stability window. It drafts a status update to the ordering provider's office in Gmail and queues an urgent text for anything closing within the hour, all left for your team to review and send before the stability window runs out.
- Pending add-on requests are ranked by how soon the stability window closes
- A status update is ready to send before your team even opens the request
- Nothing reaches the provider's office without a person reviewing it first
Built for hospital lab client services · clinical laboratory managers · phlebotomy and specimen management teams
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.clinisys.comin a real browser with your saved login - no setup, no API keys. -
1
Clinisys - check add-on requests against specimen stability
clinisys.com
WebRun opens Clinisys to check add-on requests against specimen stability. - Open Clinisys and pull add-on test requests still pending
- Check the original specimen's remaining volume and stability window for each
- Sort by how soon the stability window closes
Done when Every pending add-on request is listed with its remaining stability window.
-
2
Gmail - draft a status update for the provider's office
gmail.com
WebRun opens Gmail to draft a status update for the provider's office. - Draft a status update for each pending request: completed, still pending, or specimen no longer viable
- Address it to the ordering provider's office and leave it unsent in Drafts
- Never send the update automatically. Your team reviews and sends it
Done when Every pending add-on request has a drafted status update ready for review.
-
3
Twilio - queue an urgent text for closing windows
twilio.com
WebRun opens Twilio to queue an urgent text for closing windows. - For any request closing within the hour, queue a text to your team flagging it as urgent
- Include the specimen, the test, and the minutes remaining
- Leave the queued text for a person to send. Never auto-send to the provider's office
Done when Every request closing within the hour has an urgent text queued for review.
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
Will it tell the provider's office the add-on status without review?
No. Every status update is drafted in Gmail and left unsent. Urgent texts are queued the same way. Your team always reviews and sends before anything reaches the provider.
How does it decide a request is urgent?
By checking the original specimen's remaining stability window in Clinisys. Anything closing within the hour gets a queued text instead of waiting for the next email batch.
What happens once the add-on is completed or the specimen expires?
WebRun reads the live status in Clinisys each morning, so completed and expired requests are marked and drop off the pending list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.