Device brand name · Glucose monitoring sys/kit
One Touch Ultrasmart: medical device reports filed with FDA
658 reports name it, 2003–2006. Manufacturer given most often on reports: Lifescan. Product code CFR.
- 658
- device reports naming the brand
- 0% of all MAUDE reports · about 29 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 88.4%
- classified as malfunction
- 83.6% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 658 reports that name the brand "One Touch Ultrasmart" (glucose monitoring sys/kit), received between July 2003 and December 2006; the manufacturer given most often on reports is Lifescan. Spellings of one product vary from report to report.
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 (88.4%) and injury (10.8%); 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 (59%), replace (51.4%) and high test results (19%). The patient problems coded most often are treatment with medication(s), blood glucose, high 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 One Touch Ultrasmart was received in the five years to August 2026; the latest was received in December 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 | 388 | 59% | 56.7% |
| Replace | 338 | 51.4% | 22.8% |
| High test results | 125 | 19% | 18% |
| Device displays incorrect message | 39 | 5.9% | 4.9% |
| Low test results | 39 | 5.9% | 7% |
| Repair | 25 | 3.8% | 0.8% |
| Failure to power up | 23 | 3.5% | 3.4% |
| No display/image | 10 | 1.5% | 1.7% |
| Device issuea problem with the device | 9 | 1.4% | 1.3% |
| Loss of powerthe device lost power | 9 | 1.4% | 1.1% |
| Device damaged prior to usethe device was damaged before use | 8 | 1.2% | 0.3% |
| Malfunction | 7 | 1.1% | 0.4% |
| Corrodedthe device corroded | 4 | 0.6% | 0% |
| Erratic or intermittent display | 4 | 0.6% | 1.3% |
| High readingsreadings were too high | 4 | 0.6% | 5.3% |
| Unable to obtain readings | 4 | 0.6% | 2.5% |
| Incorrect, inadequate or imprecise result or readings | 3 | 0.5% | 1% |
| Device expiration issue | 2 | 0.3% | 1.5% |
| Display or visual feedback problem | 2 | 0.3% | 0.5% |
| Improper or incorrect procedure or method | 2 | 0.3% | 0.7% |
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 |
|---|---|---|
| Treatment with medication(s) | 68 | 10.3% |
| Blood glucose, high | 65 | 9.9% |
| Hospitalization required | 53 | 8.1% |
| Therapy/non-surgical treatment, additional | 38 | 5.8% |
| Blood glucose, low | 35 | 5.3% |
| Hypoglycemialow blood sugar | 32 | 4.9% |
| Loss of consciousnesspassing out | 18 | 2.7% |
| Shaking/tremors | 15 | 2.3% |
| Dizzinesslight-headedness or unsteadiness | 14 | 2.1% |
| Hyperglycemiahigh blood sugar | 14 | 2.1% |
| Sweating | 12 | 1.8% |
| Confusion/ disorientation | 9 | 1.4% |
| Headachehead pain | 8 | 1.2% |
| Other (for use when an appropriate patient code cannot be identified) | 8 | 1.2% |
| Therapy/non-surgical treatment, aborted/stopped | 8 | 1.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | One Touch Ultrasmart | Product code CFR | All MAUDE reports |
|---|---|---|---|
| Reports | 658 | 37,537 | 26,136,888 |
| Share of that pool | — | 1.8% | 0% |
| Classified as death, per 1,000 reports | 0 | 1 | 9 |
| Classified as injury | 10.8% | 14.2% | 36.2% |
| Classified as malfunction | 88.4% | 83.6% | 62.3% |
| Filed by the manufacturer | 100% | 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% |
| Quick Check One | 276 | 0 | 0% |
| Precision Xtra Monitor | 318 | 0 | 0.6% |
| One Touch Basic Original | 243 | 0 | 0% |
| Induo | 326 | 0 | 0.3% |
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 One Touch Ultrasmart reports
How many FDA reports name One Touch Ultrasmart?
658 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 (88.4%) and injury (10.8%). "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 (59%), replace (51.4%), high test results (19%), device displays incorrect message (5.9%) and low test results (5.9%). 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 One Touch Ultrasmart 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.