Automated Ensocare Authorization Pending Nudges
Every hour, WebRun opens Ensocare to find placements or services waiting on insurance authorization, checks how close each patient is to their estimated discharge date, and creates or nudges an Asana task so your utilization review team chases the authorizations most likely to delay a discharge.
How do I make sure a pending authorization does not delay a discharge?
WebRun checks Ensocare every hour for placements or services still waiting on insurance authorization, ranks them by how close each patient is to their estimated discharge date, and creates or nudges an Asana task so your utilization review team chases the authorizations most likely to hold up a discharge, closing the task automatically once Ensocare shows it approved.
- Authorizations most likely to delay a discharge get chased first, not last
- Approved authorizations close their task automatically, no manual cleanup
- Utilization review works from Asana instead of rechecking Ensocare by hand
Built for Utilization review teams · hospital case managers · insurance liaisons · discharge planning directors
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.ensocare.comin a real browser with your saved login - no setup, no API keys. -
1
Ensocare - find services awaiting authorization
ensocare.com
WebRun opens Ensocare to find services awaiting authorization. - Open Ensocare and filter to placements or services awaiting authorization
- Note the payer, days pending, and estimated discharge date for each
- Rank by how close each patient is to discharge
Done when Every pending authorization is listed with days pending and discharge proximity.
-
2
Asana - nudge the review task
- Create an Asana task for any newly pending authorization
- Add a comment nudging the existing task if it is still open
- Mark the task complete once Ensocare shows the authorization approved
Done when Every pending authorization has an open or updated Asana task, and approved ones are closed.
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 contact the insurance payer directly?
No. It only reads authorization status inside Ensocare and manages an Asana task. Any call or submission to the payer is still made by your utilization review team.
How does it prioritize which authorization to chase first?
It reads how close each patient is to their estimated discharge date, so authorizations most likely to delay a discharge get nudged first.
What happens once an authorization is approved?
It reads the live status in Ensocare each run and marks the matching Asana task complete automatically, no manual cleanup needed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.