Automated MedHub Conference Attendance Tracking
Every Monday, WebRun opens MedHub, checks each resident's logged attendance at grand rounds and required didactic conferences against the sessions on the teaching calendar, calculates a rolling attendance rate, and updates a Google Sheet ranking residents against your program's minimum so anyone falling short stands out immediately.
How do I track resident didactic conference attendance against the required minimum?
WebRun checks MedHub every Monday for each resident's logged attendance at grand rounds and required didactic conferences, matches it against the actual sessions held on the teaching calendar, and calculates a rolling attendance rate. It updates a Google Sheet ranking every resident against the required minimum, so anyone falling short stands out immediately.
- Attendance shortfalls surface weekly instead of at the annual review
- Excused absences are excluded automatically so rates stay fair
- The resident with the lowest rate always sits at the top of the tracker
Built for residency program coordinators · program directors · chief residents · 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 - check logged attendance
WebRun opens MedHub to check logged attendance. - Open MedHub and pull each resident's logged attendance for grand rounds and required didactic conferences
- Calculate a rolling attendance rate over the trailing academic quarter
- Flag any resident whose rate has fallen under your program's required minimum
Done when Every resident's rolling attendance rate is calculated and compared to the minimum.
-
2
Google Calendar - match against the teaching calendar
WebRun opens Google Calendar to match against the teaching calendar. - Check the teaching calendar for how many required sessions occurred in the period
- Confirm the attendance denominator matches the actual number of required sessions held
- Note any session that was cancelled or made optional so it's excluded from the count
Done when The attendance calculation matches the actual required sessions on the teaching calendar.
-
3
Google Sheets - rank residents against the minimum
WebRun opens Google Sheets to rank residents against the minimum. - Open the attendance tracker and update each resident's rolling rate for this week
- Rank residents so the lowest attendance rate appears first
- Highlight anyone who has fallen under the required minimum
Done when The tracker reflects this week's ranked attendance rate for every resident.
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 resident about their attendance directly?
No. It only updates the shared tracker sheet. The program coordinator decides how to follow up with any resident falling under the minimum.
How is the attendance rate calculated?
It divides each resident's logged attendance in MedHub by the number of required sessions actually held on the teaching calendar over the trailing quarter, excluding any session that was cancelled or made optional.
What if a resident was on an away rotation or leave?
Configure excused absence types in MedHub and WebRun will exclude those sessions from the resident's denominator, so time away doesn't unfairly count against their rate.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.