Devices › Sensor, glucose, invasive
Device brand name · Sensor glucose invasive
Dexcom G6 Sensor: medical device reports filed with FDA
364 reports name it, 2019–2026. Manufacturer given most often on reports: Dexcom. Product code MDS.
- 364
- device reports naming the brand
- 0% of all MAUDE reports · about 49 a year
- 14
- reports, 12 months to August 2026
- 27 in the 12 months before
- 25.3%
- classified as malfunction
- 94.9% across the product code
- 0.8%
- classified as death, as reported
- 3 reports · not verified by FDA
364 medical device reports received by FDA name the brand "Dexcom G6 Sensor" (sensor glucose invasive); the manufacturer given most often on reports is Dexcom; received from January 2019 to April 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
14 reports arrived in the 12 months to August 2026, down 48% from 27 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 injury (73.6%), malfunction (25.3%) and death (0.8%); across all sensor, glucose, invasive reports (product code MDS) death is recorded in 0.1% and malfunction in 94.9%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are patient-device incompatibility (22.5%), incorrect, inadequate or imprecise result or readings (15.4%) and product quality problem (6.9%). The patient problems coded most often are rash, itching sensation and hyperglycemia. 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 282,102 reports carrying product code MDS. 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 |
|---|---|---|---|
| Patient-device incompatibilitythe device did not suit the patient | 82 | 22.5% | 0.1% |
| Incorrect, inadequate or imprecise result or readings | 56 | 15.4% | 0.6% |
| Product quality problem | 25 | 6.9% | 0% |
| Therapeutic or diagnostic output failure | 17 | 4.7% | 0% |
| Defective devicethe device was defective | 11 | 3% | 0% |
| High readingsreadings were too high | 11 | 3% | 0% |
| Device sensing problem | 8 | 2.2% | 0% |
| Device markings/labelling problema problem with the device markings or label | 7 | 1.9% | 0% |
| Patient device interaction problem | 7 | 1.9% | 0% |
| Detachment of device or device componentpart of the device came off | 6 | 1.6% | 0.1% |
| Difficult to removethe device was hard to remove | 6 | 1.6% | 0% |
| Low readingsreadings were too low | 6 | 1.6% | 0% |
| Physical resistance/sticking | 6 | 1.6% | 0.3% |
| Retraction problem | 6 | 1.6% | 0% |
| Device ingredient or reagent problem | 5 | 1.4% | 0% |
| Difficult to insertthe device was hard to insert | 5 | 1.4% | 0% |
| Separation failure | 5 | 1.4% | 0% |
| Activation, positioning or separation problem | 4 | 1.1% | 0% |
| Connection problema connection problem | 4 | 1.1% | 0.1% |
| Wireless communication problema wireless connection problem | 4 | 1.1% | 21.3% |
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 |
|---|---|---|
| Rashskin rash | 80 | 22% |
| Itching sensation | 68 | 18.7% |
| Hyperglycemiahigh blood sugar | 38 | 10.4% |
| Erythemaskin redness | 29 | 8% |
| Painpain, site not specified | 27 | 7.4% |
| Caustic/chemical burns | 26 | 7.1% |
| Skin irritationirritated skin | 24 | 6.6% |
| Hypoglycemialow blood sugar | 23 | 6.3% |
| Hypersensitivity/allergic reaction | 21 | 5.8% |
| Blistera blister | 19 | 5.2% |
| Hemorrhage/blood loss/bleeding | 16 | 4.4% |
| Reactiona reaction, type not specified | 13 | 3.6% |
| Skin inflammation/ irritation | 13 | 3.6% |
| Fluid discharge | 10 | 2.7% |
| Inflammationinflammation | 9 | 2.5% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Dexcom G6 Sensor | Product code MDS | All MAUDE reports |
|---|---|---|---|
| Reports | 364 | 282,102 | 26,136,888 |
| Share of that pool | — | 0.1% | 0% |
| Classified as death, per 1,000 reports | 8 | 1 | 9 |
| Classified as injury | 73.6% | 4.8% | 36.2% |
| Classified as malfunction | 25.3% | 94.9% | 62.3% |
| Filed by the manufacturer | 0% | 99.6% | 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 MDS
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Dexcom G5 Mobile Continuous Glucose Monitoring System | 332,492 | 6 | 0% |
| Dexcom G4 Platinum Continuous Glucose Monitoring System | 53,681 | 0 | 0.1% |
| G4 Platinum Continuous Glucose Monitoring System | 48,906 | 0 | 0.1% |
| Dexcom G4 Platinum Continuous Glucose Monitoring System Dexcom Share System | 17,717 | 0 | 0.1% |
| Xmtr MMT-7811NA GST3C Lockout | 17,012 | 65 | 0% |
| Animas Vibe | 88,703 | 0 | 0% |
| Paradigm Real-Time Insulin Infusion Pump | 126,282 | 0 | 0.3% |
| Unknown XMTR | 4,431 | 2,027 | 0% |
| Carelink Personal Mmt-7333 | 3,680 | 233 | 0% |
| Guardian Link 3 OUS | 6,663 | 733 | 0% |
| Ni | 32,939 | 1,587 | 1.8% |
| Dexcom G4 Platinum Continuous Monitoring System Dexcom Share System | 2,293 | 0 | 0.3% |
| Paradigm Real-Time Revel Insulin Infusion Pump | 178,691 | 0 | 0.6% |
| Transmitter Mmt-7841zw Gst5g Ous | 31,572 | 12,351 | 0% |
| Xmtr Mmt-7821lna Gst4c Replacement | 1,685 | 13 | 0% |
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 G6 Sensor reports
How many FDA reports name Dexcom G6 Sensor?
364 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 14 in the latest 12 months.
What kinds of events are reported?
injury (73.6%), malfunction (25.3%) and death (0.8%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
patient-device incompatibility (22.5%), incorrect, inadequate or imprecise result or readings (15.4%), product quality problem (6.9%), therapeutic or diagnostic output failure (4.7%) and defective device (3%). These are FDA's device problem codes as entered on the report.
Who files these reports?
voluntary reports (99.7%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Dexcom G6 Sensor 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.