510(k) · Cleared
ClearedVitalogik
Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly
Mennen Medical, Ltd. · DSI Detector And Alarm, Arrhythmia
Cleared on Dec 20, 2005 as substantially equivalent to K001120 (Mennen Medical, Ltd., 2001) after a 119-day review. Its family tree reaches back 1 generation to 2001. 2 later devices descend from it.
- Decided
- Dec 20, 2005
- Review
- 119 days
- Class
- Class II
- Product code
- DSI
- Recalls
- None
- Predicates
- 1
Its longest line of descent runs back 1 generation to K001120 (2001). 2 later devices descend from it, 2 citing it directly.
- Root · 1 generation backK001120 Envoy Patient MonitorMennen Medical, Ltd. · 2001
- This deviceK052288 VitalogikMennen Medical, Ltd. · 2005
- Descendant · cites it directly · 0 of its ownK073140 Vitalogik Model 4000/4500Mennen Medical, Ltd. · 2007
- Descendant · cites it directly · 0 of its ownK070254 Horizon SEMennen Medical, Ltd. · 2007
Most influential descendants
Showing 2 of 2 · See allView FIG. 1 as a table
Line of descent and top descendants
| Generation | Number | Device | Applicant | Decided | Recalls |
|---|---|---|---|---|---|
| −1 | K001120 | Envoy Patient Monitor | Mennen Medical, Ltd. | 2001 | — |
| 0 (this device) | K052288 | Vitalogik | Mennen Medical, Ltd. | 2005 | — |
| +1 | K073140 | Vitalogik Model 4000/4500 | Mennen Medical, Ltd. | 2007 | — |
| +1 | K070254 | Horizon SE | Mennen Medical, Ltd. | 2007 | — |
Descendants by year cleared
| Year cleared | Devices | With a Class I recall |
|---|---|---|
| 2007 | 2 | 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 DSI? 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 DSI device
- #1 K243349 BodyGuardian Remote Monitoring System (BGRMS…score 13.1 · 9 generations · no Class I recall
- #2 Held for the reportin the report
- #3 Held for the reportin the 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.
| Type | Number | Device | Decided |
|---|---|---|---|
| * | K001120 | Envoy Patient MonitorSummary page 3…for marketing by the FDA in the following 510(k) submittals: · K974510 - 14th April 1998 * K983864 - 8 th October 1999 * K000563 -- 17 h May 2000 * K001120 -O th May2001 * K011784 -16th August 2001 · K022168 - 1st August 2002 VitaLogik = Subject of this Special 510(k). The… | 2001 |
What descends from it? (2)
2 later devices cite it directly; ranked here by how many devices descend from each in turn.
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?
How does its category compare?
All DSI devicesDSI Detector And Alarm, Arrhythmia: FDA decisions, review times, recalls and adverse event reports over 20 years.
FDA decisions per year · DSI
1in 2025
2026 to Oct 25, outlined.
Median 510(k) review, days · DSI
243in 2019
Receipt to decision; years with fewer than 3 clearances left blank.
Recalls per year · DSI
18in 2025
Class I (0 since 2007) Class II/III not classified
Adverse event reports per year · DSI
712in 2025
MAUDE reports naming product code DSI, 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 | 7 | 151 | 4 | 64 |
| 2008 | 5 | 70 | 8 | 156 |
| 2009 | 6 | 73 | 3 | 279 |
| 2010 | 6 | 111 | 5 | 823 |
| 2011 | 6 | 114 | 3 | 793 |
| 2012 | 3 | 113 | 1 | 766 |
| 2013 | 1 | — | 0 | 795 |
| 2014 | 4 | 200 | 0 | 1,000 |
| 2015 | 9 | 127 | 0 | 1,645 |
| 2016 | 6 | 224 | 0 | 4,352 |
| 2017 | 0 | — | 0 | 3,594 |
| 2018 | 2 | — | 1 | 3,648 |
| 2019 | 3 | 243 | 4 | 3,485 |
| 2020 | 2 | — | 2 | 3,084 |
| 2021 | 0 | — | 0 | 3,092 |
| 2022 | 0 | — | 1 | 1,638 |
| 2023 | 2 | — | 2 | 1,616 |
| 2024 | 1 | — | 0 | 1,320 |
| 2025 | 1 | — | 18 | 712 |
| 2026 | 1 | — | 1 | — |
What is it indicated for?
VitaLogik is intended for use as a multiparameter physiological patient monitoring system. The VitaLogik can monitor ECG/heart rate, two invasive blood pressure channels, two temperature channels, pulse oximetry, respiration, non-invasive blood pressure and EtCO2. This effectively allows the VitaLogik to monitor a wide-range of adult, pediatric and neonatal patient conditions, in many different areas of the hospital. Functions include display of…
Read the full statement (120 words)
VitaLogik is intended for use as a multiparameter physiological patient monitoring system.
The VitaLogik can monitor ECG/heart rate, two invasive blood pressure channels, two temperature channels, pulse oximetry, respiration, non-invasive blood pressure and EtCO2. This effectively allows the VitaLogik to monitor a wide-range of adult, pediatric and neonatal patient conditions, in many different areas of the hospital.
Functions include display of multiparameter waveforms, vital signs, alarm & status messages.
The Mennen Medical VitaLogik is intended for sale as a system for monitoring and recording patient information or any in-hospital application requiring patient monitoring.
The following are examples of intended clinical applications:
* Critical Care Patients
* Cardiac Step-down/Telemetry Units
* Emergency Departments
* Intra-operative (Anesthesia) Monitoring
* Post Anesthesia Care
Indications for use as stated in the FDA summary.
https://510kreport.com/device/K052288 · printed Nov 6, 2026
Cite this page
510(k) Report. “K052288: Vitalogik.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K052288
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