510(k) Report

510(k) · Cleared

Cleared

506CN Patient Monitor

K091050510(k) SpecialCleared May 27, 200944-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

Criticare Systems, Inc. · DRT Monitor, Cardiac (Incl. Cardiotachometer & Rate Alarm)

Cleared on May 27, 2009 as substantially equivalent to K051038 (Ciriticare Systems, Inc., 2005) after a 44-day review. Its family tree reaches back 3 generations to 1995. 1 later device descends from it.

Decided
May 27, 2009
Review
44 days
Class
Class II
Product code
DRT
Recalls
None
Predicates
1

Its longest line of descent runs back 3 generations to K944860 (1995). 1 later device descends from it, 1 citing it directly.

  1. Root · 3 generations backK944860 Scholar Patient MonitorCriticare Systems, Inc. · 1995
  2. 2 generations backK022435 507EL Vital Signs MonitorCriticare Systems, Inc. · 2002
  3. 1 generation backK051038 506 Patient MonitorCiriticare Systems, Inc. · 2005
  4. This deviceK091050 506CN Patient MonitorCriticare Systems, Inc. · 2009
  5. Descendant · cites it directly · 0 of its ownK101602 Vital Signs MonitorCriticare Systems, Inc. · 2010

Most influential descendants

Showing 1 of 1 · See all
  • K101602Vital Signs MonitorCriticare Systems, Inc. · 2010 · cites it directly0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−3K944860Scholar Patient MonitorCriticare Systems, Inc.1995—
−2K022435507EL Vital Signs MonitorCriticare Systems, Inc.2002—
−1K051038506 Patient MonitorCiriticare Systems, Inc.2005—
0 (this device)K091050506CN Patient MonitorCriticare Systems, Inc.2009—
+1K101602Vital Signs MonitorCriticare Systems, Inc.2010—

Descendants by year cleared

Year clearedDevicesWith a Class I recall
201010
FIG. 1 — Lineage of K091050, 1995–2010Source: 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 DRT? 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 DRT device

  1. #1 K252676 The Circadia C300 System (C300)score 15.3 · 6 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
*K051038506 Patient MonitorCiriticare Systems, Inc.2005—

Also cleared against K051038: 1 other device →

What descends from it? (1)

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

NumberDeviceApplicantDecidedDescendants
K101602Vital Signs MonitorCriticare Systems, Inc.20100

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?

  • The line of descent spans 14 years and passes through 2 companies; a new generation was cleared every 3.8 years on median.
  • None of the 3 ancestors has a recall.
  • Of its descendants, K101602 (Criticare Systems, Inc., 2010) has gone furthest, with 0 descendants of its own.
  • 1 other device also cites its predicate K051038.

How does its category compare?

All DRT devices

DRT Monitor, Cardiac (Incl. Cardiotachometer & Rate Alarm): FDA decisions, review times, recalls and adverse event reports over 20 years. 2009, this device’s year, is highlighted.

FDA decisions per year · DRT

1in 2025

2007: 12008: 12009: 62010: 32011: 32012: 12013: 12015: 12016: 12017: 12018: 12019: 12021: 22022: 12023: 12024: 32025: 12026 (partial year): 5
2007high 6 (2009) · low 0 (2014)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · DRT

228in 2024

2009: 70 days median2010: 44 days median2011: 149 days median2024: 228 days median2026 (partial year): 120 days median
2007high 228 (2024) · low 44 (2010)2026

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

Recalls per year · DRT

1in 2024

2011: 12021: 12024: 1
2007high 1 (2011) · low 0 (2007)2026

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

Adverse event reports per year · DRT

40in 2025

2007: 1132008: 992009: 1182010: 632011: 362012: 472013: 162014: 262015: 482016: 552017: 1592018: 2242019: 4472020: 502021: 852022: 352023: 472024: 292025: 40
2007high 447 (2019) · low 16 (2013)2025

MAUDE reports naming product code DRT, 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
20071—0113
20081—099
20096700118
2010344063
20113149136
20121—047
20131—016
20140—026
20151—048
20161—055
20171—0159
20181—0224
20191—0447
20200—050
20212—185
20221—035
20231—047
20243228129
20251—040
202651200—

What is it indicated for?

This system is intended to monitor physiological parameters of patients within any healthcare environment. The user, responsible to interpret the monitored data made available, will be a professional health care provider. Physiological data, system alarms and patient data analysis will be available to the care provider from the monitor.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K091050: 506CN Patient Monitor.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 4, 2026. https://510kreport.com/device/K091050

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