Automated Post-Transplant Follow-Up Coordination
Every morning, WebRun opens gGastro (ModMed), checks each liver transplant recipient's follow up schedule, books the next recurring visit in Google Calendar, logs immunosuppression labs and visit compliance to Google Sheets, and posts a Slack alert to the transplant coordinator for any patient falling behind on labs or visits.
How do I keep liver transplant recipients on schedule for follow up care?
WebRun checks gGastro (ModMed) every morning for every liver transplant recipient's follow up status, books the next recurring visit in Google Calendar, logs immunosuppression labs and visit compliance to Google Sheets, and alerts the transplant coordinator in Slack about anyone falling behind. Recipients stay on their step down schedule without the coordinator manually cross checking labs and visits by hand.
- Every recipient's next follow up visit is booked automatically each morning
- Immunosuppression labs and visit compliance are tracked in one log
- The coordinator is alerted the same day a recipient falls behind
Built for transplant hepatology teams · transplant coordinators · liver transplant clinics · post-transplant care managers
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.modmed.comin a real browser with your saved login - no setup, no API keys. -
1
gGastro (ModMed) - check each recipient's follow up status
modmed.com
WebRun opens gGastro (ModMed) to check each recipient's follow up status. - Open gGastro (ModMed) and pull the transplant follow up schedule for every recipient
- Check the latest immunosuppression trough level and renal function labs
- Identify anyone overdue for a scheduled lab or visit
Done when Every transplant recipient's follow up status is current.
-
2
Google Calendar - book the next recurring visit
calendar.google.com
WebRun opens Google Calendar to book the next recurring visit. - Open Google Calendar and book the next recurring follow up visit based on the recipient's post-transplant timeline
- Space visits according to the standard step down schedule
- Flag any recipient with no visit booked inside their required window
Done when Every recipient has their next follow up visit booked.
-
3
Google Sheets - log labs and compliance
google.com
WebRun opens Google Sheets to log labs and compliance. - Open the post-transplant tracker and log each recipient's latest immunosuppression level and visit status
- Keep a running compliance history per recipient
- Mark anyone overdue on labs or a visit in the status column
Done when The tracker reflects current compliance for every recipient.
-
4
Slack - alert the coordinator on lapses
slack.com
WebRun opens Slack to alert the coordinator on lapses. - Post an alert to the transplant coordinator for any recipient overdue on labs or a visit
- Include the recipient's last lab date and how many days overdue they are
- Leave outreach to the recipient to the coordinator, not WebRun
Done when The coordinator has been alerted to every recipient falling behind.
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 WebRun contact the transplant recipient directly about a missed visit?
No. It only alerts the transplant coordinator in Slack. The coordinator decides how to reach out to the recipient.
How does it know the right follow up interval for each recipient?
It follows the standard post-transplant step down schedule recorded in gGastro (ModMed) for each recipient's time since transplant.
What counts as falling behind?
Any recipient overdue on a scheduled immunosuppression lab or a follow up visit triggers the Slack alert, so the coordinator sees it the same morning.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.