Automated Chain of Custody Lab Alerts
Every few minutes, WebRun opens CXT Software, reads new specimen barcode scans and signature handoffs, appends each chain-of-custody event to a Google Sheet, and drafts a short status text to the receiving lab through Twilio for your team to approve before it sends.
How do I keep the lab updated on specimen custody as drivers scan each handoff?
WebRun checks CXT Software every few minutes for new specimen barcode scans and signature handoffs. It appends each chain-of-custody event to a Google Sheet with a timestamp, driver, and location, then drafts a Twilio status text to the receiving lab, with no patient identifiers, for your team to approve before it sends.
- Every specimen scan is logged to an auditable custody trail
- Labs hear about incoming specimens without patient data exposure
- No custody text goes out without human approval
Built for medical courier operations · clinical lab logistics · specimen transport teams · courier compliance leads
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.cxtsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
CXT Software - read new scans and custody handoffs
cxtsoftware.com
WebRun reads new barcode scans and signature handoffs in CXT Software. - Open CXT Software and check the chain-of-custody log for new barcode scans
- For each scan, capture the specimen ID, the scanning driver, the location, and the signature at handoff
- Identify which leg of the route the scan represents, from pickup to lab drop-off
- Skip scans already logged in a previous run
Done when Every new custody scan is captured with specimen ID, driver, location, and handoff signature.
-
2
Google Sheets - log the chain-of-custody event
google.com
WebRun appends each custody event to the chain-of-custody sheet. - Open the Chain of Custody Log sheet
- Append each scan as a new row with the timestamp, specimen ID, driver, location, and leg
- Keep one row per custody event so the full handoff trail is auditable
- Highlight any specimen still in transit past its expected leg time
Done when The custody log sheet holds a complete, timestamped trail for every scanned specimen.
-
3
Twilio - draft the lab status text for approval
twilio.com
WebRun drafts a lab status text and holds it for approval before sending. - Draft a short status text to the receiving lab noting the specimen count and expected arrival, without any patient identifiers
- Leave the text queued and unsent for your team to approve
- Send only after approval and record that the lab was notified
Done when A lab status text is drafted for each handoff and sent only after your team approves it.
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 text the lab without my approval?
No. WebRun drafts the lab status text and leaves it queued for your team to approve. Nothing is sent until a human confirms it, and the message carries no patient identifiers, only specimen counts and arrival timing.
Does the text include patient information?
No. The drafted text references specimen counts and expected arrival only. WebRun never puts patient identifiers or protected health information into an outbound message.
Where is the chain-of-custody trail kept?
In a Google Sheet that gets one timestamped row per scan, capturing the specimen ID, driver, location, and route leg, so you have an auditable handoff trail alongside the CXT Software log.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.