Device brand name · Glucose monitoring sys/kit
Induo: medical device reports filed with FDA
326 reports name it, 2002–2006. Manufacturer given most often on reports: Lifescan. Product code CFR.
- 326
- device reports naming the brand
- 0% of all MAUDE reports · about 13 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 75.5%
- classified as malfunction
- 83.6% across the product code
- 0.3%
- classified as death, as reported
- 1 reports · not verified by FDA
326 medical device reports received by FDA name the brand "Induo" (glucose monitoring sys/kit); the manufacturer given most often on reports is Lifescan; received from March 2002 to June 2006. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
0 reports arrived in the 12 months to August 2026, and none 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 (75.5%), injury (23.3%) and death (0.3%); across all hexokinase, glucose reports (product code CFR) death is recorded in 0.1% and malfunction in 83.6%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are incorrect or inadequate test results (39.3%), replace (35%) and high test results (21.2%). The patient problems coded most often are blood glucose, high, treatment with medication(s) and hospitalization required. 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
No report naming Induo was received in the five years to August 2026; the latest was received in June 2006.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 37,537 reports carrying product code CFR. 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 |
|---|---|---|---|
| Incorrect or inadequate test results | 128 | 39.3% | 56.7% |
| Replace | 114 | 35% | 22.8% |
| High test results | 69 | 21.2% | 18% |
| Failure to power up | 30 | 9.2% | 3.4% |
| Device displays incorrect message | 29 | 8.9% | 4.9% |
| Low test results | 17 | 5.2% | 7% |
| Device issuea problem with the device | 12 | 3.7% | 1.3% |
| Unable to obtain readings | 11 | 3.4% | 2.5% |
| Failure to deliverthe device did not deliver the dose or item | 9 | 2.8% | 0% |
| Crackthe device cracked | 8 | 2.5% | 0.1% |
| Other (for use when an appropriate device code cannot be identified) | 6 | 1.8% | 0.9% |
| Device damaged prior to usethe device was damaged before use | 4 | 1.2% | 0.3% |
| Sticking | 4 | 1.2% | 0.1% |
| Erratic or intermittent display | 3 | 0.9% | 1.3% |
| Incorrect measurementthe device measured wrongly | 3 | 0.9% | 0.2% |
| Component missing | 2 | 0.6% | 0.9% |
| Component(s), worn | 2 | 0.6% | 0% |
| Defective component | 2 | 0.6% | 0.2% |
| Device expiration issue | 2 | 0.6% | 1.5% |
| Difficult to insertthe device was hard to insert | 2 | 0.6% | 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 |
|---|---|---|
| Blood glucose, high | 64 | 19.6% |
| Treatment with medication(s) | 60 | 18.4% |
| Hospitalization required | 47 | 14.4% |
| Therapy/non-surgical treatment, additional | 37 | 11.3% |
| Blood glucose, low | 27 | 8.3% |
| Hypoglycemialow blood sugar | 18 | 5.5% |
| Other (for use when an appropriate patient code cannot be identified) | 15 | 4.6% |
| Loss of consciousnesspassing out | 14 | 4.3% |
| Elevated ketones/ diabetic ketoacidosis | 11 | 3.4% |
| Dizzinesslight-headedness or unsteadiness | 10 | 3.1% |
| Shaking/tremors | 10 | 3.1% |
| Sweating | 8 | 2.5% |
| Therapy/non-surgical treatment, aborted/stopped | 7 | 2.1% |
| Vomitingbeing sick | 7 | 2.1% |
| Nauseafeeling sick | 6 | 1.8% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Induo | Product code CFR | All MAUDE reports |
|---|---|---|---|
| Reports | 326 | 37,537 | 26,136,888 |
| Share of that pool | — | 0.9% | 0% |
| Classified as death, per 1,000 reports | 3 | 1 | 9 |
| Classified as injury | 23.3% | 14.2% | 36.2% |
| Classified as malfunction | 75.5% | 83.6% | 62.3% |
| Filed by the manufacturer | 99.7% | 99% | 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 CFR
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| One Touch Ultra | 16,425 | 0 | 0% |
| Fasttake | 4,173 | 0 | 0% |
| One Touch Profile | 3,032 | 0 | 0% |
| One Touch Basic Enhanced | 2,741 | 0 | 0% |
| Accu-Chek Comfort Curve | 4,120 | 0 | 0.6% |
| Surestep | 5,323 | 0 | 0.1% |
| One Touch Basic | 2,244 | 0 | 0% |
| Precision Qid Glucose Meter | 561 | 0 | 0.4% |
| Accu-Chek Advantage | 1,290 | 0 | 0.5% |
| Glucometer Dex | 442 | 0 | 0% |
| Medisense Companion 2 Meter | 390 | 0 | 0% |
| One Touch Ultrasmart | 658 | 0 | 0% |
| Quick Check One | 276 | 0 | 0% |
| Precision Xtra Monitor | 318 | 0 | 0.6% |
| One Touch Basic Original | 243 | 0 | 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 Induo reports
How many FDA reports name Induo?
326 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
malfunction (75.5%), injury (23.3%) and death (0.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
incorrect or inadequate test results (39.3%), replace (35%), high test results (21.2%), failure to power up (9.2%) and device displays incorrect message (8.9%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.7%) and voluntary reports (0.3%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Induo 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.