Automated Omnicell Override Transaction Audits
Every Monday, WebRun opens Omnicell, pulls every override transaction from the past week where a nurse accessed medication before pharmacist verification, logs each one to a Google Sheet with the user, drug, and reason given, and drafts a compliance summary email in Outlook for the Director of Pharmacy to review before it goes to Risk Management.
How do I keep a weekly audit trail of Omnicell override transactions?
Every Monday, WebRun pulls the past week's Omnicell override transactions, logs each one to a Google Sheet with the user, drug, and reason given, and flags any user whose override rate sits well above their unit's average. It drafts the compliance summary in Outlook for the Director of Pharmacy to review, so a clean weekly audit trail exists without anyone writing the report by hand.
- A full week of override activity is summarized without anyone building the report by hand
- Users with an unusually high override rate are flagged for review, not buried in a raw transaction list
- The compliance summary waits as a draft, so a human always reviews it before it reaches Risk Management
Built for Directors of Pharmacy · pharmacy compliance officers · risk management teams · hospital pharmacy auditors
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.omnicell.comin a real browser with your saved login - no setup, no API keys. -
1
Omnicell - pull the week's override transactions
WebRun opens Omnicell to pull the week's override transactions. - Open Omnicell and pull every override transaction from the past 7 days
- Capture the user, cabinet, drug, timestamp, and the reason code entered at the time of override
- Flag any user whose override rate is well above the unit average
Done when Every override from the past week is captured with its reason and the user's total for the week.
-
2
Google Sheets - log every override with its reason
WebRun opens Google Sheets to log every override with its reason. - Open the Override Audit Log sheet
- Append a row per override with the user, drug, reason, and timestamp
- Add a per-user summary tab tallying override counts for the week
Done when The week's overrides are logged individually and summarized per user.
-
3
Outlook - draft the compliance summary for review
WebRun opens Outlook to draft the compliance summary for review. - Draft a compliance summary email highlighting total overrides, the reason breakdown, and any user flagged as above average
- Attach or link the full Google Sheets log
- Leave the email as a draft addressed to the Director of Pharmacy. Never send it automatically
Done when A draft compliance summary is waiting in Outlook for the Director of Pharmacy to review and send on.
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 send the compliance summary to Risk Management automatically?
No. WebRun only drafts the summary email in Outlook, addressed to the Director of Pharmacy. It stays a draft until a person reviews and sends it, so nothing about a specific nurse or override reaches Risk Management without human review.
How does it decide a user is above average?
It compares each user's override count for the week against the average across their unit. Being flagged doesn't mean wrongdoing, it means the Director of Pharmacy should look at the reason codes before drawing a conclusion.
Does this replace the pharmacist's real-time review of overrides?
No. This is a retrospective weekly audit trail, not a replacement for verifying an override at the time it happens. It exists so patterns are visible after the fact, on top of your existing real-time checks.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.