Reported Reactions

Devices › Integrated continuous glucose monitor for non-intensive glucose monitoring, over-the-counter

Device brand name · Continuous glucose monitor

Stelo Glucose Biosensor System: medical device reports filed with FDA

2,508 reports name it, 2024–2026. Manufacturer given most often on reports: Dexcom. Product code SAF.

2,508
device reports naming the brand
0% of all MAUDE reports · about 1,373 a year
1,271
reports, 12 months to August 2026
1,237 in the 12 months before
94.7%
classified as malfunction
91.6% across the product code
0%
classified as death, as reported
0 reports · not verified by FDA

2,508 medical device reports received by FDA name the brand "Stelo Glucose Biosensor System" (continuous glucose monitor); the manufacturer given most often on reports is Dexcom; received from September 2024 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.

1,271 reports arrived in the 12 months to August 2026, close to the 1,237 of 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 (94.7%) and injury (5.3%); across all integrated continuous glucose monitor for non-intensive glucose monitoring, over-the-counter reports (product code SAF) death is recorded in 0% and malfunction in 91.6%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are detachment of device or device component (62.9%), break (18.8%) and incorrect, inadequate or imprecise result or readings (0.6%). The patient problems coded most often are foreign body in patient, pain and erythema. 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

083166Sep 2021: 0Oct 2021: 0Nov 2021: 0Dec 2021: 02022Jan 2022: 0Feb 2022: 0Mar 2022: 0Apr 2022: 0May 2022: 0Jun 2022: 0Jul 2022: 0Aug 2022: 0Sep 2022: 0Oct 2022: 0Nov 2022: 0Dec 2022: 02023Jan 2023: 0Feb 2023: 0Mar 2023: 0Apr 2023: 0May 2023: 0Jun 2023: 0Jul 2023: 0Aug 2023: 0Sep 2023: 0Oct 2023: 0Nov 2023: 0Dec 2023: 02024Jan 2024: 0Feb 2024: 0Mar 2024: 0Apr 2024: 0May 2024: 0Jun 2024: 0Jul 2024: 0Aug 2024: 0Sep 2024: 13Oct 2024: 77Nov 2024: 69Dec 2024: 732025Jan 2025: 112Feb 2025: 133Mar 2025: 132Apr 2025: 141May 2025: 166Jun 2025: 121Jul 2025: 99Aug 2025: 101Sep 2025: 111Oct 2025: 123Nov 2025: 85Dec 2025: 972026Jan 2026: 88Feb 2026: 100Mar 2026: 124Apr 2026: 118May 2026: 99Jun 2026: 106Jul 2026: 111Aug 2026: 109

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

07111,4212024: 23220242025: 1,42120252026: 8552026

Event type and report source

Event type, as classified on the report

Death0%0
Injury5.3%134
Malfunction94.7%2,374
Other0%0
Not given0%0

Who filed the report

Manufacturer report99.8%2,503
Voluntary report0.2%5
User facility report0%0
Distributor report0%0
Not given0%0

Grey bar: all 2,699 reports carrying product code SAF. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Detachment of device or device componentpart of the device came off1,57862.9%58.7%
Breakthe device broke47118.8%17.5%
Incorrect, inadequate or imprecise result or readings150.6%2.1%
Unintended electrical shock120.5%0.7%
Wireless communication problema wireless connection problem100.4%0.9%
Overheating of device50.2%0.2%
High readingsreadings were too high20.1%0.7%
Low readingsreadings were too low20.1%0.6%
No audible alarm20.1%0.1%
Application program freezes or fails to launch10%0%
Device sensing problem10%0.4%
Display or visual feedback problem10%0.1%
Insufficient device problem information10%0%
Premature end-of-life indicator10%0.1%
Unable to obtain readings10%0.2%
Unintended application program shut down10%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)ReportsShare
Foreign body in patientpart of a device left in the patient39115.6%
Painpain, site not specified1405.6%
Erythemaskin redness1174.7%
Skin inflammation/ irritation813.2%
Bacterial infectiona bacterial infection803.2%
Hemorrhage/blood loss/bleeding391.6%
Abscessa collection of pus361.4%
Rashskin rash230.9%
Foreign body reaction200.8%
Itching sensation190.8%
Appropriate clinical signs, symptoms and conditions term/code not available170.7%
Discomfortdiscomfort170.7%
Burning sensationa burning feeling140.6%
Cellulitisa skin infection100.4%
Hypersensitivity/allergic reaction100.4%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

MeasureStelo Glucose Biosensor SystemProduct code SAFAll MAUDE reports
Reports2,5082,69926,136,888
Share of that pool—92.9%0%
Classified as death, per 1,000 reports009
Classified as injury5.3%8.2%36.2%
Classified as malfunction94.7%91.6%62.3%
Filed by the manufacturer99.8%95.9%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 SAF

BrandReportsLatest 12 monthsClassified as death
Dexcom G7 Continuous Glucose Monitoring System641,507268,7810%

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 Stelo Glucose Biosensor System reports

How many FDA reports name Stelo Glucose Biosensor System?

2,508 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 1,271 in the latest 12 months.

What kinds of events are reported?

malfunction (94.7%) and injury (5.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

detachment of device or device component (62.9%), break (18.8%), incorrect, inadequate or imprecise result or readings (0.6%), unintended electrical shock (0.5%) and wireless communication problem (0.4%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (99.8%) and voluntary reports (0.2%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that Stelo Glucose Biosensor System 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.