510(k) Report

510(k) · Cleared

Recalled · Class II · 2018

Solar 9500 Information Monitor

K033964510(k) SpecialCleared Jan 15, 200424-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

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

Cleared on Jan 15, 2004 as substantially equivalent to K030575 (Ge Medical Systems Information Technologies, 2003) after a 24-day review. Its family tree reaches back 4 generations to 1990. It has been recalled once.

Decided
Jan 15, 2004
Review
24 days
Class
Class II
Product code
MHX
Recalls
1
Predicates
1

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

  1. Root · 4 generations backK900598 Tramscope SystemMarquette Electronics, Inc. · 1990
  2. 3 generations backK954852 Solar 9000 Anesthesia Information MonitorMarquette Electronics, Inc. · 1996
  3. 2 generations backK990068 Solar 9500 Information MonitorGeneral Electric Medical Systems Information Techn · 1999 · Recalled
  4. 1 generation backK030575 Modification to Solar 9500 Information MonitorGe Medical Systems Information Technologies · 2003 · Recalled
  5. This deviceK033964 Solar 9500 Information MonitorGe Medical Systems Information Technologies · 2004
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−4K900598Tramscope SystemMarquette Electronics, Inc.1990—
−3K954852Solar 9000 Anesthesia Information MonitorMarquette Electronics, Inc.1996—
−2K990068Solar 9500 Information MonitorGeneral Electric Medical Systems Information Techn19991
−1K030575Modification to Solar 9500 Information MonitorGe Medical Systems Information Technologies20032
0 (this device)K033964Solar 9500 Information MonitorGe Medical Systems Information Technologies2004—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
199310
FIG. 1 — Lineage of K033964, 1990–2004Source: 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 510(k) statement (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
*K030575Modification to Solar 9500 Information Monitor
Summary page 1
…alarm) 74DRT 21 CFR 870.2700 Oximeter, Pulse 74DQA Predicate Device: K030575 Solar 9500 Information Monitor Device Description: The Solar 9500 is a patient monitoring system that is desig…
Ge Medical Systems Information Technologies20032

What descends from it?

No later submission names this one as a predicate yet.

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

Recalls of this device

DateClassRecallRoot causeReason
Aug 31, 2018Class IIZ-0524-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.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 14 years and passes through 3 companies; a new generation was cleared every 3.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.

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 Solar® 9500 Information Monitoring System 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, in high acuity areas such as operating room (OR), post anesthesia recovery (PARR), critical care, surgical intensive care, respiratory intensive care, coronary care, medical intensive care, pediatric intensive…

Read the full statement (152 words)

The Solar® 9500 Information Monitoring System 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, in high acuity areas such as operating room (OR), post anesthesia recovery (PARR), critical care, surgical intensive care, respiratory intensive care, coronary care, medical intensive care, pediatric intensive care, or neonatal intensive care. Physiologic data includes electrocardiogram, invasive blood pressure, noninvasive blood pressure, pulse, temperature, cardiac output, respiration, pulse oximetry, carbon dioxide, oxygen, anesthetic gas concentrations and mixed venous oxygen saturation, as summarized in the Solar® 9500 Operator's Manual.

The Solar® 9500 Information Monitoring System is also intended to provide physiologic data over the Unity network to clinical information systems and allow the user to access hospital INTRAnet data via a Web Browser at the point-of-care.

This information can be displayed, trended, stored, and printed.

Indications for use as stated in the FDA 510(k) statement.

Cite this page

510(k) Report. “K033964: Solar 9500 Information Monitor.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 4, 2026. https://510kreport.com/device/K033964

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