510(k) Report

510(k) · Cleared

Recalled · Class II · 2018

Dash 3000/4000 Patient Monitor

K020290510(k) TraditionalCleared Aug 14, 2002198-day reviewClass II21 CFR 870.1025Recalls 1

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

General Electric Medical Systems Information Techn · MHX Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms)

Cleared on Aug 14, 2002 as substantially equivalent to K001359 (General Electric Medical Systems Information Techn, 2000) after a 198-day review. Its family tree reaches back 1 generation to 2000. 1 of the 286 devices in its family, counting itself, has a Class I recall. 284 later devices descend from it. It has been recalled once.

Decided
Aug 14, 2002
Review
198 days
Class
Class II
Product code
MHX
Recalls
1
Predicates
1

Its longest line of descent runs back 1 generation to K001359 (2000). 284 later devices descend from it, 2 citing it directly. 1 of the 286 devices in this family, counting this one, has a Class I recall.

Descendants, by year cleared 2003: 4 descendants cleared2004: 2 descendants cleared2009: 7 descendants cleared2010: 9 descendants cleared2008: 7 descendants cleared2017: 14 descendants cleared2007: 4 descendants cleared2005: 1 descendant cleared2006: 10 descendants cleared2016: 13 descendants cleared2013: 18 descendants cleared2012: 11 descendants cleared2022: 23 descendants cleared2015: 11 descendants cleared2020: 13 descendants cleared2014: 11 descendants cleared, 1 with a Class I recall12019: 11 descendants cleared2011: 9 descendants cleared2018: 14 descendants cleared2021: 14 descendants cleared2023: 24 descendants cleared2025: 22 descendants cleared2024: 18 descendants cleared2026: 14 descendants clearedK001359 · Dash 3000/4000 Patient Monitor · General Electric Medical Systems Information Techn · 2000 · recalled200020052010201520202025
Descendants, by generation 1 generation forward: 2 descendants2 generations forward: 7 descendants3 generations forward: 14 descendants4 generations forward: 20 descendants, 1 with a Class I recall15 generations forward: 33 descendants6 generations forward: 37 descendants7 generations forward: 47 descendants8 generations forward: 38 descendants9 generations forward: 38 descendants10 generations forward: 23 descendants11 generations forward: 12 descendants12 generations forward: 7 descendants13 generations forward: 6 descendants K001359 · Dash 3000/4000 Patient Monitor · General Electric Medical Systems Information Techn · 2000 · recalled0+5+10
  1. Root · 1 generation backK001359 Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn · 2000 · Recalled
  2. This deviceK020290 Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn · 2002
  3. Descendant · cites it directly · 257 of its ownK030431 Modification to Dash 3000/4000 Patient MonitorGe Medical Systems Information Technologies · 2003 · Recalled
  4. Descendant · 2 generations on · 238 of its ownK042417 Zoll M Series ETC02 Loflo OptionZoll Medical Corp · 2004
  5. Descendant · 3 generations on · 237 of its ownK053174 Loflo C5 CO2 SensorRespironics Novametrix, LLC · 2006 · Recalled
  6. Descendant · 4 generations on · 222 of its ownK060221 The Phillips, Model MP20,MP30,MP40,MP50,MP60,MP70,MP80,and MP90…Philips Medizin Systeme Boeblingen GmbH · 2006
  7. Descendant · 5 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

Showing 5 of 284 descendants. See all descendants

Descendants cleared per year

2003: 42004: 22005: 12006: 102007: 42008: 72009: 72010: 92011: 92012: 112013: 182014: 112015: 112016: 132017: 142018: 142019: 112020: 132021: 142022: 232023: 242024: 182025: 222026: 14
2003high 24 (2023) · low 1 (2005)2026

Class I recalls in this family

Most influential descendants

Showing 5 of 284 · See all
  • K030431Modification to Dash 3000/4000 Patient MonitorGe Medical Systems Information Technologies · 2003 · cites it directly257descendants
  • K042417Zoll M Series ETC02 Loflo OptionZoll Medical Corp · 2004 · 2 generations on238descendants
  • K053174Loflo C5 CO2 SensorRespironics Novametrix, LLC · 2006 · 3 generations on237descendants
  • K060221The Phillips, Model MP20,MP30,MP40,MP50,MP60,MP70,MP80,and MP90 Intellivue Patient…Philips Medizin Systeme Boeblingen GmbH · 2006 · 4 generations on222descendants
  • K060541The Philips MP20,MP30,MP40,MP50,MP60,MP70,MP80 and MP90 Intellivue Atient MonitorsPhilips Medizin Systeme Boblingen GmbH · 2006 · 5 generations on221descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−1K001359Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn20001
0 (this device)K020290Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn2002—
+1K030431Modification to Dash 3000/4000 Patient MonitorGe Medical Systems Information Technologies20031
+2K042417Zoll M Series ETC02 Loflo OptionZoll Medical Corp2004—
+3K053174Loflo C5 CO2 SensorRespironics Novametrix, LLC20062
+4K060221The Phillips, Model MP20,MP30,MP40,MP50,MP60,MP70,MP80,and MP90 Intellivue…Philips Medizin Systeme Boeblingen GmbH2006—
+5K060541The Philips MP20,MP30,MP40,MP50,MP60,MP70,MP80 and MP90 Intellivue Atient…Philips Medizin Systeme Boblingen GmbH20062

Descendants by year cleared

Year clearedDevicesWith a Class I recall
200340
200420
200510
2006100
200740
200870
200970
201090
201190
2012110
2013180
2014111
2015110
2016130
2017140
2018140
2019110
2020130
2021140
2022230
2023240
2024180
2025220
2026140
FIG. 1 — Lineage of K020290, 2000–2026Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

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.

1 device in this family has a Class I recall. 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. #1 K251702 IntelliVue Patient Monitor MX750; IntelliVue…score 23.0 · 40 generations · no Class I recall
  2. #2 Held for the reportin the report
  3. #3 Held for the reportin the report
Get a 510(k) 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.

TypeNumberDeviceApplicantDecidedRecalls
*K001359Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn20001

Also cleared against K001359: 1 other device →

What descends from it? (284)

See all 284

2 later devices cite it directly; ranked here by how many devices descend from each in turn.

NumberDeviceApplicantDecidedDescendants
K030431Modification to Dash 3000/4000 Patient MonitorGe Medical Systems Information Technologies2003257
K031320EK-Pro Arrhythmia Detection AlgorithmGe Medical Systems Information Technologies200342

Has anything in its family been recalled? (1 Class I)

Recalls of this device

DateClassRecallRoot causeReason
Aug 31, 2018Class IIZ-0520-2019Software designThe patient monitors may simultaneously restart as designed if all are connected to the same network and a network overload occurs for a prolonged time.

Relatives with a Class I recall

Class I is FDA’s most serious recall class. A recall in the family tree is context for this device, not evidence about it.

  • K133576Monitor B40Ge Medical Systems China Co., Ltd. · 2014 · 4 generations on · ◆ in the 2014 descendants bar of FIG. 11 Class I recall

What does this lineage say?

  • Its one ancestor has a recall.
  • Of its descendants, K030431 (Ge Medical Systems Information Technologies, 2003) has gone furthest, with 257 descendants of its own.
  • 1 other device also cites its predicate K001359.

How does its category compare?

All MHX devices

MHX 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

2007: 152008: 162009: 132010: 202011: 122012: 162013: 212014: 132015: 142016: 132017: 142018: 112019: 72020: 112021: 52022: 152023: 82024: 52025: 82026 (partial year): 14
2007high 21 (2013) · low 5 (2021)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · MHX

192in 2025

2007: 96 days median2008: 58 days median2009: 57 days median2010: 90 days median2011: 81 days median2012: 88 days median2013: 120 days median2014: 248 days median2015: 203 days median2016: 149 days median2017: 134 days median2018: 203 days median2019: 243 days median2020: 196 days median2021: 195 days median2022: 189 days median2023: 229 days median2024: 181 days median2025: 192 days median2026 (partial year): 205 days median
2007high 248 (2014) · low 57 (2009)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · MHX

21so far in 2026, the most since 2007

2007: 32008: 22009: 72010: 132011: 162012: 112013: 142014: 62015: 52016: 72017: 62018: 122019: 62022: 62023: 32024: 32025: 152026 (partial year): 21
2007high 21 (2026) · low 0 (2020)2026

Class I (0 since 2007) Class II/III not classified

Adverse event reports per year · MHX

3,761in 2025

2007: 1312008: 2322009: 3822010: 9552011: 9492012: 6762013: 1,9972014: 1,6092015: 1,2842016: 1,1052017: 1,1152018: 2,1572019: 1,4622020: 1,7142021: 2,4232022: 1,4702023: 2,2542024: 2,8142025: 3,761
2007high 3,761 (2025) · low 131 (2007)2025

MAUDE reports naming product code MHX, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
200715963131
200816582232
200913577382
2010209013955
2011128116949
2012168811676
201321120141,997
20141324861,609
20151420351,284
20161314971,105
20171413461,115
201811203122,157
2019724361,462
20201119601,714
2021519502,423
20221518961,470
2023822932,254
2024518132,814
20258192153,761
20261420521—

What is it indicated for?

The Dash 3000/4000 Patient 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, and transport monitor that can operate in all professional medical facilities and medical transport modes including but not limited to: emergency department, operating room…

Read the full statement (221 words)

The Dash 3000/4000 Patient 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, and transport monitor that can operate in all professional medical facilities and medical transport modes including but not limited to: emergency department, operating room, 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 surgical centers, and other alternate care facilities, intra-hospital patient transport, inter-hospital patient transport via ground vehicles (i.e., ambulance, etc.) and fixed and rotary winged aircraft, and pre-hospital emergency 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/4000 Patient Monitor is also intended to provide physiologic data over the Unity network to clinical information systems and allow the user to access hospital data 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 peripheral devices that support serial data outputs.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K020290: 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/K020290

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

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