510(k) · Cleared
Recalled · Class II · 2018Modification to Dash 3000/4000 Patient Monitor
Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly
Ge Medical Systems Information Technologies · MHX Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms)
Cleared on Feb 26, 2003 as substantially equivalent to K020290 (General Electric Medical Systems Information Techn, 2002) after a 16-day review. Its family tree reaches back 2 generations to 2000. 257 later devices descend from it. It has been recalled once.
- Decided
- Feb 26, 2003
- Review
- 16 days
- Class
- Class II
- Product code
- MHX
- Recalls
- 1
- Predicates
- 1
Its longest line of descent runs back 2 generations to K001359 (2000). 257 later devices descend from it, 4 citing it directly.
- Root · 2 generations backK001359 Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn · 2000 · Recalled
- 1 generation backK020290 Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn · 2002 · Recalled
- This deviceK030431 Modification to Dash 3000/4000 Patient MonitorGe Medical Systems Information Technologies · 2003
- Descendant · cites it directly · 238 of its ownK042417 Zoll M Series ETC02 Loflo OptionZoll Medical Corp · 2004
- Descendant · 2 generations on · 237 of its ownK053174 Loflo C5 CO2 SensorRespironics Novametrix, LLC · 2006 · Recalled
- Descendant · 3 generations on · 222 of its ownK060221 The Phillips, Model MP20,MP30,MP40,MP50,MP60,MP70,MP80,and MP90…Philips Medizin Systeme Boeblingen GmbH · 2006
- Descendant · 4 generations on · 221 of its ownK060541 The Philips MP20,MP30,MP40,MP50,MP60,MP70,MP80 and MP90 Intellivue…Philips Medizin Systeme Boblingen GmbH · 2006 · Recalled
- Descendant · 4 generations on · 211 of its ownK061052 The Philips Intellivue Patient Monitors, Models…Philips Medical Systems North America, Inc. · 2006
Showing 5 of 257 descendants. See all descendants
Descendants cleared per year
Most influential descendants
Showing 5 of 257 · See all- K042417Zoll M Series ETC02 Loflo OptionZoll Medical Corp · 2004 · cites it directly238descendants
- K053174Loflo C5 CO2 SensorRespironics Novametrix, LLC · 2006 · 2 generations on237descendants
- K060221The Phillips, Model MP20,MP30,MP40,MP50,MP60,MP70,MP80,and MP90 Intellivue Patient…Philips Medizin Systeme Boeblingen GmbH · 2006 · 3 generations on222descendants
- K060541The Philips MP20,MP30,MP40,MP50,MP60,MP70,MP80 and MP90 Intellivue Atient MonitorsPhilips Medizin Systeme Boblingen GmbH · 2006 · 4 generations on221descendants
- K061052The Philips Intellivue Patient Monitors, Models MP20,MP30,MP40,MP50,MP60,MP70,MP80,MP90Philips Medical Systems North America, Inc. · 2006 · 4 generations on211descendants
View FIG. 1 as a table
Line of descent and top descendants
| Generation | Number | Device | Applicant | Decided | Recalls |
|---|---|---|---|---|---|
| −2 | K001359 | Dash 3000/4000 Patient Monitor | General Electric Medical Systems Information Techn | 2000 | 1 |
| −1 | K020290 | Dash 3000/4000 Patient Monitor | General Electric Medical Systems Information Techn | 2002 | 1 |
| 0 (this device) | K030431 | Modification to Dash 3000/4000 Patient Monitor | Ge Medical Systems Information Technologies | 2003 | — |
| +1 | K042417 | Zoll M Series ETC02 Loflo Option | Zoll Medical Corp | 2004 | — |
| +2 | K053174 | Loflo C5 CO2 Sensor | Respironics Novametrix, LLC | 2006 | 2 |
| +3 | K060221 | The Phillips, Model MP20,MP30,MP40,MP50,MP60,MP70,MP80,and MP90 Intellivue… | Philips Medizin Systeme Boeblingen GmbH | 2006 | — |
| +4 | K060541 | The Philips MP20,MP30,MP40,MP50,MP60,MP70,MP80 and MP90 Intellivue Atient… | Philips Medizin Systeme Boblingen GmbH | 2006 | 2 |
| +4 | K061052 | The Philips Intellivue Patient Monitors, Models… | Philips Medical Systems North America, Inc. | 2006 | — |
Descendants by year cleared
| Year cleared | Devices | With a Class I recall |
|---|---|---|
| 2003 | 2 | 0 |
| 2004 | 2 | 0 |
| 2005 | 1 | 0 |
| 2006 | 10 | 0 |
| 2007 | 4 | 0 |
| 2008 | 7 | 0 |
| 2009 | 7 | 0 |
| 2010 | 8 | 0 |
| 2011 | 9 | 0 |
| 2012 | 10 | 0 |
| 2013 | 14 | 0 |
| 2014 | 10 | 0 |
| 2015 | 9 | 0 |
| 2016 | 13 | 0 |
| 2017 | 12 | 0 |
| 2018 | 14 | 0 |
| 2019 | 10 | 0 |
| 2020 | 10 | 0 |
| 2021 | 13 | 0 |
| 2022 | 18 | 0 |
| 2023 | 22 | 0 |
| 2024 | 18 | 0 |
| 2025 | 21 | 0 |
| 2026 | 13 | 0 |
Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.
Planning a device in MHX? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.
Top candidate predicates for a new MHX device
- #1 K251702 IntelliVue Patient Monitor MX750; IntelliVue…score 23.0 · 40 generations · no Class I recall
- #2 Held for the reportin the report
- #3 Held for the reportin the report
What was it cleared against? (1)
Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.
| Type | Number | Device | Decided |
|---|---|---|---|
| * | K020290 | Dash 3000/4000 Patient Monitor | 2002 |
What descends from it? (257)
See all 2574 later devices cite it directly; ranked here by how many devices descend from each in turn.
Has anything in its family been recalled? (0 Class I)
Recalls of this device
| Date | Class | Recall | Root cause | Reason |
|---|---|---|---|---|
| Aug 31, 2018 | Class II | Z-0520-2019 | Software design | The patient monitors may simultaneously restart as designed if all are connected to the same network and a network overload occurs for a prolonged time. |
No ancestor or descendant has a Class I recall.
What does this lineage say?
- The line of descent spans 3 years and passes through 2 companies; a new generation was cleared every 2.1 years on median.
- 2 of the 2 ancestors have a recall of any class.
- Of its descendants, K042417 (Zoll Medical Corp, 2004) has gone furthest, with 238 descendants of its own.
- 1 other device also cites its predicate K020290.
How does its category compare?
All MHX devicesMHX Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms): FDA decisions, review times, recalls and adverse event reports over 20 years.
FDA decisions per year · MHX
8in 2025
2026 to Oct 25, outlined.
Median 510(k) review, days · MHX
192in 2025
Receipt to decision; years with fewer than 3 clearances left blank.
Recalls per year · MHX
21so far in 2026, the most since 2007
Class I (0 since 2007) Class II/III not classified
Adverse event reports per year · MHX
3,761in 2025
MAUDE reports naming product code MHX, not matched to any one device; reports are not rates.
View these four charts as a table
| Year | Decisions | Median 510(k) review, days | Recalls (Class I) | MAUDE reports |
|---|---|---|---|---|
| 2007 | 15 | 96 | 3 | 131 |
| 2008 | 16 | 58 | 2 | 232 |
| 2009 | 13 | 57 | 7 | 382 |
| 2010 | 20 | 90 | 13 | 955 |
| 2011 | 12 | 81 | 16 | 949 |
| 2012 | 16 | 88 | 11 | 676 |
| 2013 | 21 | 120 | 14 | 1,997 |
| 2014 | 13 | 248 | 6 | 1,609 |
| 2015 | 14 | 203 | 5 | 1,284 |
| 2016 | 13 | 149 | 7 | 1,105 |
| 2017 | 14 | 134 | 6 | 1,115 |
| 2018 | 11 | 203 | 12 | 2,157 |
| 2019 | 7 | 243 | 6 | 1,462 |
| 2020 | 11 | 196 | 0 | 1,714 |
| 2021 | 5 | 195 | 0 | 2,423 |
| 2022 | 15 | 189 | 6 | 1,470 |
| 2023 | 8 | 229 | 3 | 2,254 |
| 2024 | 5 | 181 | 3 | 2,814 |
| 2025 | 8 | 192 | 15 | 3,761 |
| 2026 | 14 | 205 | 21 | — |
What is it indicated for?
The Dash 3000/4000Patient Monitor is intended for use under the direct supervision of a licensed healthcare practitioner. The intended use of the system is to monitor physiologic parameter data on adult, pediatric and neonatal patients. The Dash is designed as a bedside, portable, arid transport monitor that can operate in all professional mjedical facilities and medical transport modes including but not limited to: emergency department, operating mom…
Read the full statement (217 words)
The Dash 3000/4000Patient Monitor is intended for use under the direct supervision of a licensed healthcare practitioner. The intended use of the system is to monitor physiologic parameter data on adult, pediatric and neonatal patients. The Dash is designed as a bedside, portable, arid transport monitor that can operate in all professional mjedical facilities and medical transport modes including but not limited to: emergency department, operating mom, post anesthesia recovery, critical care, surgical intensive care, respiratory intensive care, coronary care, medical intensive care, pediatric intensive care, or neonatal intensive care areas located in hospitals, outpatient clinics, freestanding sucgical centers, and other alternate care facilities, intra-hospital patient transport, inter-hospital patient transport via ground vehides (Le,, ambulance, etc.) and fixed and rotary winged aircraft, and pre-hospitalemergency response.
Physiologic data includes but is not restricted to: electrocardiogram, invasive blood pressure, noninvasive blood pressure, pulse, temperature, cardiac output, respiration, pulse oximetry, carbon dioxide, oxygen, and anesthetic agents as summarized in the operator's manual.
The Dash 3000/4000Patient Monitor is also intended to provide physiologic data over the Unity network to clinical information systems and allow the user to access hospital dlata at the point-of-care.
This information can be displayed, trended, stored, and printed.
The Dash 3000/4000 Patient Monitor was developed to interface with non-proprietary third party peripheraldevices that support serial data outputs.
Indications for use as stated in the FDA summary.
https://510kreport.com/device/K030431 · printed Nov 6, 2026
Cite this page
510(k) Report. “K030431: Modification to Dash 3000/4000 Patient Monitor.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K030431
Report an extraction error
Are you the manufacturer?
Record history
- FDA decision record loaded May 2, 2026
- Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
- Lineage and recalls computed Nov 3, 2026
- Page last updated Nov 3, 2026