Devices › Sensor, glucose, invasive
Device brand name · Sensor glucose invasive
Unknown XMTR: medical device reports filed with FDA
4,431 reports name it, 2023–2026. Manufacturer given most often on reports: Medtronic Minimed. Product code MDS.
- 4,431
- device reports naming the brand
- 0% of all MAUDE reports · about 1,268 a year
- 2,027
- reports, 12 months to August 2026
- 959 in the 12 months before
- 99.5%
- classified as malfunction
- 94.9% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 4,431 reports that name the brand "Unknown XMTR" (sensor glucose invasive), received between January 2023 and August 2026; the manufacturer given most often on reports is Medtronic Minimed. Spellings of one product vary from report to report.
2,027 reports arrived in the 12 months to August 2026, up 111% from 959 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 (99.5%) and injury (0.5%); 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 wireless communication problem (97.3%), communication or transmission problem (7.2%) and battery problem (2.7%). The patient problems coded most often are hyperglycemia, hemorrhage/blood loss/bleeding and hypoglycemia. 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 |
|---|---|---|---|
| Wireless communication problema wireless connection problem | 4,311 | 97.3% | 21.3% |
| Communication or transmission problemthe device could not communicate or transmit | 317 | 7.2% | 2.7% |
| Battery problema problem with the battery | 120 | 2.7% | 1.5% |
| Display or visual feedback problem | 97 | 2.2% | 0.6% |
| Calibration problem | 74 | 1.7% | 0.3% |
| Incorrect, inadequate or imprecise result or readings | 37 | 0.8% | 0.6% |
| Inappropriate or unexpected reset | 6 | 0.1% | 1.1% |
| Breakthe device broke | 5 | 0.1% | 0.8% |
| Patient device interaction problem | 3 | 0.1% | 0% |
| Activation problem | 1 | 0% | 0% |
| Computer software problema software problem | 1 | 0% | 1.2% |
| Failure of device to self-test | 1 | 0% | 0.1% |
| Manufacturing, packaging or shipping problem | 1 | 0% | 0% |
| Material integrity problema problem with the device material | 1 | 0% | 0% |
| Material twisted/bent | 1 | 0% | 0% |
| Moisture or humidity problem | 1 | 0% | 0% |
| Obstruction of flow | 1 | 0% | 0% |
| Power problem | 1 | 0% | 0% |
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 |
|---|---|---|
| Hyperglycemiahigh blood sugar | 166 | 3.7% |
| Hemorrhage/blood loss/bleeding | 91 | 2.1% |
| Hypoglycemialow blood sugar | 64 | 1.4% |
| Bruise/contusion | 9 | 0.2% |
| Elevated ketones/ diabetic ketoacidosis | 9 | 0.2% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 6 | 0.1% |
| Malaisegeneral feeling of being unwell | 6 | 0.1% |
| Fatiguetiredness | 3 | 0.1% |
| Vomitingbeing sick | 3 | 0.1% |
| Confusion/ disorientation | 2 | 0% |
| Discomfortdiscomfort | 2 | 0% |
| Hypoglycemic shock | 2 | 0% |
| Diaphoresis | 1 | 0% |
| Distress | 1 | 0% |
| Dizzinesslight-headedness or unsteadiness | 1 | 0% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Unknown XMTR | Product code MDS | All MAUDE reports |
|---|---|---|---|
| Reports | 4,431 | 282,102 | 26,136,888 |
| Share of that pool | — | 1.6% | 0% |
| Classified as death, per 1,000 reports | 0 | 1 | 9 |
| Classified as injury | 0.5% | 4.8% | 36.2% |
| Classified as malfunction | 99.5% | 94.9% | 62.3% |
| Filed by the manufacturer | 100% | 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% |
| 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% |
| Gst4c Ous | 1,637 | 2 | 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 Unknown XMTR reports
How many FDA reports name Unknown XMTR?
4,431 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 2,027 in the latest 12 months.
What kinds of events are reported?
malfunction (99.5%) and injury (0.5%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
wireless communication problem (97.3%), communication or transmission problem (7.2%), battery problem (2.7%), display or visual feedback problem (2.2%) and calibration problem (1.7%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Unknown XMTR 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.