Automated XSOLIS Status Change Recommendations
Every hour, WebRun opens XSOLIS, checks for any new status change recommendation such as observation to inpatient or inpatient to observation, drafts an Outlook note to the attending physician explaining the clinical reason, and posts your UM lead a Slack alert of every recommendation still awaiting a decision.
How do I get XSOLIS status change recommendations to physicians faster?
WebRun checks XSOLIS every hour for new status change recommendations, such as observation moving to inpatient, and drafts an Outlook note to the attending physician explaining the clinical reason behind each one. It posts the UM lead a Slack list of every recommendation still awaiting a decision, flagging anything open past 4 hours, while leaving the actual order change to the physician.
- Physicians see the clinical reason for a recommended status change within the hour
- No recommendation sits unactioned past 4 hours without an escalation flag
- Every status decision still requires the attending physician's own order
Built for utilization review nurses · physician advisors · UM department leads · hospital case management
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 - surface status change recommendations
xsolis.com
WebRun opens XSOLIS to surface status change recommendations. - Open XSOLIS and check for new status change recommendations since the last run
- Capture the patient, current status, recommended status, and the clinical reason given
- Note the attending physician of record for each recommendation
Done when Every new status change recommendation is listed with its clinical reason and attending physician.
-
2
Outlook - draft the physician note
microsoft.com
WebRun opens Outlook to draft the physician note. - Draft a concise Outlook note to the attending physician summarizing the recommended status change and the clinical reason behind it
- Ask the physician to confirm or update the order to match
- Leave every note unsent in Outlook Drafts. Only the physician's own order changes a patient's status
Done when A drafted, unsent note is waiting for the attending physician on every recommendation.
-
3
Slack - alert the UM lead
slack.com
WebRun opens Slack to alert the UM lead. - Post an alert to the UM lead's Slack channel listing every recommendation still awaiting a physician decision
- Flag any recommendation open more than 4 hours so it can be escalated
Done when The UM lead has a live Slack list of every recommendation still awaiting a physician decision.
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
Can it change a patient's status by itself?
No. WebRun only drafts a note explaining the recommended change and leaves it unsent in Outlook. Only the attending physician's own order can change a patient's status.
How is the clinical reason for a recommendation written?
It's pulled directly from XSOLIS's own recommendation and reason code, so the physician sees the same clinical rationale the UM team is looking at.
What happens if a recommendation sits too long?
Any recommendation still awaiting a physician decision after 4 hours is flagged in the Slack alert so the UM lead can follow up or escalate.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.