Track down patients with no meal order on file
Every hour during ordering windows, WebRun opens Computrition, finds patients with no meal order on file for the next service such as a new admit not yet ordered or an expired diet order, and posts the diet office a Slack list so someone can call the unit before the tray line closes.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch patients with no meal order before the next tray line closes?
WebRun checks Computrition every hour for patients with no meal order on file for the next service, whether a new admit, an expired diet order, or a unit transfer. It posts the diet office a Slack list grouped by unit with the reason for each gap, so staff can call the floor and get an order placed before the tray line closes.
- Missing orders get caught every hour instead of at tray line close
- New admits and NPO reversals surface at the top of the list first
- Diet office follows up with time left before the next meal service
Built for hospital diet office staff · nutrition services coordinators · charge nurses · admitting and unit clerks
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.computrition.comin a real browser with your saved login - no setup, no API keys. -
1
Computrition - find patients with no order for the next meal
computrition.com How to Automate Computrition
WebRun opens Computrition to find patients with no order for the next meal. - Open Computrition and pull the patient list for the next meal service
- Cross check it against placed meal orders for that service
- Flag any patient with no order: new admits, diet order expirations, and unit transfers
- Note the patient's room, unit, and the reason no order exists
Done when Every patient without an order for the next meal service has been listed with a reason.
-
2
Slack - alert the diet office to follow up
slack.com How to Automate Slack
WebRun opens Slack to alert the diet office to follow up. - Post the missing order list to the diet office Slack channel, grouped by unit
- Put new admits and NPO reversals at the top since those need an order fastest
- Mark a patient off the list once an order appears in Computrition
Done when The diet office has this hour's missing order list in Slack, grouped by unit.
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 place a meal order for the patient automatically?
No. WebRun only flags who has no order and alerts the diet office. Placing the actual order in Computrition is always done by a person after checking with the patient or unit.
Does it contact the patient directly to ask what they want to eat?
No. WebRun only posts an internal Slack list for your diet office. It never messages or calls a patient itself.
How often does it check for missing orders?
Every hour during your meal ordering windows, so a gap gets caught with enough time left for the diet office to call the unit before the tray line closes.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.