510(k) Report

510(k) · Cleared

Recalled · 2008

Web Viewer, Pocket Viewer and Cellular Viewer with L- WEB05 Software

K061994510(k) SpecialCleared Aug 11, 200628-day reviewClass II21 CFR 870.2300Recalls 1

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

GE Healthcare · MSX System, Network And Communication, Physiological Monitors

Cleared on Aug 11, 2006 after a 28-day review. The FDA summary names no predicate by number. 8 later devices descend from it. It has been recalled once.

Decided
Aug 11, 2006
Review
28 days
Class
Class II
Product code
MSX
Recalls
1
Predicates
0

8 later devices descend from it, 2 citing it directly.

Descendants, by year cleared 2011: 1 descendant cleared2010: 1 descendant cleared2015: 1 descendant cleared2023: 1 descendant cleared2022: 1 descendant cleared2025: 1 descendant cleared2024: 2 descendants cleared20052010201520202025
  1. This deviceK061994 Web Viewer, Pocket Viewer and Cellular Viewer with L- WEB05 SoftwareGE Healthcare · 2006
  2. Descendant · cites it directly · 6 of its ownK100133 Airstrip Remote Patient Monitoring (RPM) Remote Data Viewing…Airstrip Technologies, LP · 2010
  3. Descendant · 2 generations on · 5 of its ownK142106 Decisio Health Patient DashboardDecisio Health, Inc. · 2015
  4. Descendant · 3 generations on · 3 of its ownK213335 Capsule Surveillance SystemCapsule Surveillance Technologies, Sas /Capsule Tech, Inc. · 2022
  5. Descendant · 4 generations on · 0 of its ownK241958 WARD-CSS (v1.2.x)Ward 24/7 Aps · 2025
  6. Descendant · 4 generations on · 0 of its ownK240756 Aitrics-VCAitrics Co., Ltd. · 2024

Showing 5 of 8 descendants. See all descendants

Descendants cleared per year

2010: 12011: 12015: 12022: 12023: 12024: 22025: 1
2010high 2 (2024) · low 0 (2012)2026

Most influential descendants

Showing 5 of 8 · See all
  • K100133Airstrip Remote Patient Monitoring (RPM) Remote Data Viewing Software, Version 3.1Airstrip Technologies, LP · 2010 · cites it directly6descendants
  • K142106Decisio Health Patient DashboardDecisio Health, Inc. · 2015 · 2 generations on5descendants
  • K213335Capsule Surveillance SystemCapsule Surveillance Technologies, Sas /Capsule Tech, Inc. · 2022 · 3 generations on3descendants
  • K241958WARD-CSS (v1.2.x)Ward 24/7 Aps · 2025 · 4 generations on0descendants
  • K240756Aitrics-VCAitrics Co., Ltd. · 2024 · 4 generations on0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
0 (this device)K061994Web Viewer, Pocket Viewer and Cellular Viewer with L- WEB05 SoftwareGE Healthcare2006—
+1K100133Airstrip Remote Patient Monitoring (RPM) Remote Data Viewing Software, Version…Airstrip Technologies, LP2010—
+2K142106Decisio Health Patient DashboardDecisio Health, Inc.2015—
+3K213335Capsule Surveillance SystemCapsule Surveillance Technologies, Sas /Capsule Tech, Inc.2022—
+4K241958WARD-CSS (v1.2.x)Ward 24/7 Aps2025—
+4K240756Aitrics-VCAitrics Co., Ltd.2024—

Descendants by year cleared

Year clearedDevicesWith a Class I recall
201010
201110
201510
202210
202310
202420
202510
FIG. 1 — Lineage of K061994, 2006–2025Source: 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 MSX? 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 MSX device

  1. #1 K242750 Central Stationscore 21.5 · 31 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?

The FDA summary names no predicate by number.

What descends from it? (8)

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

NumberDeviceApplicantDecidedDescendants
K100133Airstrip Remote Patient Monitoring (RPM) Remote Data Viewing Software, Version 3.1Airstrip Technologies, LP20106
K112282M Visum Alert Alarm Management SystemMvisum, Inc.20110

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

Recalls of this device

DateClassRecallRoot causeReason
Jul 16, 2008Not classifiedZ-0213-2009Software designIssue 1 -Possible failure of CIC Pro audible alarms: Requests for telemetry defaults from Mobile Care Server could cause excessive CIC Pro memory consumption. This excessive memory consumption may lead to potential loss of audio at the…

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • Of its descendants, K100133 (Airstrip Technologies, LP, 2010) has gone furthest, with 6 descendants of its own.

How does its category compare?

All MSX devices

MSX System, Network And Communication, Physiological Monitors: FDA decisions, review times, recalls and adverse event reports over 20 years.

FDA decisions per year · MSX

4in 2025

2007: 42008: 12009: 12010: 32011: 72012: 42013: 22014: 32015: 52016: 32017: 22018: 42019: 42020: 52021: 32022: 52023: 32024: 42025: 42026 (partial year): 5
2007high 7 (2011) · low 1 (2008)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · MSX

295in 2025

2007: 58 days median2010: 43 days median2011: 72 days median2012: 145 days median2014: 165 days median2015: 138 days median2016: 174 days median2018: 111 days median2019: 92 days median2020: 193 days median2021: 227 days median2022: 177 days median2023: 244 days median2024: 212 days median2025: 295 days median2026 (partial year): 145 days median
2007high 295 (2025) · low 43 (2010)2026

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

Recalls per year · MSX

1in 2025

2007: 12008: 12009: 22010: 12011: 12012: 22015: 22017: 22018: 12022: 12025: 12026 (partial year): 2
2007high 2 (2009) · low 0 (2013)2026

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

Adverse event reports per year · MSX

19in 2025

2007: 52008: 62009: 72010: 142011: 32012: 42013: 172014: 322015: 312016: 112017: 162018: 152019: 152020: 252021: 172022: 182023: 102024: 322025: 19
2007high 32 (2014) · low 3 (2011)2025

MAUDE reports naming product code MSX, 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
200745815
20081—16
20091—27
2010343114
201177213
2012414524
20132—017
20143165032
20155138231
20163174011
20172—216
20184111115
2019492015
20205193025
20213227017
20225177118
20233244010
20244212032
20254295119
202651452—

What is it indicated for?

Indication for use for Web Viewer- The Web Viewer displays Information received from other networked devices. It is comprised of a Mobile Care Server and Web Viewer clients. The Mobile CareServer maintains and coordinates the network connections between the devices in the Datex-Ohmeda Network or Unity Network and Web Vwer clients. The Web Vier client runs on a generic computer that is connected to the hospital local area network (LAN), The Web Viewer can…

Read the full statement (397 words)

Indication for use for Web Viewer- The Web Viewer displays Information received from other networked devices. It is comprised of a Mobile Care Server and Web Viewer clients. The Mobile CareServer maintains and coordinates the network connections between the devices in the Datex-Ohmeda Network or Unity Network and Web Vwer clients. The Web Vier client runs on a generic computer that is connected to the hospital local area network (LAN), The Web Viewer can be used for viewing or otherwise processing of information from several bedside monitors or other networked devices. The Web Viewer can be used for patients in the hospital and it is meant for consultation and remote monitoring use. The Web Viewe is not a primary alarm source. The device is for use by qualified medical personnel only.

Indication for use for Pocket Viewer. The Pocket Viewer displays information received froe other networked devices. It is cornpised of a Mobile Care Seaver and Pocket Viewer clients. The Mobile Cam Server maintains and coordinates the network connections between the devices in the Datex-Ohmeda Network or Unity Network and Pocket Viewer clients. The Pocket Viwver client runs on a generic handheld computer (PDA) that is connected to the hospital local area network (LAN). The Pocket Viewer can be used for viewing or otherwise processing o information from several bedside monitors or ether networked devices. The Pocket Viewer can be used for patients in the hospital and it is meant for consultation and remote monitoring use. The Pocket Viewer is not a primary alarm source. The device is for use by qualified medical personnel only.

Indication for use for Cellular Viewer The Cellular Viewer displays information received from other networked devices. It is crnprised of a Mobile Care Server and Cellular Viewer clients. The Mobile Care Server maintains and coordinates the network connections between the devices in the Datex-Ohoreda Network or Unity Network and Cellular Viewer clients. The Cellular Viewer client runs on a generic cellular phone that is connected to the hospital local area network (LAN). The Cellular Viewer can be used fo viewing or otherwise processing of information from several bedside monitors or ether networked devices. The Cellular Viwer can be used for patients in the hospital and it is mearn for consultation and remote monitoring use. The Cellular Viewer is not a primary alarm source. The device is for use by qualified personnel only.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K061994: Web Viewer, Pocket Viewer and Cellular Viewer with L- WEB05 Software.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K061994

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