510(k) Report

510(k) · Cleared

Cleared

Modification to Dash 2500 Patient Monitor

K090702510(k) SpecialCleared Apr 15, 200929-day reviewClass II21 CFR 870.1025

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

Ge Medical Systems Information Technologies · MHX Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms)

Cleared on Apr 15, 2009 as substantially equivalent to K080157 (Ge Medical Systems Information Technologies, 2008) after a 29-day review. Its family tree reaches back 4 generations to 2000.

Decided
Apr 15, 2009
Review
29 days
Class
Class II
Product code
MHX
Recalls
None
Predicates
1

Its longest line of descent runs back 4 generations to K001359 (2000). 5 ancestors in all. No later device cites it as a predicate yet.

  1. Root · 4 generations backK001359 Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn · 2000 · Recalled
  2. 3 generations backK012915 Dinamap Pro 1000 Monitor, Model 1000Ge Medical Systems Information Technologies · 2002 · Recalled
  3. 2 generations backK031376 Dinamap Pro 1000 V3 Monitor, Model 1100 SeriesGe Medical Systems Information Technologies · 2003
  4. 1 generation backK080157 Dash 2500 Patient MonitorGe Medical Systems Information Technologies · 2008
  5. This deviceK090702 Modification to Dash 2500 Patient MonitorGe Medical Systems Information Technologies · 2009
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−4K001359Dash 3000/4000 Patient MonitorGeneral Electric Medical Systems Information Techn20001
−3K012915Dinamap Pro 1000 Monitor, Model 1000Ge Medical Systems Information Technologies20021
−2K031376Dinamap Pro 1000 V3 Monitor, Model 1100 SeriesGe Medical Systems Information Technologies2003—
−1K080157Dash 2500 Patient MonitorGe Medical Systems Information Technologies2008—
0 (this device)K090702Modification to Dash 2500 Patient MonitorGe Medical Systems Information Technologies2009—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
200010
FIG. 1 — Lineage of K090702, 2000–2009Source: 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.

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. #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
*K080157Dash 2500 Patient Monitor
Summary page 1
…Patient Monitor (with arrhythmia detection or alarms) Product Code: MHIX Predicate Device: K(080157 Dash 2500 Patient Monitor Device Description: The Dash 2500 Patient Monitor is a portable (intra-hospital) multi-…
Ge Medical Systems Information Technologies2008—

What descends from it?

No later submission names this one as a predicate yet.

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

No FDA recall names this device.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 9 years and passes through 2 companies; a new generation was cleared every 1.7 years on median.
  • 2 of the 5 ancestors have a recall of any class.

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. 2009, this device’s year, is highlighted.

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 2500 Patient Monitor is intended for use under the direct supervision of a licensed healthcare practitioner. The intended use of this device is a portable (intra-hospital) multiparameter unit designed for monitoring adult, pediatric, and neonate patient vital signs in a hospital subacute care environments, such as same-day surgery, emergency rooms, recovery/PACU, progressive care, interventional radiology, special care units, and GI/endoscopy.…

Read the full statement (165 words)

The Dash 2500 Patient Monitor is intended for use under the direct supervision of a licensed healthcare practitioner. The intended use of this device is a portable (intra-hospital) multiparameter unit designed for monitoring adult, pediatric, and neonate patient vital signs in a hospital subacute care environments, such as same-day surgery, emergency rooms, recovery/PACU, progressive care, interventional radiology, special care units, and GI/endoscopy.

The Dash 2500 Patient Monitor monitors and displays oscillometric non-invasive blood pressure (systolic, diastolic and mean arterial pressure), heart/pulse rate, respiration rate, ECG, temperature with an reusable electronic thermometer (predictive mode for oral and rectal temperature measurement, monitor mode for axillary temperature measurement), and functional oxygen saturation (SpO2) and pulse rate via spot checking and continuous monitoring, including monitoring during conditions of clinical patient motion or low perfusion.

The Dash 2500 Patient Monitor also detects alarm limit conditions and is capable of recording up to two waveforms. Using this monitor a clinician can view, record and recall clinical data derived from each parameter.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K090702: Modification to Dash 2500 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/K090702

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