All templates

Automated Medication Delivery Refusal Alerts

Every hour, WebRun checks adherent360 for any bedside or kiosk delivery a patient has refused, logs the unit, reason, and time to a Google Sheet, and texts the covering pharmacist through Twilio so someone can follow up in person before the patient is discharged.

Runs on WebRun · Strict Lockdown policy
Every hour, 7 AM to 9 PM WebRunorchestrates each step
1 adherent360 find delivery refusals
2 Google Sheets log the refusal and its reason
3 Twilio text the covering pharmacist
In short

How do I get notified when a patient refuses a bedside medication delivery?

WebRun checks adherent360 every hour for any bedside or kiosk delivery a patient has refused, logs the unit, reason, and time to a Google Sheet, and texts the covering pharmacist through Twilio, naming only the unit and bed, so someone can address the refusal in person while the patient is still admitted and before a dose gets missed.

  • Refusals reach a pharmacist within the hour instead of surfacing after discharge
  • Refusal reasons get logged automatically so patterns are easy to spot
  • Patients already discharged are routed to a callback list instead of falling through

Built for hospital pharmacy teams · meds to beds programs · discharge nurses · care transition coordinators

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 adherent360.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    adherent360 - find delivery refusals
    adherent360.com
    WebRun in adherent360: find delivery refusals
    WebRun opens adherent360 to find delivery refusals.
    • Open the delivery tracker in adherent360 and filter to refused or declined status
    • Capture the unit, bed, refusal reason if recorded, and the time of refusal
    • Note whether the patient is still an inpatient or already discharged

    Done when Every refusal in the last hour is listed with its reason and timing.

  3. 2
    Google Sheets - log the refusal and its reason
    google.com
    WebRun in Google Sheets: log the refusal and its reason
    WebRun opens Google Sheets to log the refusal and its reason.
    • Open the refusal log sheet
    • Add a row for each refusal with unit, reason, and time
    • Roll up refusal counts by reason so patterns are visible over time

    Done when Every refusal from this hour is logged with its reason.

  4. 3
    Twilio - text the covering pharmacist
    twilio.com
    WebRun in Twilio: text the covering pharmacist
    WebRun opens Twilio to text the covering pharmacist.
    • Text the pharmacist covering that unit naming only the unit and bed, never the patient's full name
    • Ask them to follow up with the patient in person while they are still admitted
    • Skip the text if the patient has already been discharged and route it to the callback list instead

    Done when The covering pharmacist has been texted for every refusal involving a still admitted patient.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
adherent360.com
ScheduleRuns automatically on this cadence
Every hour, 7 AM to 9 PM
DeliveryHow each run's result reaches you
Refusal alert · Twilio
OutputWhat each run produces - A log of every delivery refusal with its reason, plus a text sent to the covering pharmacist for any refusal involving a patient still in house.
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 WebRun contact the patient who refused?

No. It texts your covering pharmacist only, naming the unit and bed, not the patient. Any conversation with the patient is a human one, in person, before discharge.

Why does a refusal matter if the patient can just get meds elsewhere?

A refusal at discharge is one of the biggest predictors of a missed first dose after leaving. Surfacing it fast gives your pharmacist a chance to address the concern while the patient is still there.

What happens if the patient already left before the text goes out?

It skips the text and routes that refusal to a callback list instead, so it is not lost, it just moves to a follow up path suited to a discharged patient.

Put this on autopilot.

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