Devices › Integrated continuous glucose monitoring system, factory calibrated
Device brand name · Continuous glucose monitor
Dexcom Follow App: medical device reports filed with FDA
277 reports name it, 2019–2026. Manufacturer given most often on reports: Dexcom. Product code QBJ.
- 277
- device reports naming the brand
- 0% of all MAUDE reports · about 38 a year
- 30
- reports, 12 months to August 2026
- 46 in the 12 months before
- 94.6%
- classified as malfunction
- 98.1% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 277 reports that name the brand "Dexcom Follow App" (continuous glucose monitor), received between April 2019 and July 2026; the manufacturer given most often on reports is Dexcom. Spellings of one product vary from report to report.
30 reports arrived in the 12 months to August 2026, down 35% from 46 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are malfunction (94.6%) and injury (5.4%); across all integrated continuous glucose monitoring system, factory calibrated reports (product code QBJ) death is recorded in 0% and malfunction in 98.1%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are unintended application program shut down (33.9%), wireless communication problem (29.6%) and no audible alarm (11.6%). The patient problems coded most often are hypoglycemia, coma and confusion/ disorientation. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 2,268,325 reports carrying product code QBJ. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| Unintended application program shut down | 94 | 33.9% | 3.1% |
| Wireless communication problema wireless connection problem | 82 | 29.6% | 35.7% |
| No audible alarm | 32 | 11.6% | 0.7% |
| Operating system version or upgrade problem | 16 | 5.8% | 0.4% |
| Defective alarm | 12 | 4.3% | 0.7% |
| Application program freezes or fails to launch | 8 | 2.9% | 0.2% |
| Display or visual feedback problem | 6 | 2.2% | 0.5% |
| Insufficient device problem information | 5 | 1.8% | 0% |
| Alarm not visible | 2 | 0.7% | 0% |
| Connection problema connection problem | 2 | 0.7% | 0.4% |
| Application program problem | 1 | 0.4% | 0% |
| Incorrect, inadequate or imprecise result or readings | 1 | 0.4% | 10.4% |
| Intermittent program or algorithm execution | 1 | 0.4% | 0% |
| Low audible alarm | 1 | 0.4% | 0.1% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Hypoglycemialow blood sugar | 9 | 3.2% |
| Coma | 1 | 0.4% |
| Confusion/ disorientation | 1 | 0.4% |
| Fatiguetiredness | 1 | 0.4% |
| Hyperglycemiahigh blood sugar | 1 | 0.4% |
| Hypothermia | 1 | 0.4% |
| Seizures | 1 | 0.4% |
| Sleepiness/drowsiness/somnolence | 1 | 0.4% |
| Vomitingbeing sick | 1 | 0.4% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Dexcom Follow App | Product code QBJ | All MAUDE reports |
|---|---|---|---|
| Reports | 277 | 2,268,325 | 26,136,888 |
| Share of that pool | — | 0% | 0% |
| Classified as death, per 1,000 reports | 0 | 0 | 9 |
| Classified as injury | 5.4% | 1.9% | 36.2% |
| Classified as malfunction | 94.6% | 98.1% | 62.3% |
| Filed by the manufacturer | 99.6% | 99.7% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code QBJ
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Dexcom G6 Continuous Glucose Monitoring System | 1,339,562 | 61,710 | 0% |
| Dexcom G7 Continuous Glucose Monitoring System | 641,507 | 268,781 | 0% |
| FreeStyle Libre 3 | 120,677 | 103,045 | 0% |
| FreeStyle Libre 3 Plus | 91,348 | 88,323 | 0% |
| FreeStyle Libre 2 Plus | 49,668 | 45,839 | 0% |
| Dexcom G7 15 Day Continuous Glucose Monitoring System | 13,869 | 13,869 | 0% |
| Dexcom G6 Glucose Program Continuous Glucose Monitoring System | 5,664 | 1,759 | 0% |
| Libre 3 Sensor FreeStyle | 12,829 | 2 | 0% |
| FreeStyle Libre 2 Plus Sensor | 3,929 | 2,799 | 0% |
| Dexcom G6 Mobile Continuous Glucose Monitoring System | 1,833 | 0 | 0% |
| Dexcom ONE Continuous Glucose Monitoring System | 1,550 | 189 | 0% |
| Dexcom G7 | 1,394 | 583 | 0.1% |
| Libre 2 Plus Sensor FreeStyle | 808 | 10 | 0% |
| Libre 3 Plus Sensor Freestyle | 585 | 13 | 0% |
| Dexcom G7 Sensor | 436 | 137 | 0.2% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Dexcom Follow App reports
How many FDA reports name Dexcom Follow App?
277 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 30 in the latest 12 months.
What kinds of events are reported?
malfunction (94.6%) and injury (5.4%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
unintended application program shut down (33.9%), wireless communication problem (29.6%), no audible alarm (11.6%), operating system version or upgrade problem (5.8%) and defective alarm (4.3%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.6%) and voluntary reports (0.4%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Dexcom Follow App was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.