510(k) · Cleared
ClearedM Visum Alert Alarm Management System
Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly
Mvisum, Inc. · MSX System, Network And Communication, Physiological Monitors
Cleared on Nov 4, 2011 as substantially equivalent to K990378 (Data Critical Corp., 1999) and 1 other predicate after an 87-day review. Its family tree reaches back 1 generation to 1999.
- Decided
- Nov 4, 2011
- Review
- 87 days
- Class
- Class II
- Product code
- MSX
- Recalls
- None
- Predicates
- 2
Its longest line of descent runs back 1 generation to K990378 (1999). 2 ancestors in all. No later device cites it as a predicate yet.
- Root · 1 generation backK990378 Statview SystemData Critical Corp. · 1999
- This deviceK112282 M Visum Alert Alarm Management SystemMvisum, Inc. · 2011
View FIG. 1 as a table
Line of descent and top descendants
| Generation | Number | Device | Applicant | Decided | Recalls |
|---|---|---|---|---|---|
| −1 | K990378 | Statview System | Data Critical Corp. | 1999 | — |
| 0 (this device) | K112282 | M Visum Alert Alarm Management System | Mvisum, Inc. | 2011 | — |
Other ancestors by year cleared
| Year cleared | Devices | With a Class I recall |
|---|---|---|
| 2006 | 1 | 0 |
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 K242750 Central Stationscore 21.5 · 31 generations · no Class I recall
- #2 Held for the reportin the report
- #3 Held for the reportin the report
What was it cleared against? (2)
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.
| Type | Number | Device | Decided |
|---|---|---|---|
| * | K990378 | Statview SystemSummary page 1…m) Predicate Devices: mVisum Alert Alarm Management System is substantially equivalent to previously cleared GE! Data Critical Corporation Statview System pursuant to K990378 and GE Web Viewer, Pocket Viewer, Cellular Viewer pursuant to K<061994. Device Description: The mVisum Alert Alarm Management Sy… | 1999 |
| * | K061994 | Web Viewer, Pocket Viewer and Cellular Viewer with L- WEB05 SoftwareSummary page 1…tially equivalent to previously cleared GE! Data Critical Corporation Statview System pursuant to K990378 and GE Web Viewer, Pocket Viewer, Cellular Viewer pursuant to K<061994. Device Description: The mVisum Alert Alarm Management System is a software based secondary alarm notification system that trans… | 2006 |
What descends from it?
No later submission names this one as a predicate yet.
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?
- 1 of the 2 ancestors has a recall of any class.
How does its category compare?
All MSX devicesMSX System, Network And Communication, Physiological Monitors: FDA decisions, review times, recalls and adverse event reports over 20 years. 2011, this device’s year, is highlighted.
FDA decisions per year · MSX
4in 2025
2026 to Oct 25, outlined.
Median 510(k) review, days · MSX
295in 2025
Receipt to decision; years with fewer than 3 clearances left blank.
Recalls per year · MSX
1in 2025
Class I (0 since 2007) Class II/III not classified
Adverse event reports per year · MSX
19in 2025
MAUDE reports naming product code MSX, not matched to any one device; reports are not rates.
View these four charts as a table
| Year | Decisions | Median 510(k) review, days | Recalls (Class I) | MAUDE reports |
|---|---|---|---|---|
| 2007 | 4 | 58 | 1 | 5 |
| 2008 | 1 | — | 1 | 6 |
| 2009 | 1 | — | 2 | 7 |
| 2010 | 3 | 43 | 1 | 14 |
| 2011 | 7 | 72 | 1 | 3 |
| 2012 | 4 | 145 | 2 | 4 |
| 2013 | 2 | — | 0 | 17 |
| 2014 | 3 | 165 | 0 | 32 |
| 2015 | 5 | 138 | 2 | 31 |
| 2016 | 3 | 174 | 0 | 11 |
| 2017 | 2 | — | 2 | 16 |
| 2018 | 4 | 111 | 1 | 15 |
| 2019 | 4 | 92 | 0 | 15 |
| 2020 | 5 | 193 | 0 | 25 |
| 2021 | 3 | 227 | 0 | 17 |
| 2022 | 5 | 177 | 1 | 18 |
| 2023 | 3 | 244 | 0 | 10 |
| 2024 | 4 | 212 | 0 | 32 |
| 2025 | 4 | 295 | 1 | 19 |
| 2026 | 5 | 145 | 2 | — |
What is it indicated for?
The mVisum Alert Alarm Management System is software intended for use to display status and alarm events from other medical devices and patient information systems and associated physiological and other patient information. It serves as a parallel, redundant mechanism to inform the clinical staff of patient events. It is intended to be a secondary means of annunciating and displaying patient alarm and physiological information to mobile healthcare…
Read the full statement (129 words)
The mVisum Alert Alarm Management System is software intended for use to display status and alarm events from other medical devices and patient information systems and associated physiological and other patient information. It serves as a parallel, redundant mechanism to inform the clinical staff of patient events. It is intended to be a secondary means of annunciating and displaying patient alarm and physiological information to mobile healthcare providers.
The mVisum Alert Alarm Management System is limited to use by qualified medical professionals who have been trained on the use of the system. It is intended to supplement and not to replace any part of the current patient monitoring systems. It is not considered in and of itself to be diagnostic without skilled interpretation and does not replace physician's care.
Indications for use as stated in the FDA summary.
https://510kreport.com/device/K112282 · printed Nov 6, 2026
Cite this page
510(k) Report. “K112282: M Visum Alert Alarm Management System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K112282
Report an extraction error
Are you the manufacturer?
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