How to Automate Glooko

Glooko turned the device download into a shared record

Glooko is the layer that made diabetes device data usable by a clinic. A person with diabetes wears or carries several devices, and for years every manufacturer had its own cable, its own desktop uploader and its own report. Glooko consolidates them: meters, insulin pumps, continuous glucose monitors, connected pens, activity trackers and scales, from a long list of makers, into one record a clinician and a patient can look at together. European clinics that knew the service as diasend are on the same platform.

The people using it are diabetes care and education programs, endocrinology clinics, primary care practices carrying large panels, hospitals and health systems, and patients themselves through the mobile app.

It has grown by acquisition as well as by integration. Since Glooko acquired Monarch Medical Technologies it also carries EndoTool, the inpatient insulin dosing system, so one company now spans the ward and the clinic.

Everything except the glucose still arrives late

A diabetes service that has solved its data problem has not solved its day.

Consider what a diabetes educator is actually holding. A patient on an insulin pump needs infusion sets, reservoirs and sensors, ordered from a supplier that ships them and reports on its own portal. A new CGM prescription needs a prior authorization, filed on a payer's site and decided on the payer's timetable. Every patient needs an annual retinal screening, done at an optometrist or an ophthalmology practice that sends something back if anybody remembers to ask. An A1C drawn at a hospital lab is a result on that hospital's system.

Then the classes. A self-management education program has a roster, a waiting list and people who did not turn up, and the roster is almost never kept where the readings are.

Glooko

Sensors that arrive before they run out Supply orders checked at each distributor's portal against who is due, so nobody ends up stretching an infusion set.

Authorizations followed to a decision CGM and pump requests tracked at the payer's own site through pended, denied and approved, with the date attached.

Eye exams marked done when they are done Retinal screening results chased at the practice that performed them, so a completed exam stops reading as an open gap.

The dashboard can only rank what has already synced

Glooko covers its own ground thoroughly, and any clinic should exhaust that before adding anything.

Remote syncing means data arrives without a cable, an appointment or a manual upload, which was the original problem and is no longer one. The clinic dashboard turns a panel into something a care team can work through: the TIDE view sorts patients by clinical risk using measures like time in range and hypoglycemia, so the ones needing attention sit at the top instead of being buried. Population Metrics show how much of the panel is monitoring and syncing at all, and Engagement Metrics show where that has dropped off. EHR integration puts the data where the visit happens, with Epic, Oracle Health, MEDITECH, Greenway Health, eClinicalWorks, NextGen and athenahealth among the systems connected. The mobile app gives the patient the same picture the clinic has.

Every one of those works on glucose, insulin and activity data that Glooko already receives.

A supplier's shipping portal sends no glucose. Neither does the payer's authorization queue, the optometrist, or the outside lab that ran the A1C.

Supplies, screening and approvals tracked beside the readings

The readings are already arriving. Everything alongside them can arrive the same way.

Pump and CGM supply orders checked at each supplier's portal against who is due, so a patient about to run out of infusion sets is found before they start stretching them. CGM prior authorizations tracked at the payer's own site through submitted, pended and approved, so a sensor cleared on Tuesday is not still sitting in a folder on Friday.

Retinal screening chased at the practice that performed it, so an eye exam done in March is recorded as done rather than showing as an open gap all year. A1C results collected from outside labs and set beside the sensor data for the same person, so a value drawn at a hospital turns up in the same review. Education class rosters and waiting lists read from wherever they are kept, with the people who booked and never came listed for a call. Foot exams that are due, ordered by how long overdue they are.

The gaps around the glucose get watched too

Reading a glucose chart is the part a diabetes educator trained for. Working out from six supplier and payer sites why a patient has no sensors this month is not.

WebRun takes that part. It is an agent working an ordinary Chrome browser, logged in as a member of your team, opening the supplier site, the payer portal, the eye clinic or the lab and reading what is on the screen.

It runs on your schedule, in a private environment of your own, with sessions kept apart and each workflow restricted to named domains. Gathering runs unattended. Editing a record, sending a message and submitting a form all stop at a draft until a clinician approves them.

The workflows below each name the sites they open.