Device type · DXG
Computer, Diagnostic, Pre-Programmed, Single-Function
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
DXG
Cardiovascular
Device class
Class II
FDA decisions since 2015
12
510(k), De Novo and PMA
Adverse event reports
6
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Computer, Diagnostic, Pre-Programmed, Single-Function
- Product code
- DXG
- Device class
- Class II
- Review panel
- Cardiovascular
- Regulation
- 21 CFR 870.1435
- Specialty
- Cardiology
- FDA record
- Classification database entry for DXG
Latest FDA decisions
The 8 newest of 12 since 2015.
K253092 · Decided Feb 13, 2026 · 143 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
K251275 · Decided Sep 26, 2025 · 155 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
K232048 · Decided Dec 20, 2023 · 163 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
K212529 · Decided Nov 23, 2021 · 104 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
K192169 · Decided Apr 30, 2020 · 265 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
- EV1000 Clinical Platform510(k)
K193179 · Decided Dec 17, 2019 · 29 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
K190955 · Decided Nov 27, 2019 · 230 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
- Argos510(k)
K181372 · Decided Dec 13, 2018 · 204 days after receipt
Device type: Computer, Diagnostic, Pre-Programmed, Single-Function (DXG) · Cardiology
Reports received
6
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
6
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 | 1 | 0 | 0 | 0 |
| Jan 24 | 1 | 0 | 0 | 0 |
| Feb 24 | 0 | 0 | 0 | 0 |
| Mar 24 | 4 | 0 | 0 | 0 |
| Apr 24 | 1 | 0 | 0 | 0 |
| May 24 | 2 | 0 | 0 | 0 |
| Jun 24 | 4 | 0 | 0 | 0 |
| Jul 24 | 1 | 0 | 0 | 0 |
| Aug 24 | 5 | 0 | 0 | 0 |
| Sep 24 | 1 | 0 | 0 | 0 |
| Oct 24 | 3 | 0 | 0 | 0 |
| Nov 24 | 0 | 0 | 0 | 0 |
| Dec 24 | 1 | 0 | 0 | 0 |
| Jan 25 | 3 | 0 | 0 | 0 |
| Feb 25 | 4 | 0 | 0 | 0 |
| Mar 25 | 1 | 0 | 0 | 0 |
| Apr 25 | 0 | 0 | 0 | 0 |
| May 25 | 1 | 0 | 0 | 0 |
| Jun 25 | 0 | 0 | 0 | 0 |
| Jul 25 | 0 | 0 | 0 | 0 |
| Aug 25 | 2 | 0 | 0 | 0 |
| Sep 25 | 0 | 0 | 0 | 0 |
| Oct 25 | 1 | 0 | 0 | 0 |
| Nov 25 | 0 | 0 | 0 | 0 |
| Dec 25 | 0 | 0 | 0 | 0 |
| Jan 26 | 1 | 0 | 0 | 0 |
| Feb 26 | 0 | 0 | 0 | 0 |
| Mar 26 | 1 | 0 | 0 | 0 |
| Apr 26 | 1 | 0 | 0 | 0 |
| May 26 | 0 | 0 | 0 | 0 |
| Jun 26 | 0 | 0 | 0 | 0 |
| Jul 26 | 1 | 0 | 0 | 0 |
| Aug 26 | 0 | 0 | 0 | 0 |
| Sep 26 | 0 | 0 | 0 | 0 |
| Oct 26 | 2 | 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.
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Fluid/Blood Leak3
- Incorrect, Inadequate or Imprecise Result or Readings1
- Leak/Splash1
- Low Readings1
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions5
- Appropriate Clinical Signs, Symptoms and Conditions Term/Code Not Available1
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-0756-2021 · Started Nov 19, 2020
Reason given: The expiration date on labeling is incorrect.
Cause as FDA categorized it: Labeling mix-ups
Z-0859-2021 · Started Nov 9, 2020
Reason given: Due to a potential software issue, the display may show the incorrect continuous cardiac output (CCO) values after PulseCO calibration.
Cause as FDA categorized it: Software design
Z-1927-2020 · Started Feb 14, 2020
Reason given: Firm identified software issues which leads to the patient ID and patient information not being stored in the system.
Cause as FDA categorized it: Software Design Change
Z-2077-2019 · Started Jun 5, 2019
Reason given: The monitor displays an error message . The error message states "internal error restart or service".
Cause as FDA categorized it: Software design
Z-1147-2013 · Started Mar 28, 2013 · Posted by FDA Apr 18, 2013
Reason given: Transonic Systems Inc. have received complaints of blood leakage involving the AV Loop Kit.
Cause as FDA categorized it: Component design/selection
Z-0160-2011 · Started Jun 25, 2010 · Posted by FDA Oct 28, 2010
Reason given: The recall was initiated because the Edwards' MHANM8 Pressure Slave Cable was wired incorrectly, thus will not work as stated.
Cause as FDA categorized it: Process design
Z-0942-2012 · Started Sep 12, 2008 · Posted by FDA Feb 2, 2012
Reason given: Edwards Lifesciences has made the decision to initiate a field corrective action for the Edwards Vigilance II Model: Software: versions 00.51, 00.60, 00.61, 00.62, 00.63, 00.64, 00.67, 00.69, 00.71, 00.73 due to the potential of inaccurate Injectate Cardiac Output (ICO) measurements.
Cause as FDA categorized it: Device Design
Z-0262-2008 · Started May 17, 2007 · Posted by FDA Nov 24, 2007
Reason given: MAP offset errors: If users are "slaving" mean arterial pressure (MAP) from the bedside monitor into the Vigilance II Monitor for the purpose of the continuous calculation of systemic vascular resistance (SVR), at times, on some bedside monitors, the Vigilance II monitor may display a MAP offset of as much as 25mmHg....
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.