Glooko Automated CGM Prior Authorization Tracking
Every Monday, WebRun opens Glooko to find patients whose CGM sensor supply or prescription is expiring within 30 days, checks CoverMyMeds for each one's prior authorization status, starts a new request where none exists, and posts a worklist to Slack of which requests are waiting on a clinician signature.
How can I automatically track CGM supply prior authorizations before they lapse?
Every Monday, WebRun checks Glooko for patients whose CGM supply prescription expires within 30 days, looks up each one's prior authorization status in CoverMyMeds, and drafts a new request for anyone without one. It posts a Slack worklist ranked by urgency so a clinician can sign off quickly, keeping CGM supply moving without a lapse in coverage.
- Every expiring CGM prescription gets a drafted prior authorization before it lapses
- Clinicians see a ranked sign-off worklist instead of hunting for what is due
- Patients with an already-approved authorization are skipped automatically
Built for CDCES diabetes educators · prior authorization coordinators · endocrinology clinics · diabetes care coordinators
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
my.glooko.com/users/sign_inin a real browser with your saved login - no setup, no API keys. -
1
Glooko - find patients with expiring CGM supply prescriptions
glooko.com
WebRun opens Glooko to find patients with expiring CGM supply prescriptions. - Open Glooko and list patients whose CGM sensor supply prescription expires within 30 days
- Capture the device brand, prescribing provider, and insurance plan for each
- Skip patients whose supply order is already confirmed for renewal
Done when Every patient with an expiring CGM supply prescription is listed with their plan and device.
-
2
CoverMyMeds - check or start the prior authorization request
covermymeds.com
WebRun opens CoverMyMeds to check or start the prior authorization request. - Look up each patient's existing prior authorization status in CoverMyMeds
- Start a new request for anyone without an active or pending authorization
- Leave every new request as a draft. Do not submit until a clinician signs off
Done when Every expiring patient has either an active authorization or a drafted request awaiting signature.
-
3
Slack - post the sign-off worklist
slack.com
WebRun opens Slack to post the sign-off worklist. - Post the list of drafted prior authorization requests needing a clinician signature
- Flag anyone whose current supply runs out in fewer than 14 days
- Include the payer and device for each so the clinician can sign quickly
Done when The clinician has this week's prior authorization sign-off worklist in Slack.
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
Will it submit prior authorization requests without a clinician?
No. WebRun drafts each request in CoverMyMeds and leaves it there. A clinician reviews and signs before anything is submitted to the payer.
How far ahead does it check for expiring supplies?
It looks 30 days ahead by default, and flags anyone inside 14 days as urgent, so there is enough runway to get a request signed and approved before supplies run out.
What if a patient already has an approved authorization?
It checks the live status in CoverMyMeds each Monday, so anyone with an active or already-pending authorization is skipped from the worklist.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.