Skip to content

Dexcom G4 PLATINUM (Pediatric) Receiver with Share Kit USRecalls & reported problems across all models

Dexcom, Inc. · 3 models in the FDA device registry

Data updated Oct 18, 2026 from official FDA records · Editorial policy

Adverse event reports
630
Deaths reported
0
Injuries reported
1
Recalls
0

We found 3 models of Dexcom G4 PLATINUM (Pediatric) Receiver with Share Kit US by Dexcom, Inc. in the FDA's device registry (GUDID). Together they are named in 630 adverse event reports in the FDA's MAUDE database, received between Aug 17, 2016 and Mar 4, 2020 — classified as 1 injury, 629 malfunctions.

The most frequently reported specific device problem is “Device Displays Incorrect Message” (270 reports).

Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event. Widely used products collect more reports, so totals can't be used to compare products or estimate failure rates. Only reports that name a model's exact device identifier are counted. What reports can and can't tell you · How this data works

Most reported Dexcom G4 PLATINUM (Pediatric) Receiver with Share Kit US problems

Device problems

  • Device Displays Incorrect Message270
  • No Audible Alarm91
  • Wireless Communication Problem78
  • Defective Alarm67
  • Device Inoperable41
  • Inappropriate or Unexpected Reset34
  • Unable to Obtain Readings31
  • Use of Device Problem13

Patient problems

  • No Consequences Or Impact To Patient629
  • Hypoglycemia1

Dexcom G4 PLATINUM (Pediatric) Receiver with Share Kit US models

3 models, most reported first. Each model has its own page with its reports, recalls and device details.

Recent Dexcom G4 PLATINUM (Pediatric) Receiver with Share Kit US adverse event reports

The 15 most recent reports across all models, in the reporter's own words as published by the FDA.

Other Dexcom, Inc. products

All Dexcom, Inc. devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page