Device type · OUG
Medical Device Data System
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
OUG
General Hospital
Device class
Class I
FDA decisions since 2015
0
510(k), De Novo and PMA
Adverse event reports
132
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Medical Device Data System
- Product code
- OUG
- Device class
- Class I
- Review panel
- General Hospital
- Regulation
- 21 CFR 880.6310
- Specialty
- Hospital Medicine & Nursing
- FDA record
- Classification database entry for OUG
Latest FDA decisions
No 510(k), De Novo or PMA decisions for this product code since 2015.
Reports received
132
Received Nov 1, 2025 to Nov 19, 2026. Includes 1 of another or unstated type.
Malfunction reports
126
95% of reports
Injury reports
5
3.8% 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 | 113 | 0 | 1 | 1 |
| Jan 24 | 127 | 2 | 0 | 0 |
| Feb 24 | 74 | 0 | 0 | 0 |
| Mar 24 | 76 | 0 | 0 | 0 |
| Apr 24 | 53 | 2 | 0 | 0 |
| May 24 | 65 | 0 | 0 | 1 |
| Jun 24 | 42 | 1 | 0 | 0 |
| Jul 24 | 22 | 1 | 0 | 0 |
| Aug 24 | 16 | 0 | 0 | 0 |
| Sep 24 | 18 | 0 | 0 | 0 |
| Oct 24 | 13 | 1 | 0 | 0 |
| Nov 24 | 17 | 0 | 0 | 0 |
| Dec 24 | 22 | 1 | 0 | 0 |
| Jan 25 | 36 | 0 | 0 | 0 |
| Feb 25 | 16 | 0 | 0 | 0 |
| Mar 25 | 16 | 1 | 0 | 0 |
| Apr 25 | 18 | 0 | 0 | 0 |
| May 25 | 30 | 0 | 0 | 0 |
| Jun 25 | 35 | 0 | 0 | 0 |
| Jul 25 | 36 | 0 | 0 | 0 |
| Aug 25 | 33 | 0 | 0 | 0 |
| Sep 25 | 51 | 0 | 0 | 0 |
| Oct 25 | 46 | 0 | 0 | 0 |
| Nov 25 | 41 | 1 | 0 | 0 |
| Dec 25 | 41 | 1 | 0 | 0 |
| Jan 26 | 8 | 0 | 0 | 0 |
| Feb 26 | 6 | 0 | 0 | 0 |
| Mar 26 | 5 | 0 | 0 | 0 |
| Apr 26 | 0 | 0 | 0 | 0 |
| May 26 | 7 | 0 | 0 | 0 |
| Jun 26 | 1 | 0 | 0 | 0 |
| Jul 26 | 6 | 1 | 0 | 0 |
| Aug 26 | 2 | 0 | 0 | 0 |
| Sep 26 | 5 | 2 | 0 | 1 |
| Oct 26 | 4 | 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.
- Medtronic102
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Wireless Communication Problem90
- Computer Software Problem16
- No Display/Image14
- Communication or Transmission Problem9
- Data Problem3
- Date/Time-Related Software Problem3
- Contamination2
- Degraded2
- Device Alarm System2
- Patient Data Problem2
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions118
- Hypoglycemia4
- Hyperglycemia3
- Insufficient Information2
- Cancer1
- Dyspnea1
- Electric Shock1
- Hemorrhage/Blood Loss/Bleeding1
- Paresis1
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.
Z-1394-2023 · Started Mar 8, 2023 · Posted by FDA Apr 17, 2023
Reason given: Due to potential software issue that may result in patient mix-up information.
Cause as FDA categorized it: Software design
Z-1201-2023 · Started Feb 6, 2023 · Posted by FDA Mar 2, 2023
Reason given: For users with MYLA V4.8.X / V4.9 that use VITEK MS to identify organisms as part of their workflow, AST filter rules that have been activated are not always being applied to AST results when sending the results to the clinician.
Cause as FDA categorized it: Software design
Z-0084-2022 · Started Sep 2, 2021
Reason given: Under certain conditions, there is a risk for a false negative result.
Cause as FDA categorized it: Software design
Z-0292-2021 · Started Sep 22, 2020 · Posted by FDA Oct 23, 2020
Reason given: There is an intermittent software issue that could affect the systems, in which an exam video for one patient (Patient A) might be copied to another patient (Patient B). This does not occur at the time the user performs and initially reviews an exam; it is not evident until a follow-up review occurs.
Cause as FDA categorized it: Software design
Z-0293-2021 · Started Sep 22, 2020 · Posted by FDA Oct 23, 2020
Reason given: There is an intermittent software issue that could affect the systems, in which an exam video for one patient (Patient A) might be copied to another patient (Patient B). This does not occur at the time the user performs and initially reviews an exam; it is not evident until a follow-up review occurs.
Cause as FDA categorized it: Software design
Z-1673-2020 · Started Jan 17, 2020
Reason given: A security-only update was released via remote diagnostics on January 14, 2020 to customers with Windows 7 operation system. Shortly after the releases some customers reported that Data Management System computers would not restart. If the computer is unable to restart, then the system cannot download data generated...
Cause as FDA categorized it: Software Manufacturing/Software Deployment
Z-0542-2020 · Started Sep 25, 2019
Reason given: The firm have received reports of patients myCordella Hubs fully powering themselves down without interaction from the patient or Endotronix.
Cause as FDA categorized it: Other
Z-0864-2020 · Started Aug 8, 2019
Reason given: The firm has become aware that there is a potential problem relating to the blood gas and immunoassay analyzer Systems that may result in patient mix-up when connected to some third-party devices. The error may lead to serious adverse health consequences for the patient caused by patient data mix-up.
Cause as FDA categorized it: Software design
Showing the 8 newest of 24 recall records in FDA's data.
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.