Continuous Glucose Monitors: Does Better Accuracy Mean Better Glycemic Control?

Accuracy is good, but precision is essential.

Data from the Dexcom G6 (blue) and G7 (red).

Introduction

Pop quiz: Your CGM displays a glucose level of 120 mg/dL, but a finger-stick blood glucose meter (BGM) displays 180 mg/dL. What do you do next?

• Take insulin because your “real” blood sugar is high.

• Calibrate your CGM because the BGM is “more accurate”.

• Ignore it because you don’t really understand how all this works anyway.

Sorry to say, it’s a trick question. To actually know what to do, and what not to do, you need to understand a lot more about how glucose actually moves around your body. CGMs report readings, yes, but more importantly, they reveal patterns. And those are where not all CGMs are alike, and where the true nature of T1D management lies. Whether you make your own decisions, or rely on an automated pump, the data is essential. And that’s what brings us to the vastly underappreciated aspect of blood glucose.

The physiological reality is that blood glucose is always moving around your body in different concentrations and in different places. The assumption has always been that CGM data is supposed to match—or come as close as possible to—a finger-prick blood glucose monitor (BGM). But that, and many other assumptions, are oversimplified.

Examine the chart at the top of this article, which is one day from a month-long experiment where I wore the Dexcom G6 and G7 at the same time. (I also tested my blood glucose levels using a BGM.) As you can see, the BGM readings are not really all that useful or predictive of anything, nor do they necessarily help infer anything about either sensor’s data. This isn’t to say a BGM is never useful; it can be. But that leads to the nuance about glucose movement that’s the main point of this article.

A rigorous investigation into how glucose moves around the body can be found in the peer-reviewed paper, Differences in venous, capillary and interstitial glucose concentrations.

The Pleus et al. (2023) study demonstrates that glucose concentrations measured in venous, capillary, and interstitial compartments diverge significantly after a glucose load, with median differences exceeding 30% at 60 and 120 minutes post-ingestion—even in non-diabetic subjects. These discrepancies are not merely technical artifacts, but reflect real physiological compartmentalization and time-lag effects, which are further compounded by device-specific calibration and signal processing.

In other words, the more volatile systemic glucose levels are—that is, your whole body’s glucose levels, not just anywhere in particular—the more variability you’re going to see in each of these compartments. This is why and when a BGM reading rarely matches a CGM. The cases where those levels do match are interesting, but again, let’s pause on that for now.

Much of my article here is based on findings from this and other studies to be cited soon. In the paper cited above, the authors explain some key takeaways. Namely:

• Just because a BGM reads one reading, it very likely has little bearing on whether that represents your actual, systemic glucose level. Nor does it imply your CGM’s reading is valid. Only when glucose levels are very stable for an hour or more might a BGM and CGM align (and potentially represent systemic levels). Yes, this is very useful, and the best time to calibrate a CGM. More on that soon.

• Interstitial fluids, which a CGM reads, is NOT just a lag effect from blood. That can and does happen, primarily in controlled lab studies (which are used to establish CGM “accuracy”), but those are not real-world conditions. As you can see by the chart above, a CGM reading does not represent a “lag” from blood glucose levels. (Note that companies’ claims that their CGMs have a shorter "lag time” is marketing hype.)

• Glucose resides in “compartments” in the body, and movement between compartments is not reliably consistent. Therefore, the only way to reliably infer one’s systemic glucose levels—and more importantly, rates of change—is to gather multiple reads. If a sensor detects intermittent signals—the way the G7 does—those readings are not reflective of systemic glucose levels or movement. Therefore, they should NOT be used to make clinical dosing decisions (for insulin or carbs).

The job of a CGM is to take all this into account and report what is most likely to be an estimate of systemic glucose levels, and the rate of change. The true differences in CGMs rests almost entirely on the algorithm. That’s what the key is to a good CGM, and accordingly, good T1D management.

Self-managing T1D does not require the sophisticated level of understanding of these findings, but only the top-level headline: Learning to see—and react to—glucose patterns is the way to achieve healthy glycemic control. You therefore need a CGM that produces good, reliable, actionable data. Noise is not actionable. This especially true for those who use automated insulin pumps.

“Accuracy” is more of a marketing term than a meaningful measure of a CGM’s utility.

This is not just conjecture—researchers have studied this phenomenon and published their results in the article, “Limits to the Evaluation of the Accuracy of Continuous Glucose Monitoring Systems by Clinical Trials.”

Here, the authors describe the erratic and random patterns of glucose fluctuations, and call into question the appropriateness of how clinical trials for CGMs are conducted in the first place. Popular metrics (like MARD) can be misleading without considering trends and consistency.

Real-World Scenario

Let’s return to the chart at the top of this article, which I’ve copied below. It shows CGM data from both the G6 and G7 that I wore at the same time. The G7, in red, is purportedly “more accurate” than the G6 because it meticulously measures each sample of fluid. The G6, by contrast, is doing a more sophisticated analysis on a series of signals it gets from the sensor and makes a more “precise” inference on what the body’s glucose levels are. No, this is not just a matter of “smoothing” the data. Determining “precision” is a far more physiological complex algorithm than merely smoothing out those erratic anomalies that the G7 detects. You can see that by simply looking at the data points associated with each sensor:

With all we’ve covered to this point, let’s return to the pop quiz at the beginning: A finger-prick blood glucose test shows 180 mg/dL, while the CGM shows 120. If you were to treat the 180 value as “correct,” and administer 2u of insulin, that may work… or it might be an overkill if the 180 value was more of an anomaly due to the erratic nature of glucose movement. Here, the CGM value of 120 might have been correct.

If you’re a T1D and learning to make in-the-moment management decisions—or rely on an automated insulin pump to read this data—knowing this is important.

Let’s put it to the test: Below is a familiar screenshot from the Dexcom G6 app:

The “down arrow” on this Dexcom reading indicates glucose levels are dropping. And yes, 75 is definitely low. But you can’t infer very much more than that. How fast is it dropping? How high was it before? How long did it take to get from that peak to this level? This is what you need to know to make an informed decision on what to do next.

Let’s expand to see the whole chart now:

Here, we see that the levels were quite high (180s), then dropped to roughly the 150s, and then suddenly took a dive in the last 30 minutes. But we can also see that it’s starting to level off. Yes, only ONE reading suggests this tapering off. This is really important because it means you can anticipate near-term patterns reliably, say 30m from now.

That’s why I ignore directional arrows—it can’t answer these questions. And worse, it can be misleading, as the downarrow may continue until glucose levels rise. If the pattern suggests it’s already leveling off, and you only look at the arrow, you may think it’s still dropping, and needless eat—or eat too much.

In this case, I knew that the leveling off would imply that I should not eat anything; I don’t want to overreact and have a glucose spike.

Looking at the chart later, after time has passed, we see more information.

Hey! 108 is a good number, and the slight upward trend doesn’t bother me. Still, I’ll keep an eye on it.

Here’s the thing that made all this happen: I TRUSTED THE G6 DATA. It was smooth, the trend line was reliable, and the readings did not wobble around. Most importantly, it was TIMELY. I was able to make an in-the-moment decision when it was at 75. By contrast, if the data was “wobbly,” I would have had to wait longer—potentially much longer—before the pattern stabilized, and by then, it might have been too late had I actually needed an intervention.

To illustrate the wobbly nature of data, let’s look at that G6/G7 chart and zoom in on the 4:00pm window. Here’s an enlargement of that data:

A two-hour time window of G6 and G7 glucose readings

The G6 data is smooth, but the G7 is bouncing all around like a buoy bobbing in turbulent ocean waters. Each G7 reading may well be “accurate” in isolation, but they offer no help in determining directionality or rate of change.

I’ll return to this screenshot later in this article, but you can easily see that the differences between the G6 and G7 are clear and obvious: I can rely on the G6 data to make an informed decision, but anomalous spikes or dips that the G7 produces are intermittent and—by themselves—are entirely unreliable.

Now, let’s be honest. you may not be watching your CGM like this. In fact, you may be using an automated insulin pump to do that work. But remember, those systems are doing exactly the same read-by-read analysis that I do for myself, making the same in-the-moment decisions. No algorithm can figure out G7 data any better than you can. So, those systems won’t work if the data being observed is not reliable enough. Garbage in, garbage out.

And that’s where the risk lies with G7 data. But more importantly, that’s where the risk lies with so-called “accurate” data. You don’t want accuracy, you want precision.

Read that bold text again—seriously. Out loud. With a British accent if you must. It’s that important.

Now let’s expand this to the wider data I collected over a month

Does the G7 yield greater glucose control?

Before I explain how I tested the G6 vs the G7, I need to make it clear that Dexcom’s clinical trial that demonstrated the MARD level for the G7 was not intended to claim that the G7 resulted in healthier outcomes. That’s a very different goal. The company only intended to conduct an “efficacy trial,” which is only intended to show that the sensor was good enough to be approved by the FDA.

What Dexcom did not do is perform an “effectiveness trial,” which is when test subjects would wear each of the two sensors and make real-time management decisions under real-world conditions. I explain this in much greater detail in my article on how to evaluate clinical trials.

Since no trials have tested the G7 this way, I did it on myself. As it happens, my T1D is under very tight control, where my time in range is 95%, with <2% below range (70 mg/dL) and <4% above range (180 mg/dL).

NOTE: I do not aim for this level of tight control. I do not have “targets” in mind. I am not fanatical or obsessed about numbers. I am not on a low-carb diet. I merely follow the four basic habits of T1D management, which I describe in my article, The Four Habits of Healthy T1Ds. Habit #1: Watch your CGM and get to know your patterns; Habit #2: Make small interventions with carbs or insulin “as needed.”

You can read the article to see what habits #3 and #4 are.

During March, 2023, I wore both the G6 and G7 at the same time, but would only observe data from one sensor’s app at a time to make real-time management decisions. That’s right, I did NOT look at both apps and compare them in real-time. My goal was to determine which data made it easier or better to make in-the-moment decisions. After a period of a few days, I switched to the other sensor’s app. I repeated this back-and-forth between the two sensors several times.

Upon completion of the experiment, I downloaded all my data to Excel and analyzed it to see how my TIR varied between the two. I also collected data for insulin (InPen bluetooth enabled insulin pen), carbohydrates, exercise, sleep, and glucose levels from my Contour Next One blood glucose meter (BGM), which I included in my analysis report.

The graphic below is the topline dashboard from my month wearing both the G6 and G7:

Dashboard stats for the G6 and G7 during March 2023

The first thing that pops out is that the G7 reported glucose values ~5% lower than the G6, which is consistent with what others have reported online. Aside from that, the two sensors appear roughly equivalent: The G6 averaged 121 mg/dL, versus the G7’s 116, and the standard deviations (SD) were 33 vs. 34, respectively. 

But the real difference between the two sensors is shown by the time-in-range (TIR) stats on a day-by-day basis, as shown in the following graph:

Time-in-Range (TIR) charts for the G6 and G7

You’ll notice the periodic pattern, where my TIR is very high, followed by days when my TIR slipped. These variations are entirely due to which sensor’s data I looked at the make in-the-moment decisions. When I used the G6 to make decisions, I achieved a TIR of >90%. When I used the G7, my TIR dropped to the ~70% range. The reason is obvious: The G7 data would at time present patterns that looked like my glucose levels were moving in a particular direction at a particular rate, which would have meant either taking insulin or consuming carbs. But in actuality, those patterns were anomalies, so my actions would cause my real glucose levels to go off in the wrong direction. And sometimes, dangerously so.

Let’s zoom into the two-hour window between 4-6pm that I illustrated earlier. This kind of movement is highly representative of the kind of volatility seen in the G7 versus the G6, and why it’s hard to make real-time decisions.

A two-hour time window of G6 and G7 glucose readings

Remember, I couldn’t see the G6 data (the smoother blue graph), so at 5:30pm, and with only the G7 data in view, I saw the very rapid rise from 88 to 155 in a matter of 30 minutes. Granted, the data leading up to that was highly erratic, but these successive readings were not–they were decisively rising, and fast. Without any idea where these levels might top out, especially given the rapid rate of change, I thought I needed to start bolusing.

As I always do, I began with small, incremental boluses, keeping a close eye on those glucose levels as they rise, waiting to see when they level off or begin to fall. The goal is to avoid taking too much, or too little. I’m aiming for the Goldilocks effect.

Turns out, the G7’s data shot up to 270. If this really was my real glucose level, the stacked boluses I’d taken would have perfectly corrected these readings, and I would have had a soft landing. But, as the insulin started to kick in, my glucose levels plummeted to 49, making it clear to me that the G7 readings were not giving me reliable information. Individual readings may have been “accurate,” but they were not representative of my actual systemic glucose levels.

To achieve tight glucose control, one must be able to look at short time windows, and respond quickly to glucose movements to glucose movements, even if they are finely tuned adjustments. (Most people aren’t in tight control, and typically work on bigger time windows, so they won’t be as affected by these erratic readings.)

Over time, these anomalous readings will create more errors in decisions (or pump algorithms) than successes, which will impose an upper limit on how well they can ever perform.

Below are more daily charts to consider (without additional commentary). You can zoom in on your own and guess how/why I was able–or unable–to see trends in time to make decisions proactively.

The G7 generally reports lower BG values

While both the G6 and G7 were tighter (SD=29 and 28), the G7’s volatility is apparent.

The G7 appears to behave better this day, but real-time decisions were based on G6 data

The day was 100% in range, but the G7’s data was all over the map. (Thanks, G6!)

The Dexcom G7 trial: Exploring the futility of “accuracy.”

In Dexcom’s published report, “Accuracy and Safety of Dexcom G7 Continuous Glucose Monitoring in Adults with Diabetes,” 318 diabetic subjects wore three G7 sensors simultaneously over the course of ten days. For three of these days, subjects underwent clinically induced hyperglycemia and hypoglycemia under controlled conditions, where blood samples were taken and measured using a reference blood glucose sensor, the YSI 2300 Stat Plus glucose analyzer. The analysis showed that the “mean absolute relative difference” (MARD) between the two was ~8.8% for the G7, versus ~10% for the G6. The lower the percentage, the smaller the difference to the reference analyzer. Hence, greater accuracy.

Let me remind the reader that the G7 trial had subjects where THREE G7s simultaneously during the testing period. When blood samples were taken and measured on the iStat device, it then compared that value to G7 readings.

Ok, wait. If the person was wearing three G7’s, which one was used to compare measurements? Or were all three averaged together? Or, did Dexcom choose which of the three that happened to be closest to the iStat? The company doesn’t reveal this in the trial data, and that alone raises eyebrows to me.

All this further substantiates the paper I cited earlier about the inappropriateness of using CGM values against a single-read iStat device. Any claims about MARD should not be taken at face value.

Moreover, MARD values in Dexcom’s data varied widely, especially under different conditions, such as glucose levels and rates of change, as shown in this figure from their report.

The mean and median per-sensor MARDs were 8.8% and 7.8%, respectively, 442 (71.4%) had MARD values <10%, and 12 (1.9%) had MARD values >20%.

According Dexcom’s data, the G7’s MARD value was best when glucose values were in the sweet spot of glycemic ranges, but diminished as glucose levels edged higher. This bar graph suggests the best MARD happened most often at ideal glucose ranges, but most T1Ds only spend about 30% of their day in those ranges. The rest of their day is spent far outside, usually well above 180 mg/dL, where the G7’s MARD rating is well above 14%.

What is also not revealed in Dexcom’s report is the rate of change (ROC), which can also greatly affect MARD. Dexcom limited its testing to only 1 mg/dL change per minute, which showed some of the worst performing MARD values. In the real world, once a T1D eats a meal, glycemic levels can change at 2-4 mg/dL per minute as a matter of course. Relying on CGMs to capture that data is prone to significant error bars. (The G6’s algorithm is far superior in this regard for smoothing out these errors and giving the user or algorithm more reliable data to work with.)

To what degree this variability in MARD plays into real-world conditions, we can look at this meta-analysis of multiple studies on overall glucose levels for T1Ds who wear CGMs. It shows that only 30% of T1Ds have glucose ranges between 70-180 mg/dL 70% of the time, which is where the G7 is most accurate. By contrast, 80% of T1Ds spend more than 70% of their time above 180 md/dL, where the G7’s accuracy exceeds 30% error. (For context, 44.5% have an A1c between 7–9%, 32.5% exceed 9%, and only 23% of T1Ds had an A1c <7%.)

Despite the fact that the G7 is the most accurate at glucose levels between 70-180, T1Ds spend far more time far above 180. Hence, T1Ds are experiencing accuracy error rates of >30% most of the time. This means that decisions that either humans or algorithms are going to make in whether to dose insulin or carbs are dealing with highly imperfect information (especially compared to the G6, which was more reliable.

Summary

I personally suspect that few people will find the G7 helps T1Ds improve their glycemic control. This will also be a problem for automated insulin pumps for the same reasons.

Nevertheless, I suspect Dexcom is primarily focused on the value of the improved MARD rating in their marketing plans. It’s invaluable to claim that your MARD is superior to all other CGMs, regardless of the dubious value of MARD.

It also helps that Dexcom’s target market is moving well beyond T1Ds into the T2D market, where there are nearly 40 million T2Ds, with another 98 million presumed to be undiagnosed. That, plus a very rapidly emerging market of non-diabetic “life-hackers”, such as athletes, health enthusiasts, and everyday consumers. In fact, Dexcom has released a non-prescription version of the G7 called Stelo, and these people don’t care that much about volatility.

Of course, the downside for T1Ds is that some could actually see worse outcomes, and not even realize it. The G7’s propensity to report lower average glucose averages (than what is actually in the bloodstream) may give people the false impression that their glycemic control has actually improved with the G7.

I hope the G6 never goes away. But a better idea is to provide the G6’s algorithms to a G7 sensor. Here’s a marketing plan: Sell the G7 with the G6 algorithm as the less expensive over-the-counter product for the comparatively fewer number of T1Ds that actually need higher quality data—that is, better precision—to manage glucose levels. We’re already paying too much for all the other stuff we have to buy, and we’re a tiny market compared to the rest of the world. This way, everyone’s a winner!