Skip to content
Recall Observatory FDA recall evidence

Device product

Dexcom G6, Continuous Glucose Monitoring System, REF: STK-OE-001

Z-1204-2025

January 27, 2025

Class II

Product summary

Firm
Dexcom, Inc.
Event
Event 96091
Status
Ongoing
Classification
Class II
Quantity
N/A
Official record key
device-enforcement:Z-1204-2025

Official wording

Reason: Under very rare situations, the Dexcom G6 touchscreen receiver may not provide high or low glucose alarms/alerts as designed, which can result in two different conditions. First, if a receiver operating system .net error occurs when an alarm/alert should be triggered, the initial alarm/alert will not be delivered until a subsequent alarm/alert is triggered. At that time, the initial alarm/alert is delivered, but not the second one. Alarm/alerts will continue to be delayed and be one alarm/alert behind, causing delayed alarm/alerts until the receiver is reset. This condition could result in the missed detection of a hyperglycemic or hypoglycemic event. Second, a single EGV reading may be delayed for 5 minutes after the initial .net operating system error. If the user receives a single EGV reading delayed by 5 minutes, the delay is not expected to cause user harm.

Code information: All Serial Numbers/UDI: 00386270001900

Distribution pattern: Worldwide - US Nationwide distribution in the states of OH, TX, PA, MN, SC, NH, FL, CA, NJ, PR, GA and the countries of Austria, Belgium, Canada, Switzerland, Germany, Spain, France, Ireland, Japan, Netherlands, Slovenia, United Kingdom, Australia, Czech Republic, Denmark, Finland, France, Hong Kong, Israel, Italy, Korea, Kuwait, New Zealand, Norway, Oman, Poland, Qatar, Saudi Arabia, Singapore, Slovakia, South Africa, Sweden, Turkey, United Arab Emirates.

Derived failure modes

  • Unknown

    reason.no_named_rule · v1.0.0

    Under very rare situations, the Dexcom G6 touchscreen receiver may not provide high or low glucose alarms/alerts as designed, which can result in two different conditions. First, if a receiver operating system .net error occurs when an alarm/alert should be triggered, the initial alarm/alert will not be delivered until a subsequent alarm/alert is triggered. At that time, the initial alarm/alert is delivered, but not the second one. Alarm/alerts will continue to be delayed and be one alarm/alert behind, causing delayed alarm/alerts until the receiver is reset. This condition could result in the missed detection of a hyperglycemic or hypoglycemic event. Second, a single EGV reading may be delayed for 5 minutes after the initial .net operating system error. If the user receives a single EGV reading delayed by 5 minutes, the delay is not expected to cause user harm.