Automated LTC Pharmacy Cycle Fill Recovery Worklist
After each cycle run closes, WebRun opens FrameworkLTC and identifies all medication orders that were scheduled for the cycle but not dispensed, captures the reason code for each gap (out of stock, hold, authorization pending, discontinued), logs the recovery list to Google Sheets grouped by facility and reason, and posts a Slack alert to your pharmacy team so every skipped fill is resolved or closed before the next delivery run.
How do I automatically recover medications not dispensed during an LTC pharmacy cycle fill?
WebRun reviews FrameworkLTC after each cycle run, identifies every medication order scheduled but not dispensed, captures the reason code for each gap, logs the recovery list to Google Sheets grouped by facility and reason, and posts a Slack alert to your pharmacy team so every skipped fill is resolved or closed before the next delivery goes out.
- Every skipped fill is identified and actioned before the next delivery run
- Reason codes are captured so systemic supply or authorization issues are visible
- Persistent multi-cycle gaps are escalated before residents experience a gap in care
Built for long-term care pharmacies · LTC pharmacy dispensing teams · pharmacy operations managers · nursing facility medication coordinators
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.frameworkltc.comin a real browser with your saved login - no setup, no API keys. -
1
FrameworkLTC - identify orders scheduled but not dispensed
frameworkltc.com
WebRun opens FrameworkLTC to identify orders scheduled but not dispensed. - Open FrameworkLTC and navigate to the completed cycle fill queue
- Compare the scheduled order list against dispensing records to identify orders not dispensed
- Capture the reason code for each gap: out of stock, resident hold, authorization pending, order discontinued, or other
- Group skipped fills by nursing facility and reason code
Done when Every medication order scheduled but not dispensed is listed with its reason and facility.
-
2
Google Sheets - log recovery list by facility and reason
google.com
WebRun opens Google Sheets to log recovery list by facility and reason. - Open the cycle recovery worklist Google Sheet
- Append skipped fills grouped by facility and reason code with the drug, resident identifier, and scheduled delivery date
- Mark items resolved when the pharmacy team confirms the fill was completed or the order was closed
Done when The Google Sheet shows all open skipped fills from the most recent cycle.
-
3
Slack - alert pharmacy team to open gaps
slack.com
WebRun opens Slack to alert pharmacy team to open gaps. - Post a Slack alert to the pharmacy team channel with the total count of skipped fills and the breakdown by reason code
- List facilities with more than two skipped fills at the top
- Include a link to the Google Sheet recovery worklist for the team to action
Done when The pharmacy team has the cycle recovery list and worklist link in Slack.
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 contact the nursing facility about a missing fill automatically?
No. The recovery list goes to your internal pharmacy team. Any communication to a nursing facility about a skipped fill is prepared as a draft for a pharmacist or tech to review and send, so no external message is sent automatically.
How does it distinguish a legitimate hold from a true gap?
It reads the reason code recorded in FrameworkLTC for each unfilled order. Orders on an authorized resident hold are listed separately from items that were simply skipped without a recorded reason, so your team knows which gaps need urgent follow-up.
What happens to items carried over from a previous cycle?
Items still open in Google Sheets from a prior cycle remain on the worklist until your team marks them resolved. The Slack alert flags any item that has been open for more than one cycle so persistent gaps get escalated attention.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.