Fill a coverage gap the moment a resident calls out
Every few minutes, WebRun checks MedHub for a newly logged resident absence, checks the current rotation schedule and each nearby resident's duty hours already worked this week, and posts the chief resident an immediate Slack alert naming who could cover without crossing a duty-hour limit, along with the open block flagged on Google Calendar.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find duty-hour-safe coverage the moment a resident calls out?
WebRun checks MedHub every few minutes for a newly logged resident absence. It reads the current rotation schedule and each nearby resident's duty hours already worked this week, then posts the chief resident an immediate Slack alert ranking who could cover without breaching a duty-hour limit, leaving the actual reassignment for a person to make.
- Coverage alerts go out within minutes of an absence being logged
- Every suggested swap is checked against duty hours already worked
- Chief residents get ranked options instead of calling around to find who's free
Built for chief residents · residency program coordinators · GME schedulers · academic medical centers
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.medhub.comin a real browser with your saved login - no setup, no API keys. -
1
MedHub - detect a newly logged absence
medhub.com How to Automate MedHub
WebRun opens MedHub to detect a newly logged absence. - Check MedHub for any resident absence logged since the last run
- Pull the current rotation schedule for who else is on service nearby
- Check each candidate's duty hours already worked this week so no swap would create a new violation
Done when Any new absence is identified along with a duty-hour-safe list of possible coverage.
-
2
Slack - alert the chief resident with coverage options
slack.com How to Automate Slack
WebRun opens Slack to alert the chief resident with coverage options. - Post the chief resident an immediate alert naming the absent resident, the block that needs coverage, and who's eligible to swap in
- Rank eligible candidates by fewest hours already worked this week
- Note that the actual reassignment still needs to be made in MedHub by a person
Done when The chief resident has an immediate coverage alert with ranked options in Slack.
-
3
Google Calendar - flag the open block
calendar.google.com How to Automate Google Calendar
WebRun opens Google Calendar to flag the open block. - Mark the affected block as needing coverage on the rotation calendar
- Update the block once the chief resident confirms who's covering
- Remove the flag once MedHub shows the reassignment is complete
Done when The open block is flagged on the calendar until a confirmed replacement is entered.
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 reassign the resident's shift automatically?
No. WebRun only surfaces who's eligible to cover without breaching a duty-hour limit. The chief resident makes the actual call and enters the reassignment in MedHub.
How does it make sure a swap doesn't cause a new violation?
It checks each candidate's duty hours already logged this week in MedHub before ranking them, so it never suggests a swap that would push someone over the weekly cap.
How fast does the alert go out?
Within a few minutes of the absence being logged in MedHub, since coverage gaps need same-day answers, not a next-morning digest.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.