510(k) Report

510(k) · Cleared

Recalled · Class II · 2019

Modification of Apexpro Telemetry System

K021325510(k) SpecialCleared May 7, 200211-day reviewClass II21 CFR 870.1025Recalls 2

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 May 7, 2002 as substantially equivalent to K000779 (General Electric Medical Systems Information Techn, 2000) after an 11-day review. Its family tree reaches back 1 generation to 2000. 4 later devices descend from it. It has been recalled 2 times.

Decided
May 7, 2002
Review
11 days
Class
Class II
Product code
MHX
Recalls
2
Predicates
1

Its longest line of descent runs back 1 generation to K000779 (2000). 4 later devices descend from it, 1 citing it directly.

Descendants, by year cleared 2003: 2 descendants cleared2008: 1 descendant cleared2016: 1 descendant clearedK000779 · Apexpro Telemetry System · General Electric Medical Systems Information Techn · 2000 · recalled200020052010201520202025
Descendants, by generation 1 generation forward: 1 descendant2 generations forward: 2 descendants3 generations forward: 1 descendant K000779 · Apexpro Telemetry System · General Electric Medical Systems Information Techn · 2000 · recalled0
  1. Root · 1 generation backK000779 Apexpro Telemetry SystemGeneral Electric Medical Systems Information Techn · 2000 · Recalled
  2. This deviceK021325 Modification of Apexpro Telemetry SystemGeneral Electric Medical Systems Information Techn · 2002
  3. Descendant · cites it directly · 3 of its ownK032369 Modification to: Apexpro Telemetry SystemGe Medical Systems Information Technologies · 2003 · Recalled
  4. Descendant · 2 generations on · 2 of its ownK033365 Apexpro FH Telemetry SystemGe Medical Systems Information Technologies · 2003 · Recalled
  5. Descendant · 2 generations on · 1 of its ownK080251 Apexpro Telemetry SystemsGe Medical Systems Information Technologies · 2008 · Recalled
  6. Descendant · 3 generations on · 0 of its ownK160685 Surveyor S4 Mobile MonitorMortara Instrument, Inc. · 2016 · Recalled

Most influential descendants

Showing 4 of 4 · See all
  • K032369Modification to: Apexpro Telemetry SystemGe Medical Systems Information Technologies · 2003 · cites it directly3descendants
  • K033365Apexpro FH Telemetry SystemGe Medical Systems Information Technologies · 2003 · 2 generations on2descendants
  • K080251Apexpro Telemetry SystemsGe Medical Systems Information Technologies · 2008 · 2 generations on1descendant
  • K160685Surveyor S4 Mobile MonitorMortara Instrument, Inc. · 2016 · 3 generations on0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−1K000779Apexpro Telemetry SystemGeneral Electric Medical Systems Information Techn20002
0 (this device)K021325Modification of Apexpro Telemetry SystemGeneral Electric Medical Systems Information Techn2002—
+1K032369Modification to: Apexpro Telemetry SystemGe Medical Systems Information Technologies20034
+2K033365Apexpro FH Telemetry SystemGe Medical Systems Information Technologies20033
+2K080251Apexpro Telemetry SystemsGe Medical Systems Information Technologies20084
+3K160685Surveyor S4 Mobile MonitorMortara Instrument, Inc.20161

Descendants by year cleared

Year clearedDevicesWith a Class I recall
200320
200810
201610
FIG. 1 — Lineage of K021325, 2000–2016Source: 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
*K000779Apexpro Telemetry System
Summary page 1
…Classification Names: 21 CFR 870.1025 Detector and Alarm, Arrhythmia 21 CFR 870.2910 Transmitters & Receivers, Physiological Signal, Radio Frequency Predicate Device: K000779 ApexPro Telemetry System Device Description: The ApexPro Telemetry System is composed of six major components: e The patient wor…
General Electric Medical Systems Information Techn20002

Also cleared against K000779: 1 other device →

What descends from it? (4)

1 later device cites it directly; ranked here by how many devices descend from each in turn.

NumberDeviceApplicantDecidedDescendants
K032369Modification to: Apexpro Telemetry SystemGe Medical Systems Information Technologies20033

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

Recalls of this device

DateClassRecallRoot causeReason
Nov 12, 2019Class IIZ-0725-2020Software in the Use EnvironmentWhen connected to the Mission Critical (MC) and /or Information Exchange (IX) networks, certain versions of the CARESCAPE Telemetry Server, ApexPro Telemetry Server, CARESCAPE Central Station (CSCS) version 1 and Central Information…
Aug 30, 2019Class IIZ-0175-2020Software designMay not provide visual and/or audible alarms at the CARESCAPE Central Station or Clinical Information Center monitor for ECG arrhythmias, ECG LEADS FAIL or Pulse Oximetry (SpO2) under certain conditions.

No ancestor or descendant has a Class I recall.

What does this lineage say?

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

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 ApexPro Telemetry System is intended for use under the direct supervision of a licensed healthcare practitioner. The system is designed to acquire and monitor physiological data for ambulating patients within a defined coverage area. The system processes this physiological data to detect various ECG arrhythmia events and select physiological parameter limit violations. The ApexPro Telemetry System is intended to be installed in the hospital or…

Read the full statement (157 words)

The ApexPro Telemetry System is intended for use under the direct supervision of a licensed healthcare practitioner. The system is designed to acquire and monitor physiological data for ambulating patients within a defined coverage area. The system processes this physiological data to detect various ECG arrhythmia events and select physiological parameter limit violations.

The ApexPro Telemetry System is intended to be installed in the hospital or clinical environment in order to provide clinicians with patient physiological data, while allowing for patient mobility. These systems are typically deployed in sub acute care areas in hospitals or clinical sites where patient mobility can enhance the effectiveness of the medical procedures administered.

The physiological parameters monitored include ECG, non-invasive blood pressure and SpO.. The ApexPro Telemetry System is intended to provide ECG data via Ethernet to the computer platform for processing. The ApexPro is also intended to provide physiologic data over the Unity network to clinical information systems for display.

Indications for use read by OCR from a scanned FDA summary, so letters may be misread. Check the PDF before quoting it.

Cite this page

510(k) Report. “K021325: Modification of Apexpro Telemetry System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 4, 2026. https://510kreport.com/device/K021325

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