Device type · PHV
Continuous Glucose Monitor Retrospective Data Analysis Software
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
PHV
Clinical Chemistry
Device class
Class I
FDA decisions since 2015
0
510(k), De Novo and PMA
Adverse event reports
197
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Continuous Glucose Monitor Retrospective Data Analysis Software
- Product code
- PHV
- Device class
- Class I
- Review panel
- Clinical Chemistry
- Regulation
- 21 CFR 862.2120
- FDA record
- Classification database entry for PHV
Latest FDA decisions
No 510(k), De Novo or PMA decisions for this product code since 2015.
Reports received
197
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
197
100% of reports
Injury reports
0
0.0% of reports
Death reports
0
0.0% of reports
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 36 | 0 | 0 | 0 |
| Jan 24 | 46 | 0 | 0 | 0 |
| Feb 24 | 64 | 0 | 0 | 0 |
| Mar 24 | 26 | 0 | 0 | 0 |
| Apr 24 | 17 | 0 | 0 | 0 |
| May 24 | 17 | 0 | 0 | 0 |
| Jun 24 | 17 | 0 | 0 | 0 |
| Jul 24 | 15 | 0 | 0 | 0 |
| Aug 24 | 12 | 0 | 0 | 0 |
| Sep 24 | 9 | 1 | 0 | 0 |
| Oct 24 | 19 | 1 | 0 | 0 |
| Nov 24 | 19 | 0 | 0 | 0 |
| Dec 24 | 21 | 0 | 0 | 0 |
| Jan 25 | 19 | 0 | 0 | 0 |
| Feb 25 | 5 | 0 | 0 | 0 |
| Mar 25 | 3 | 0 | 0 | 0 |
| Apr 25 | 14 | 0 | 0 | 0 |
| May 25 | 13 | 0 | 0 | 0 |
| Jun 25 | 9 | 1 | 0 | 0 |
| Jul 25 | 15 | 0 | 0 | 0 |
| Aug 25 | 22 | 0 | 0 | 0 |
| Sep 25 | 28 | 0 | 0 | 0 |
| Oct 25 | 19 | 0 | 0 | 0 |
| Nov 25 | 9 | 0 | 0 | 0 |
| Dec 25 | 13 | 0 | 0 | 0 |
| Jan 26 | 3 | 0 | 0 | 0 |
| Feb 26 | 11 | 0 | 0 | 0 |
| Mar 26 | 23 | 0 | 0 | 0 |
| Apr 26 | 15 | 0 | 0 | 0 |
| May 26 | 10 | 0 | 0 | 0 |
| Jun 26 | 20 | 0 | 0 | 0 |
| Jul 26 | 23 | 0 | 0 | 0 |
| Aug 26 | 15 | 0 | 0 | 0 |
| Sep 26 | 21 | 0 | 0 | 0 |
| Oct 26 | 34 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
- Medtronic196
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Data Problem185
- Computer Software Problem25
- Unauthorized Access to Computer System5
- Device Alarm System1
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions194
- Hypoglycemia2
- Hyperglycemia1
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
- CareLink Clinic, REF: MMT-7350Open, Classified
Z-0203-2027 · Started Sep 11, 2026 · Posted by FDA Oct 21, 2026
Reason given: CareLink Clinic software version 4.4A includes a software defect in the Settings Calculator feature in which the calculation logic fails to use custom values entered by healthcare professionals (HCPs) for Total Daily Dose (TDD) or Long-acting insulin when calculating the Carb Ratio, Insulin Sensitivity Factor (ISF),...
Cause as FDA categorized it: Software design
- CareLink Clinic, REF: MMT-7350Open, Classified
Z-0594-2026 · Started Oct 21, 2025 · Posted by FDA Nov 25, 2025
Reason given: Software error causing incorrect data to be displayed on the 24-hour Sensor Glucose Overview Graph, any potential therapy decisions were made based on the incorrect data displayed on the 24-hour sensor glucose overview graph may lead to hypoglycemia or hyperglycemia.
Cause as FDA categorized it: Software change control
Z-2898-2016 · Started Aug 5, 2016
Reason given: Medtronic MiniMed is recalling the CareLink iPro Therapy Management Software due to a time stamp error.
Cause as FDA categorized it: Software design
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.