510(k) Report

510(k) · Cleared

Recalled · Class II · 2014

Viewpoint Telemetry System

K031760510(k) AbbreviatedCleared Oct 10, 2003126-day reviewClass II21 CFR 870.1025Recalls 5

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

Datascope Corp. · MHX Monitor, Physiological, Patient (With Arrhythmia Detection Or Alarms)

Cleared on Oct 10, 2003 as substantially equivalent to K021681 (Welch Allyn Protocol, Inc., 2002) and 2 other predicates after a 126-day review. Its family tree reaches back 3 generations to 1990. 2 later devices descend from it. It has been recalled 5 times.

Decided
Oct 10, 2003
Review
126 days
Class
Class II
Product code
MHX
Recalls
5
Predicates
3

Its longest line of descent runs back 3 generations to K903702 (1990). 12 ancestors in all. 2 later devices descend from it, 1 citing it directly.

Other ancestors, by year clearedDescendants, by year cleared 2002: 2 other ancestors2000: 1 other ancestor1997: 1 other ancestor1994: 1 other ancestor1991: 2 other ancestors1995: 1 other ancestor1993: 1 other ancestor2014: 1 descendant cleared2015: 1 descendant clearedK903702 · Model 90421 Flexport Interface · Spacelabs, Inc. · 1990 · recalledK962473 · (Vcom, Irvs, RVS) Central Monitoring Station, V-Link or Ambulatory Transmitters and Arrhytmia Detector and Alarms with · Data Critical Corporation · 1997K020524 · Patientnet Monitoring System · General Electric Medical Systems Information Techn · 2002 · recalled1990200020102020
Other ancestors, by generationDescendants, by generation 1 generation back: 2 other ancestors2 generations back: 4 other ancestors3 generations back: 3 other ancestors 1 generation forward: 1 descendant2 generations forward: 1 descendant K020524 · Patientnet Monitoring System · General Electric Medical Systems Information Techn · 2002 · recalledK962473 · (Vcom, Irvs, RVS) Central Monitoring Station, V-Link or Ambulatory Transmitters and Arrhytmia Detector and Alarms with · Data Critical Corporation · 1997K903702 · Model 90421 Flexport Interface · Spacelabs, Inc. · 1990 · recalled0
  1. Root · 3 generations backK903702 Model 90421 Flexport InterfaceSpacelabs, Inc. · 1990 · Recalled
  2. 2 generations backK962473 (Vcom, Irvs, RVS) Central Monitoring Station, V-Link or Ambulatory…Data Critical Corporation · 1997
  3. 1 generation backK020524 Patientnet Monitoring SystemGeneral Electric Medical Systems Information Techn · 2002 · Recalled
  4. This deviceK031760 Viewpoint Telemetry SystemDatascope Corp. · 2003
  5. Descendant · cites it directly · 1 of its ownK142601 Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co. · 2014 · Recalled
  6. Descendant · 2 generations on · 0 of its ownK150082 Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co., Ltd. · 2015 · Recalled

Most influential descendants

Showing 2 of 2 · See all
  • K142601Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co. · 2014 · cites it directly1descendant
  • K150082Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co., Ltd. · 2015 · 2 generations on0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−3K903702Model 90421 Flexport InterfaceSpacelabs, Inc.19901
−2K962473(Vcom, Irvs, RVS) Central Monitoring Station, V-Link or Ambulatory…Data Critical Corporation1997—
−1K020524Patientnet Monitoring SystemGeneral Electric Medical Systems Information Techn20021
0 (this device)K031760Viewpoint Telemetry SystemDatascope Corp.2003—
+1K142601Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co.20141
+2K150082Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co., Ltd.20151

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
199120
199310
199410
199510
199710
200010
200220

Descendants by year cleared

Year clearedDevicesWith a Class I recall
201410
201510
FIG. 1 — Lineage of K031760, 1990–2015Source: 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? (3)

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
*K021681Micropaq, Models 402, 404Welch Allyn Protocol, Inc.2002—
*K022453Modification to Acuity Central Monitoring SystemWelch Allyn Protocol, Inc.20021
*K020524Patientnet Monitoring SystemGeneral Electric Medical Systems Information Techn20021

Also cleared against K021681: 2 other devices →

What descends from it? (2)

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

NumberDeviceApplicantDecidedDescendants
K142601Panorama Patient Monitoring NetworkShenzhen Mindray Bio-Medical Electronics Co.20141

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

Recalls of this device

DateClassRecallRoot causeReason
Jan 8, 2014Class IIZ-1156-2014Software designMindray has identified two issues with the Panorama Central Station. Full Disclosure data may lag behind the Panorama system time clock when the Panorama Central Station is in use with Mindray¿s V-Series Monitor. Additionally, event…
Apr 10, 2009Not classifiedZ-1401-2009Software designSoftware Anomaly: Software anomaly can occur when the Panorama is attempting to play an audio file, either a physiological or technical alarm sound, at which time the system software may cause the system to freeze due to an interaction in…
Dec 7, 2005Not classifiedZ-0437-06OtherSoftware anomaly that affects the Panorama Telepack where if communications are lost during standby, certain alarms which appear set could be actually off.
Aug 19, 2005Not classifiedZ-1567-05OtherThe software version contains an anomaly which could freeze the unit when the right click button is used on the mouse.
Jun 16, 2005Not classifiedZ-1104-05OtherUpon the new release of software, the firm started receiving reports of unexpected system failures in the database subsystem related to virtual memory pages.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 13 years and passes through 4 companies; a new generation was cleared every 4.4 years on median.
  • 3 of the 12 ancestors have a recall of any class.
  • Of its descendants, K142601 (Shenzhen Mindray Bio-Medical Electronics Co., 2014) has gone furthest, with 1 descendant of its own.
  • 2 other devices also cite its predicate K021681.

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 Indications for use for the Viewpoint Central Monitoring System include: Viewing real time patient clinical and demographic data Graphical and numeric trending of clinical data Storing and printing of clinical and demographic data Setting independent alarm limits for data sent by the bedside monitor. The clinical data displayed by the Viewpoint Central Monitoring System is obtained from one or more Datascope compatible physiological monitors and…

Read the full statement (268 words)

The Indications for use for the Viewpoint Central Monitoring System include:

Viewing real time patient clinical and demographic data

Graphical and numeric trending of clinical data

Storing and printing of clinical and demographic data

Setting independent alarm limits for data sent by the bedside monitor.

The clinical data displayed by the Viewpoint Central Monitoring System is obtained from one or more Datascope compatible physiological monitors and includes: ECG waveforms, Invasive and Non-Invasive Blood Pressure, Blood Oxygenation (Sp02), Heart Rate, Respiration Rate, Temperature, C 0 2 inspired and end-tidal, Ventricular Arrythmia analysis and ST Segment analysis.

The Viewpoint Central Monitoring System is intended for use in a fixed location, in the health care facility setting, as a central viewing station. The Viewpoint Central Monitoring System is not intended to be directly connected to the patient at any time, or installed in a patient's vicinity.

The Viewpoint 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 Viewpoint Telemetry System is intended for installation in the hospital or clinical environment to provide clinicians with patient physiological data, while allowing for patient mobility.

The physiological parameters monitored include ECG, Heart Rate from ECG, Lethal and Non-Lethal Arrhythmia Detection and ST Segment Analysis. Received data is sent to the Viewpoint Server for ECG processing via Ethernet. This information can be displayed, trended, stored, and printed at the Viewpoint Central Station.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K031760: Viewpoint Telemetry System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K031760

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