Walk into every CCC meeting with the packet ready
The Monday before each quarterly CCC meeting, WebRun opens MedHub, pulls every resident's current milestones, evaluation completion, and any professionalism or performance flags, compiles it all into a per-resident packet in Google Docs, and puts the meeting on the committee's Google Calendar with the draft packet attached for the program director to finalize.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I prepare a Clinical Competency Committee meeting packet automatically?
Before each quarterly CCC meeting, WebRun pulls every resident's milestones, evaluation completion, and performance flags from MedHub and compiles a one-page packet per resident in Google Docs. It links the draft packet to the calendared meeting, leaving the final packet for the program director to review, so the committee sits down already prepared.
- Committee members open the meeting with a prepared packet instead of a data pull
- Program directors get final review before anything reaches the committee
- Packets stay current because a rerun before the meeting reflects the latest MedHub data
Built for Clinical Competency Committee chairs · residency program directors · GME program coordinators · designated institutional officials
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 - pull milestones, evaluations, and flags
WebRun opens MedHub to pull milestones, evaluations, and flags. - Open MedHub and pull each resident's current milestone ratings, evaluation completion rate, and any professionalism or performance flags on file
- Note which residents have an open remediation plan or unresolved evaluation gap
- Organize the data by resident, in the order the committee reviews them
Done when Every resident on this quarter's agenda has their milestones, evaluations, and flags pulled.
-
2
Google Docs - compile the per-resident packet
WebRun opens Google Docs to compile the per-resident packet. - Draft a one-page packet per resident with their milestone summary, evaluation completion, and any open flags
- Order the packet to match the committee's review sequence
- Leave the packet as a draft for the program director to review and finalize before it's shared with the committee
Done when A draft packet exists in Google Docs for every resident on the agenda.
-
3
Google Calendar - put the meeting on the committee calendar
WebRun opens Google Calendar to put the meeting on the committee calendar. - Confirm the quarterly CCC meeting is on the committee's shared calendar
- Attach a link to the draft packet document on the calendar event
- Send the standard meeting reminder to committee members who already sit on the recurring invite
Done when The meeting is calendared with the draft packet linked for the committee.
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 the committee see the packet before the program director reviews it?
No. WebRun leaves the packet as a draft in Google Docs. The program director reviews and finalizes it before it's shared with the rest of the committee.
What if a resident's data changed after the packet was drafted?
Rerun WebRun any time before the meeting and it rereads MedHub fresh, so a last-minute evaluation or milestone update is reflected in the next draft.
Does it schedule the meeting itself?
No. It confirms your existing recurring CCC meeting on the calendar and attaches the packet link. Setting up a new meeting time is left to the program coordinator.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.