Catch inpatient versus observation mismatches before the payer does
Every hour, WebRun opens XSOLIS, compares each patient's current inpatient or observation order against what the clinical documentation supports, flags any mismatch, logs it to a Google Sheet with the gap detail, and posts your UM team a Slack alert so a nurse can follow up with the ordering physician the same day.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch inpatient versus observation status mismatches before a payer denies the claim?
WebRun compares every patient's current order against XSOLIS's clinical criteria each hour, flags any mismatch between an inpatient or observation order and what the documentation supports, and logs it to a Google Sheet. It posts a same day Slack alert naming the assigned nurse, so a mismatch gets corrected with the ordering physician quickly instead of surfacing later as a payer denial.
- Status mismatches are caught within the hour instead of surfacing as a denial weeks later
- Every mismatch is logged with what the order says and what the documentation supports
- No order is ever changed automatically. Only the physician's order updates a patient's status
Built for utilization review nurses · hospital compliance teams · case management directors · denial prevention teams
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
dragonfly.xsolis.comin a real browser with your saved login - no setup, no API keys. -
1
XSOLIS - compare order against criteria
xsolis.com How to Automate XSOLIS
WebRun opens XSOLIS to compare order against criteria. - Open XSOLIS and compare each patient's current order to the clinical criteria the documentation supports
- Flag any patient ordered inpatient whose documentation only supports observation criteria, and the reverse
- Capture the patient, unit, current order, and what the documentation actually supports
Done when Every inpatient versus observation mismatch is listed with the current order and what the documentation supports.
-
2
Google Sheets - log every mismatch
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log every mismatch. - Open the Status Mismatch Log sheet
- Append a row for each new mismatch found this hour
- Mark a row resolved once XSOLIS shows the order and criteria now agree
Done when The log sheet reflects every open and resolved status mismatch.
-
3
Slack - alert the UM team
slack.com How to Automate Slack
WebRun opens Slack to alert the UM team. - Post a Slack alert to the UM channel for each new mismatch found
- Name the assigned nurse so they can contact the ordering physician the same day
- Never change the order itself. Only the physician's own order can update a patient's status
Done when The UM team has a same day Slack alert for every open status mismatch.
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 correct the order automatically?
No. WebRun only flags the mismatch and alerts the assigned nurse. Only the ordering physician's own order can change a patient's inpatient or observation status.
How quickly does it catch a new mismatch?
It compares every patient's order against the supporting documentation each hour, so a new mismatch is caught and alerted within the hour it appears, not days later.
What happens once the order and documentation agree again?
It reads the live status in XSOLIS each hour, so any mismatch that gets corrected is marked resolved on the next run automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.