Integrated continuous glucose monitoring system for non-intensive diabetes management medical device reports that FDA received
- FDA product code
- QDK
- Device class
- Class 2
- Panel
- Clinical Chemistry
What a report is
A report is not proof that the device was the cause of the event.
FDA says:
Adverse event reports submitted to FDA do not undergo extensive validation or verification. Therefore, a causal relationship cannot be established between product and reactions listed in a report. While a suspected relationship may exist, it is not medically validated and should not be the sole source of information for clinical decision making or other assumptions about the safety or efficacy of a product. Additionally, it is important to remember that adverse event reports represent a small percentage of total usage numbers of a product. Common products may have a higher number of adverse events due to the higher total number of people using the product.
Source: openFDA, Device Adverse Event Overview, section "Responsible use of the data". The site read the page on . The data have the reports that FDA received through .
FDA also says:
Although MDRs are a valuable source of information, this passive surveillance system has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data. In addition, the incidence or prevalence of an event cannot be determined from this reporting system alone due to potential under-reporting of events and lack of information about frequency of device use.
Source: openFDA, Device Adverse Event Overview. The site read the page on .
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.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
Do not rely on openFDA to make decisions regarding medical care. While we make every effort to ensure that data is accurate, you should assume all results are unvalidated.
Source: openFDA, Response of the drug event API (meta.disclaimer). The site read the page on .
Not medical advice. This site counts what was reported to FDA. Questions about a medicine or device belong with a pharmacist or clinician.
Reports on file
Product code QDK is the FDA classification for Integrated continuous glucose monitoring system for non-intensive diabetes management. The panel is Clinical Chemistry. The device class is 2.
From November 2018 to June 2025, FDA received 620 medical device reports that have this product code.
FDA received 0 reports in the 12 months to September 2026 and 282 in the 12 months before. FDA releases MAUDE data every month. Reports can arrive months after an event, so the newest months grow in later releases.
Manufacturer reports were 97.1% of the reports that have this product code and 94.9% of all device reports.
The number of people who use the product is not in the data. A count is not a rate.
Product code
FDA gives each type of device a product code of three letters. A report has the code of its device, so a code has the reports of each brand of one device type.
Device class
Class I, II or III is the regulatory class of FDA for the device type. It is not a rating of a product.
Data version
openFDA MAUDE release of 23 Oct 2026. Reports received through 30 Sep 2026.
Brand names of this type
No brand name with this product code has a page.
Manufacturers named
The table has the 1 manufacturers with 5 or more reports that have this product code. The rows are in order of name. A manufacturer with fewer reports is not in the table.
FDA says:
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.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
| Manufacturer, as written on reports | Reports |
|---|---|
| Dexcom | 627 |
Manufacturers, importers and device user facilities are mandatory reporters. The guide on what affects a count gives FDA's words.
Reports by month
FDA releases MAUDE data every month. Reports can arrive months after an event, so the newest months grow in later releases.
Event type and report source
| Event type | Reports | Share | Share as a bar |
|---|---|---|---|
| Death | 1 | 0.2% | |
| Injury | 18 | 2.9% | |
| Malfunction | 601 | 96.9% | |
| Other | 0 | 0% | |
| Not given | 0 | 0% |
| Report source | Reports | Share | Share as a bar |
|---|---|---|---|
| Manufacturer report | 602 | 97.1% | |
| Voluntary report | 18 | 2.9% | |
| User facility report | 0 | 0% | |
| Distributor report | 0 | 0% | |
| Not given | 0 | 0% |
The event type is the classification that the reporter gave. FDA does not verify it.
Device problems coded
| Device problem (FDA code) | Reports | Share |
|---|---|---|
| Wireless communication problema wireless connection problem | 385 | 62.1% |
| Imprecision | 83 | 13.4% |
| No device output | 40 | 6.5% |
| Unable to obtain readings | 27 | 4.4% |
| Unexpected shutdown | 12 | 1.9% |
| Unintended application program shut down | 8 | 1.3% |
| No audible alarm | 6 | 1% |
| Operating system version or upgrade problem | 6 | 1% |
| Defective alarm | 5 | 0.8% |
| Detachment of device or device componentpart of the device came off | 4 | 0.6% |
| Display or visual feedback problem | 4 | 0.6% |
| Inappropriate or unexpected reset | 3 | 0.5% |
| Incorrect, inadequate or imprecise result or readings | 3 | 0.5% |
| Premature end-of-life indicator | 3 | 0.5% |
| Output problem | 2 | 0.3% |
| Physical resistance/sticking | 2 | 0.3% |
| Application program freezes or fails to launch | 1 | 0.2% |
| Breakthe device broke | 1 | 0.2% |
| Computer software problema software problem | 1 | 0.2% |
| Connection problema connection problem | 1 | 0.2% |
Official pages
- Medical Device Reporting (MDR): How to Report Medical Device ProblemsThe FDA page that tells how to report a problem with a medical device.
- MedWatch Online Voluntary Reporting FormThe online form of FDA for a voluntary report.
- Manufacturer and User Facility Device Experience (MAUDE) DatabaseThe search page of FDA for the device reports.
The site checked these addresses on . The links open in a new tab.
Cite this page
Reported Reactions. Integrated continuous glucose monitoring system for non-intensive diabetes management (product code QDK): medical device reports that FDA received. https://reportedreactions.com/device-type/qdk/ Source: U.S. Food and Drug Administration, openFDA Device Adverse Event (MAUDE) files, release of . Reports received through .
Where the data come from
The counts come from the openFDA Device Adverse Event (MAUDE) bulk files, release of 23 Oct 2026. The files have the reports that FDA received through 30 Sep 2026. Brand names, generic names and manufacturer names are as written on the reports. The names of the product codes come from the device classification of FDA.
The site does not publish a report narrative, a lot number, a detail of a patient or the identity of a reporter. The record of FDA is the authority. See how the site counts reports, the data sources and the corrections page.
Questions
What is product code QDK?
It is the FDA classification code for Integrated continuous glucose monitoring system for non-intensive diabetes management, class 2, in the Clinical Chemistry panel. Each device report has the product code of the device.
What event types do the reports record?
Death (1), injury (18) and malfunction (601). The event type is the classification that the reporter gave. FDA does not verify it.
Can the table of brand names rank the devices?
No. FDA says:
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.
Source: openFDA, Manufacturer and User Facility Device Experience. The site read the page on .
Brands also differ in the number of devices in use and in their time on the market.