Automated Omnicell Par Level Breach Digest
Every morning, WebRun opens Omnicell, compares every cabinet item's on-hand quantity against its set par level, logs each breach to a running Google Sheet with the item, unit, and variance, and posts the pharmacy team a Teams digest sorted by the worst breaches first.
How do I catch Omnicell par level breaches before they cause a stockout?
Every morning, WebRun compares Omnicell cabinet stock against your configured par levels across every unit, logs each breach to a Google Sheet with the variance, and posts the pharmacy team a Teams digest ranking the worst overstock and understock items first, so the team catches drift before it becomes waste or a stockout.
- Par drift is caught every morning instead of at the next physical count
- Overstock and understock risk are ranked separately so the worst items get attention first
- A full history of breaches is kept in Sheets to spot repeat offenders
Built for hospital pharmacy managers · inventory technicians · pharmacy operations teams · nursing unit liaisons
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 - compare stock against par levels
omnicell.com
WebRun opens Omnicell to compare stock against par levels. - Open Omnicell and pull the current on-hand quantity for every cabinet item across all units
- Compare each item's on-hand quantity against its configured min and max par level
- Calculate the variance, in units and in percent, for every item outside its par range
Done when Every item currently above max or below min par is identified with its variance.
-
2
Google Sheets - log every breach
google.com
WebRun opens Google Sheets to log every breach. - Open the Par Level Breach Log sheet
- Append a row per breach with the unit, item, on-hand quantity, par range, and variance
- Preserve prior days' rows so recurring breaches are visible over time
Done when Today's breaches are logged with enough detail to spot repeat offenders.
-
3
Microsoft Teams - digest breaches to the team
microsoft.com
WebRun opens Microsoft Teams to digest breaches to the team. - Post a Teams digest to the pharmacy team channel, sorted with the largest breaches first
- Separate the list into over-par (waste and expiry risk) and under-par (stockout risk)
- Link to the full Google Sheet for the complete history
Done when The pharmacy team has this morning's par breach digest in Teams, split by over and under par.
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
Does it change par levels on its own?
No. WebRun only compares current stock against the par levels your team has already configured in Omnicell. Adjusting a par level itself is always a decision your team makes.
What counts as a breach?
Any item currently holding more than its configured maximum or less than its configured minimum. Both directions are tracked, since overstock risks waste and expiry while understock risks a stockout.
Will I get a digest even when everything is within range?
Yes. A short digest posts every morning either way, so a quiet day is a confirmation the cabinets are in range, not silence you have to interpret.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.