Remote Patient Monitoring for Diabetes: Glucose Data Review and Escalation Workflows That Hold Up

A three-physician primary care practice had dozens of patients wearing continuous glucose monitors, all uploading to the manufacturer’s clinic portal. The data was there, every five minutes, for weeks at a time. Nobody opened it until a patient came in for a visit. One patient’s overnight lows showed up in the portal for nearly a month before anyone looked, and the physician found them the morning of a routine follow-up.

The practice had the data and the concern. What it lacked was an owner and a sorting rule. Diabetes monitoring produces more data than any other RPM program, and it arrives through two different tracks: connected glucometers that send individual readings, and CGMs that send a continuous stream. Each track has its own codes, its own review rhythm, and its own way of going wrong.

This article lays out how remote patient monitoring for diabetes works on both tracks, how to pick the right billing track before enrollment, a review model that sorts every day’s data into three response windows, the mistakes we see most, and how to scale the review as the program grows. It comes from the diabetes monitoring programs Care VMA supports in independent primary care and endocrinology practices.

The CGM Data Nobody Opened Until the Visit

That practice, in central Pennsylvania, had assumed the portal’s alerts would surface anything urgent. They did, for the patients who had alerts switched on. For everyone else, the data simply sat there. No staff member had the portal in their daily routine, and the physicians reviewed reports only when a patient was on the schedule.

The fix started with something small. One medical assistant opened the portal every morning at 8:30, checked every enrolled patient against a short list of physician-written criteria, and routed anything that met them to the nurse before the first patient arrived. Within a few weeks, the physicians were seeing problems days after they started instead of at the next visit.

What Remote Patient Monitoring for Diabetes Includes

Connected Glucometer Monitoring

The patient checks blood glucose with a fingerstick meter that transmits each reading automatically to the practice, usually over a cellular connection. The care team sees individual readings, often a few a day, and reviews them for out-of-range values and trends. This track uses the standard RPM codes and suits many patients with type 2 diabetes who aren’t on a CGM.

Continuous Glucose Monitoring

A sensor worn on the body measures glucose every few minutes and sends the data to a reader or smartphone app, which shares it with the practice through the manufacturer’s clinic portal. The team sees a continuous picture, including overnight patterns, time spent in and out of the target range, and summary reports such as the ambulatory glucose profile (AGP). This track has its own CPT code family.

The Two Tracks Side by Side

Why Glucose Data Overwhelms Practice Teams

Volume is part of it. A single CGM patient generates more data points in a day than a blood pressure patient sends in a year. Without a rule for what to look at, staff either look at everything or nothing.

Fragmentation is the other part. Glucometer readings may land in an RPM platform, CGM data in one or two manufacturer portals, and the care plan in the EHR. Each system has its own login, its own alerts, and its own idea of what’s urgent. A nurse who has to check four screens before 9 AM will eventually check two.

And the most important problems don’t look urgent. A steady climb in post-dinner readings over three weeks never trips an alert, yet it’s exactly the pattern that calls for a medication or education change before the next quarterly visit.

Choose the Billing Track Before the First Reading

Glucometer Patients Use RPM Codes

For patients on a connected glucometer, the standard RPM rules apply: an established patient relationship, documented consent, a device furnished by the practice that transmits readings automatically, the minimum days of data in each 30-day period, and monthly treatment management time that includes a real-time conversation with the patient. Manually entered readings don’t count toward the data days. Our complete RPM billing guide covers each code and its documentation.

CGM Patients Use the CGM Code Family

CGM work has its own codes: 95249 for starting a patient on their own CGM (once per device), 95250 for a professional CGM using office equipment, and 95251 for the monthly analysis, interpretation, and report by a physician or other qualified practitioner. CPT directs CGM work to these codes instead of the RPM setup and device supply codes. Whether RPM treatment management time can also be billed for a CGM patient, and how it sits next to 95251 in the same month, depends on your MAC and payers. Confirm it before you build the workflow.

A five-physician family medicine group we started working with had been billing RPM setup and device codes for patients whose only device was a personal CGM. The claims had mostly paid, which is why nobody noticed. Separating the program into a glucometer track and a CGM track, each with its own code set and documentation template, ended the mismatch and gave the physicians a clean monthly 95251 workflow.

Diabetes RPM Alongside Care Management

Many diabetes patients also qualify for chronic care management. The programs can run together for the same patient when each program’s requirements are met separately and the same minutes aren’t counted twice. Track time by program from the first day.

The Now, Soon, Next Visit Glucose Review Model

Every reading or pattern your team reviews should land in one of three response windows. The windows decide who acts and how fast.

Step 1: Have Your Physicians Write the Thresholds

Before the first patient enrolls, the physicians define the criteria for each window: which values, symptoms, or patterns go to Now, Soon, or Next Visit, and whether any criteria differ for patients on insulin or with a history of severe lows. The criteria belong in a signed protocol, not in a nurse’s memory. Staff apply them; physicians own them.

Step 2: Sort Every Day’s Data Into Three Windows

Now

Readings or patient reports that meet the physicians’ urgent criteria, such as a value in the dangerous range or symptoms the protocol flags. These go to a licensed clinician the same day, with a direct call to the patient and an escalation to the physician if the protocol calls for it. Patients should also be told plainly, at enrollment, that monitoring isn’t an emergency service and what to do if they feel unwell.

Soon

Patterns that need a clinical look within a few days: repeated lows at the same time of day, a steady climb in readings, or a CGM showing more time above range than last month. The nurse or diabetes educator reviews these, contacts the patient, and brings anything needing a medication change to the physician. Most of the program’s clinical value sits in this window, because these are the problems that never look urgent on a single day.

Next Visit

Everything within the expected range, plus observations worth discussing at the next appointment. These are logged for the monthly review and the visit, without a call.

Step 3: Review CGM Patterns on a Schedule

Daily sorting catches individual events. CGM patterns need a scheduled look. Many practices review flagged CGM patients weekly in the “Soon” window and run a full pattern review for every CGM patient monthly, which is also when the physician completes the interpretation and report.

Step 4: Close the Loop

A review that ends in a decision has to end in an action: a visit scheduled, a dose change documented and communicated, an education session booked, a refill sent. For practices running diabetes patients through both monitoring and care management, Care VMA’s chronic care management support can handle those follow-up calls, scheduling, and reminders so the clinical team’s decisions don’t stall in the inbox. Our article on managing diabetes patient appointments covers the scheduling side in more detail.

Mistakes That Break Diabetes Monitoring Programs

Treating Every Alert as Urgent

If everything is urgent, staff learn to ignore the alerts. Physician-defined windows give each reading a place.

Reviewing CGM Data Only at Visits

A CGM worn for three months between visits holds three months of patterns. Looking at it once, in the exam room, wastes most of it.

Mixing the Code Families

RPM device codes for CGM patients, or CGM codes for glucometer patients, create claims that can come back years later in an audit.

No Workflow for Data Gaps

A sensor that fell off, a meter that stopped syncing, or a patient who stopped checking all look the same in the data: silence. Give data gaps their own daily list and their own owner.

Escalating Without Documentation

A text to the physician’s phone isn’t a record. Every Now and Soon escalation needs to land in the chart with the reading, the action, and the outcome.

Running Diabetes RPM at Scale

Split the Review by Skill

A four-physician endocrinology practice we support split its glucose review into three layers once the program passed a few hundred patients. A medical assistant ran the morning sort against the written criteria and worked the data-gap list. A certified diabetes educator handled the Soon window and the patient conversations. The physicians reviewed escalations and completed the monthly CGM interpretations. Each person worked at the top of their license, and the physicians stopped scrolling through portals between patients.

Let the Data Set Visit Timing

Monitoring data can tell you which patients need to come in sooner and which can safely stay on their regular schedule. Practices that let the monthly review drive scheduling use their appointment slots where they matter most. Our article on virtual medical assistants for endocrinology covers the front-office side of that shift.

Watch the 2027 Proposals

CMS has proposed, for 2027, that RPM be furnished only by clinical staff who are direct employees of the billing practice and that monitoring start with a face-to-face initiating visit. These are proposals until the final rule is published, expected in early November 2026. If finalized, they would shape who on your team performs the billable review work, so plan your structure with that line in mind.

Decide the Track, Sort the Data, Own the Follow-Up

Remote patient monitoring for diabetes works when three decisions are made early. Put each patient on the right track (connected glucometer RPM or CGM) with the right code set. Have your physicians write criteria that sort every day’s data into Now, Soon, and Next Visit. And give someone ownership of the follow-up, from data gaps to scheduled visits.

There’s an honest limit here. This is a workflow framework. Glucose thresholds, escalation criteria, and treatment changes belong to your physicians, and billing for CGM patients varies by payer and MAC. Confirm both before you launch or restructure.

The work that usually falls through is the coordination around the review: enrolling patients, getting meters shipped and sensors connected to the clinic portal, chasing the patients whose data went quiet, and preparing the monthly lists your clinicians work from. That’s the part Care VMA’s remote patient monitoring support is built to carry, so your clinical team can spend its time in the Now and Soon windows.

If your glucose data is piling up between visits, book a free consultation with the Care VMA team. We’ll map your current review process against the three windows and show you where the follow-up is getting lost.

Frequently Asked Questions

How does remote patient monitoring work for diabetes?

Patients either use a connected glucometer that transmits each fingerstick reading to the practice or wear a CGM that shares continuous data through the manufacturer’s clinic portal. The care team reviews the data between visits, contacts patients when readings or patterns meet physician-defined criteria, and escalates to the physician when treatment may need to change.

Can you bill RPM codes for CGM patients?

CPT directs CGM work to its own codes: 95249 or 95250 for setup and recording, and 95251 for monthly interpretation and report. The RPM setup and device supply codes are meant for other devices, such as connected glucometers. Whether RPM treatment management time can also be billed for a CGM patient depends on your MAC and payers, so confirm it first.

Who should review remote glucose data in a practice?

A common split is a medical assistant who sorts data each morning against written criteria and works the data-gap list, a nurse or diabetes educator who handles patterns and patient conversations, and a physician who reviews escalations and completes CGM interpretations. The physicians define the criteria everyone works from.

How often should CGM data be reviewed between visits?

Many practices check for urgent events daily, look at flagged patients weekly, and run a full pattern review for every CGM patient monthly. The right rhythm depends on your patient mix and your physicians’ protocol.

What should trigger an escalation in a diabetes RPM program?

The triggers should come from a physician-signed protocol: specific glucose values, symptoms, and patterns, sorted into same-day, within-a-few-days, and next-visit windows. Staff apply the criteria; physicians own them and review them on a schedule.

What happens when a patient’s glucose data stops coming in?

Treat it as its own workflow. A missing reading can mean a dead sensor, a meter that stopped syncing, or a patient who stopped checking. A daily data-gap list with a clear owner gets patients back on track before the month’s data requirements are missed.