510(k) Report

510(k) · Cleared

Recalled · 2006

Datex-Ohmeda S/5 Compact Critical Care Monitor with L-CICU02 & L-CICU02A Software

K022740510(k) TraditionalCleared Nov 14, 200287-day reviewClass II21 CFR 870.1025Recalls 2

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

Datex-Ohmeda · MLD Monitor, St Segment With Alarm

Cleared on Nov 14, 2002 as substantially equivalent to K002158 (Datex-Ohmeda, Inc., 2000) after an 87-day review. Its family tree reaches back 1 generation to 2000. 2 of the 15 devices in its family, counting itself, have a Class I recall. 13 later devices descend from it. It has been recalled 2 times.

Decided
Nov 14, 2002
Review
87 days
Class
Class II
Product code
MLD
Recalls
2
Predicates
1

Its longest line of descent runs back 1 generation to K002158 (2000). 13 later devices descend from it, 2 citing it directly. 2 of the 15 devices in this family, counting this one, have a Class I recall.

Descendants, by year cleared 2004: 1 descendant cleared, 1 with a Class I recall12007: 1 descendant cleared2012: 1 descendant cleared2013: 2 descendants cleared2014: 1 descendant cleared, 1 with a Class I recall12015: 2 descendants cleared2020: 1 descendant cleared2017: 1 descendant cleared2022: 1 descendant cleared2024: 1 descendant cleared2025: 1 descendant clearedK002158 · S/5 Compact Critical Care Monitor with S-00C03 or S-00C04 Software · Datex-Ohmeda, Inc. · 2000200020052010201520202025
Descendants, by generation 1 generation forward: 2 descendants, 1 with a Class I recall12 generations forward: 1 descendant3 generations forward: 2 descendants4 generations forward: 1 descendant, 1 with a Class I recall15 generations forward: 2 descendants6 generations forward: 2 descendants7 generations forward: 1 descendant8 generations forward: 2 descendants K002158 · S/5 Compact Critical Care Monitor with S-00C03 or S-00C04 Software · Datex-Ohmeda, Inc. · 20000+5
  1. Root · 1 generation backK002158 S/5 Compact Critical Care Monitor with S-00C03 or S-00C04 SoftwareDatex-Ohmeda, Inc. · 2000
  2. This deviceK022740 Datex-Ohmeda S/5 Compact Critical Care Monitor with L-CICU02 &…Datex-Ohmeda · 2002
  3. Descendant · cites it directly · 11 of its ownK043276 Datex-Ohmeda S/5TM FM with L-FICU04 and L-FICU04A Software and…Datex-Ohmeda · 2004 · Recalled (Class I)
  4. Descendant · 2 generations on · 10 of its ownK120598 Procare Monitor B40Ge Medical Systems China Co., Ltd. · 2012 · Recalled
  5. Descendant · 3 generations on · 8 of its ownK130584 Monitor B40Ge Medical Systems China Co., Ltd. · 2013 · Recalled
  6. Descendant · 4 generations on · 7 of its ownK133576 Monitor B40Ge Medical Systems China Co., Ltd. · 2014 · Recalled (Class I)
  7. Descendant · 5 generations on · 5 of its ownK151063 Monitor B40Ge Medical Systems China Co., Ltd. · 2015 · Recalled

Showing 5 of 13 descendants. See all descendants

Descendants cleared per year

2004: 12007: 12012: 12013: 22014: 12015: 22017: 12020: 12022: 12024: 12025: 1
2004high 2 (2013) · low 0 (2005)2026

Class I recalls in this family

Most influential descendants

Showing 5 of 13 · See all
  • K043276Datex-Ohmeda S/5TM FM with L-FICU04 and L-FICU04A Software and N-Fcrec ModuleDatex-Ohmeda · 2004 · cites it directly11descendants
  • K120598Procare Monitor B40Ge Medical Systems China Co., Ltd. · 2012 · 2 generations on10descendants
  • K130584Monitor B40Ge Medical Systems China Co., Ltd. · 2013 · 3 generations on8descendants
  • K133576Monitor B40Ge Medical Systems China Co., Ltd. · 2014 · 4 generations on7descendants
  • K151063Monitor B40Ge Medical Systems China Co., Ltd. · 2015 · 5 generations on5descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−1K002158S/5 Compact Critical Care Monitor with S-00C03 or S-00C04 SoftwareDatex-Ohmeda, Inc.2000—
0 (this device)K022740Datex-Ohmeda S/5 Compact Critical Care Monitor with L-CICU02 & L-CICU02A…Datex-Ohmeda2002—
+1K043276Datex-Ohmeda S/5TM FM with L-FICU04 and L-FICU04A Software and N-Fcrec ModuleDatex-Ohmeda2004Class I
+2K120598Procare Monitor B40Ge Medical Systems China Co., Ltd.20122
+3K130584Monitor B40Ge Medical Systems China Co., Ltd.20132
+4K133576Monitor B40Ge Medical Systems China Co., Ltd.2014Class I
+5K151063Monitor B40Ge Medical Systems China Co., Ltd.20151

Descendants by year cleared

Year clearedDevicesWith a Class I recall
200411
200710
201210
201320
201411
201520
201710
202010
202210
202410
202510
FIG. 1 — Lineage of K022740, 2000–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.

2 devices in this family have a Class I recall. A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

  • Candidate predicates for a device like this, rankedin the report
  • Recall history across each candidate’s familyin 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
*K002158S/5 Compact Critical Care Monitor with S-00C03 or S-00C04 Software
Summary page 4
…S/STMCompact Critical Care Monitor with L-CICUO2, which is a new revision of the predicate devices, S/STMCompact Critical Care Monitor with S-OOCO3 software (K002158). The S/STMCompact Critical Care Monitor with L-CICUO2 may be equipped with extended bedside arrhythrma analysis capability…
Datex-Ohmeda, Inc.2000—

What descends from it? (13)

See all 13

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

NumberDeviceApplicantDecidedDescendants
K043276Datex-Ohmeda S/5TM FM with L-FICU04 and L-FICU04A Software and N-Fcrec Module Class IDatex-Ohmeda200411
K071020Datex-Ohmeda S/5 Compact Critical Care Monitor with L-CICU05 and L-CICU05A SoftwareGE Healthcare20070

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

Recalls of this device

DateClassRecallRoot causeReason
Feb 6, 2006Not classifiedZ-1995-2009Software designGE Healthcare (Datex-Ohmeda) S/5 Critical Care Monitor and S/5 Compact Critical Care Monitor with L-CICU01, L-CICU02A, L-ICU05 & L-ICUO5A software had an issue where the Heart Rate (HR) was displaying as ---(3 dashes) when the monitor was…
Feb 6, 2006Not classifiedZ-1994-2009Software designGE Healthcare (Datex-Ohmeda) S/5 Critical Care Monitor and S/5 Compact Critical Care Monitor with L-CICU01, L-CICU02A, L-ICU05 & L-ICUO5A software had an issue where the Heart Rate (HR) was displaying as ---(3 dashes) when the monitor was…

Relatives with a Class I recall

Class I is FDA’s most serious recall class. A recall in the family tree is context for this device, not evidence about it.

  • K043276Datex-Ohmeda S/5TM FM with L-FICU04 and L-FICU04A Software and N-Fcrec ModuleDatex-Ohmeda · 2004 · Cites it directly · ◆ in the 2004 descendants bar of FIG. 11 Class I recall
  • K133576Monitor B40Ge Medical Systems China Co., Ltd. · 2014 · 4 generations on · ◆ in the 2014 descendants bar of FIG. 11 Class I recall

What does this lineage say?

  • Its one ancestor has no recall.
  • Of its descendants, K043276 (Datex-Ohmeda, 2004) has gone furthest, with 11 descendants of its own.

How does its category compare?

All MLD devices

MLD Monitor, St Segment With Alarm: FDA decisions, review times, recalls and adverse event reports over 20 years.

FDA decisions per year · MLD

1in 2010

2008: 12010: 1
2007high 1 (2008) · low 0 (2007)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · MLD

Too few MLD 510(k)s in any year since 2007 to give a median.

Recalls per year · MLD

No recall names MLD since 2007.

Adverse event reports per year · MLD

1in 2019

2007: 32008: 52009: 32010: 32011: 62012: 72014: 12015: 12017: 12018: 12019: 1
2007high 7 (2012) · low 0 (2013)2025

MAUDE reports naming product code MLD, 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
20070—03
20081—05
20090—03
20101—03
20110—06
20120—07
20130—00
20140—01
20150—01
20160—00
20170—01
20180—01
20190—01
20200—00
20210—00
20220—00
20230—00
20240—00
20250—00
20260—0—

What is it indicated for?

The S / 5 T M Compact Critical Care Monitor with L-CICUO2 and L-CICU02A software is indicated for monitoring of hemodynamic (including arrhythmia and ST-segment analysis), respiratory, ventilatory, gastrointestinal/regional perfusion, Bispectral index (BIS), and neurophysiological status of all hospital patients. The S / 5 T M Compact Critical Care Monitor with L-CICUO2 and L-CICU02A software when using BIS is for monitoring the state of the brain by…

Read the full statement (113 words)

The S / 5 T M Compact Critical Care Monitor with L-CICUO2 and L-CICU02A software is indicated for monitoring of hemodynamic (including arrhythmia and ST-segment analysis), respiratory, ventilatory, gastrointestinal/regional perfusion, Bispectral index (BIS), and neurophysiological status of all hospital patients.

The S / 5 T M Compact Critical Care Monitor with L-CICUO2 and L-CICU02A software when using BIS is for monitoring the state of the brain by data acquisition and processing of electroencephalograph signals and may be used as an aid in monitoring the effects of certain anesthetic agents.

The S / 5 T M Compact Critical Care Monitor with L-CICUO2 and L-CICU02A software is indicated for use by qualified medical personnel only.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K022740: Datex-Ohmeda S/5 Compact Critical Care Monitor with L-CICU02 & L-CICU02A Software.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 5, 2026. https://510kreport.com/device/K022740

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