Glooko Automated Pre-Visit CGM Data Review
Every morning, WebRun opens Google Calendar to find today's diabetes visits, pulls each patient's time in range, CGM trends, and pump or pen dose history from Glooko into a one-page brief, and posts the care team a ready-to-read summary in Slack before the first patient walks in.
How can I automatically prep CGM data before each diabetes visit?
Every morning, WebRun checks Google Calendar for the day's diabetes visits, pulls each patient's time in range, glucose trends, and pump or pen dose history from Glooko, and posts a one-page brief per patient to the care team's Slack channel. The team walks into every visit already knowing the trends, before the patient even sits down.
- Every visit starts with the patient's CGM trends already reviewed
- Care teams see time in range and dose data before walking in
- Data gaps and low sensor wear time get flagged before the visit, not during it
Built for CDCES diabetes educators · endocrinology clinics · diabetes care coordinators · primary care diabetes programs
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
calendar.google.comin a real browser with your saved login - no setup, no API keys. -
1
Google Calendar - find today's diabetes visits
calendar.google.com
WebRun opens Google Calendar to find today's diabetes visits. - Open Google Calendar and list every diabetes visit scheduled for today
- Capture each patient's name, visit time, and visit reason
- Skip canceled or rescheduled appointments
Done when Every patient on today's diabetes schedule is listed with their visit time.
-
2
Glooko - pull CGM and pump trends for each patient
glooko.com
WebRun opens Glooko to pull CGM and pump trends for each patient. - Look up each scheduled patient in Glooko's Population Tracker
- Pull time in range, average glucose, sensor wear time, and recent low or high glucose events
- Note pump or pen dose totals and any missed boluses since the last visit
- Flag any patient with a large drop in sensor wear time or a data gap
Done when Every scheduled patient has a current CGM and dose summary pulled from Glooko.
-
3
Slack - post the pre-visit brief to the care team
slack.com
WebRun opens Slack to post the pre-visit brief to the care team. - Format a one-page brief per patient with visit time, time in range, and flags
- Order the list by visit time so the earliest patient appears first
- Post the full brief to the care team channel before clinic opens
Done when The care team has a pre-visit brief for every patient in Slack before the first appointment.
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 this share patient data outside the clinic?
No. The brief posts to your clinic's own Slack channel only. WebRun does not email, text, or post any patient data anywhere outside the tools your team already uses.
What if a patient's appointment is added or moved last minute?
WebRun reads the live Google Calendar each morning, so a same-day add or reschedule is picked up on the next run. A very last-minute change after the morning run shows up the following day.
What if a patient has not synced their CGM recently?
WebRun flags it. Any patient with a sensor wear time drop or a data gap is marked on the brief so the care team knows to ask about it at the visit.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.