510(k) Report

510(k) · Cleared

Cleared

Modification to Alarmview Wireless Data Network System

K012005510(k) SpecialCleared Jul 24, 200127-day reviewClass II21 CFR 870.2300

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

Data Critical Corp. · MSX System, Network And Communication, Physiological Monitors

Cleared on Jul 24, 2001 as substantially equivalent to K010912 (Data Critical Corp., 2001) after a 27-day review. Its family tree reaches back 1 generation to 2001. 1 later device descends from it.

Decided
Jul 24, 2001
Review
27 days
Class
Class II
Product code
MSX
Recalls
None
Predicates
1

Its longest line of descent runs back 1 generation to K010912 (2001). 1 later device descends from it, 1 citing it directly.

Descendants, by year cleared 2001: 1 descendant clearedK010912 · Alarmview Wireless Data Network System · Data Critical Corp. · 2001200020052010201520202025
Descendants, by generation 1 generation forward: 1 descendant K010912 · Alarmview Wireless Data Network System · Data Critical Corp. · 20010
  1. Root · 1 generation backK010912 Alarmview Wireless Data Network SystemData Critical Corp. · 2001
  2. This deviceK012005 Modification to Alarmview Wireless Data Network SystemData Critical Corp. · 2001
  3. Descendant · cites it directly · 0 of its ownK013156 Modification to Alarmview Wireless Data Network SystemData Critical Corp. · 2001

Most influential descendants

Showing 1 of 1 · See all
  • K013156Modification to Alarmview Wireless Data Network SystemData Critical Corp. · 2001 · cites it directly0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−1K010912Alarmview Wireless Data Network SystemData Critical Corp.2001—
0 (this device)K012005Modification to Alarmview Wireless Data Network SystemData Critical Corp.2001—
+1K013156Modification to Alarmview Wireless Data Network SystemData Critical Corp.2001—

Descendants by year cleared

Year clearedDevicesWith a Class I recall
200110
FIG. 1 — Lineage of K012005, 2001–2001Source: 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? (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
*K010912Alarmview Wireless Data Network System
Summary page 1
…assitication Name: System, Network and Communication, Physiological Monitors Device Classification: Class II Predicate Device(s): AlarmView™ Wireless Data Network System K010912 Device Description The modified AlarmView™ Wireless Data Network System is a low powered local area wireless paging system that…
Data Critical Corp.2001—

What descends from it? (1)

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

NumberDeviceApplicantDecidedDescendants
K013156Modification to Alarmview Wireless Data Network SystemData Critical Corp.20010

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?

  • Its one ancestor has no recall.
  • Of its descendants, K013156 (Data Critical Corp., 2001) has gone furthest, with 0 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?

The AlarmView™ Wireless Data Network System is for use in real-time monitoring of routine patient status and alarm events on medical devices. It serves as a parallel, redundant mechanism to inform the clinical staff of patient events. The AlarmView™ System provides a secondary means of annunciating and displaying patient alarm information to mobile healthcare professionals. The AlarmView™ Wireless Data Network System is limited to use by qualified…

Read the full statement (140 words)

The AlarmView™ Wireless Data Network System is for use in real-time monitoring of routine patient status and alarm events on medical devices. It serves as a parallel, redundant mechanism to inform the clinical staff of patient events. The AlarmView™ System provides a secondary means of annunciating and displaying patient alarm information to mobile healthcare professionals.

The AlarmView™ Wireless Data Network System is limited to use by qualified medical professionals who have been trained on the use of the device. It is for use in hospital and hospital type environments and is not for home use.

The AlarmView™ Wireless Data Network System is to supplement and not replace any part of the current device monitoring procedure.

The AlarmView™ Wireless Data Network System is not considered in and of itself to be diagnostic without skilled interpretation and does not replace physician’s care.

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. “K012005: Modification to Alarmview Wireless Data Network System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 3, 2026. https://510kreport.com/device/K012005

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 30, 2026 (extraction version 2d9447fa9ea4)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026