Here’s a new comparison between the Libre and the Dexcom 505. Unlike one of the previous comparison posted here, this one is utterly “unclean”. In short
- this was a tennis tournament week, with frequent games.
- Max forgot to scan with the Libre, or simply forgot the Libre reader. The straight green lines are those no data periods.
- both sensors were on the arms: we experienced several adhesion issues and patched as we went.
- variability is much higher than usual because we were “pre-loading” a bit for games (not very useful, but better than starting too low anyway) and experienced severe delayed hypos on a couple of occasions, despite minimal levemir doses (5U / 24 hours)
ERRATUM: G4 505 vs Libre - legend copy paste error. Thanks to KS for spotting it.
While I would not draw too many conclusions out of such an awful data set, some comments
It is good to have backup. We lost a Dexcom sensor almost at once (not shown here) and the Libre started dangling after a few days. Interestingly, the Libre started to read a bit too low and sensing delay increased a lot. The yellow marker on the above chart marks the near sensor loss moment. When Max noticed (or paid attention), we used a bit of opsite to stabilize the sensor and normal operation resumed.
The Libre remains, in general, faster than the Dexcom 505 algorithm, and even more so if one looks at spot checks (with the draback that those can be off when the trend changes suddenly). We now have a year or so of side by side data and experience and the result is always the same. Yes, on occasions the Dexcom will pick up a trend before the Libre does (as reflected in historical data) but I don’t remember seeing it picking up a trend before Libre spot checks. Depending on the data set, the optimal correlation between the two signals consistently gives a 6 to 10 minutes advantage to the Libre.
Note: I am not really that interested in collecting additional very clean data. In order to make a rigorous comparison, we need to sync the device clocks on a regular basis, we need precise reference points such as “timecode” BG tests, we need mechanically stable sensors, reminders to scan at least once every 8 hours, etc… All of this adds to the management burden of a teen T1D and that is something I don’t really need.
In practice, that speed advantage needs to be taken with some caution:
- the Libre historical data is computed and corrected a posteriori (as shown here). It is not useful in real time.
- the Libre spot checks are typically faster than historical data, but the delay compensation (combined to the so-so temperature compensation) often introduces overshoots.
Excluding the excursions introduced by the interpolation, the Bland Altman plot is relatively flat. Still I wouldn’t draw any conclusion in terms of absolute slopes/biases because the G4 505 depends to a large extent on the calibration it receives (the nasty non linearity of the original G4 has been reduced in the current sensors/algorithm combo).
I realize quite a few issues I addressed here need a more detailed discussion, more data and detailed examples. Please treat this post as a simple keep-alive ping.