510(k) Report

510(k) · Cleared

Recalled · Class II · 2024

CareEvent inclusive of the CareEvent Mobile Application accessory

K161164510(k) TraditionalCleared Jun 24, 201660-day reviewClass II21 CFR 870.2300Recalls 3

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

Philips Medical Systems · MSX System, Network And Communication, Physiological Monitors

Cleared on Jun 24, 2016 as substantially equivalent to K142935 (Philips Medical Systems, 2015) after a 60-day review. Its family tree reaches back 7 generations to 1997. It has been recalled 3 times.

Decided
Jun 24, 2016
Review
60 days
Class
Class II
Product code
MSX
Recalls
3
Predicates
1

Its longest line of descent runs back 7 generations to K962827 (1997). 9 ancestors in all, the oldest K945277 (1995). No later device cites it as a predicate yet.

  1. Root · 7 generations backK962827 Alarm Display Unit/Pager-Lan System (Adu)Marquette Electronics, Inc. · 1997
  2. 6 generations backK971868 Impact (Informing Mobile Personnel and Care Tracking) Pager SystemMarquette Electronics, Inc. · 1997
  3. 5 generations backK973527 Cardio-Pager SystemData Critical Corp. · 1998
  4. 4 generations backK992749 Ultraview Waveform Pager System, Model 91841Spacelabs Medical, Inc. · 2000
  5. 3 generations backK062278 Spacelabs Medical Clinical Event Interface, Model 91847Spacelabs Medical, Inc. · 2006
  6. 2 generations backK102974 Intellisphere Event Managment System Rel. 10.00Philips Medical Systems · 2011
  7. 1 generation backK142935 CareEventPhilips Medical Systems · 2015
  8. This deviceK161164 CareEvent inclusive of the CareEvent Mobile Application accessoryPhilips Medical Systems · 2016
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−7K962827Alarm Display Unit/Pager-Lan System (Adu)Marquette Electronics, Inc.1997—
−6K971868Impact (Informing Mobile Personnel and Care Tracking) Pager SystemMarquette Electronics, Inc.1997—
−5K973527Cardio-Pager SystemData Critical Corp.1998—
−4K992749Ultraview Waveform Pager System, Model 91841Spacelabs Medical, Inc.2000—
−3K062278Spacelabs Medical Clinical Event Interface, Model 91847Spacelabs Medical, Inc.2006—
−2K102974Intellisphere Event Managment System Rel. 10.00Philips Medical Systems2011—
−1K142935CareEventPhilips Medical Systems2015—
0 (this device)K161164CareEvent inclusive of the CareEvent Mobile Application accessoryPhilips Medical Systems2016—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
199510
200610
FIG. 1 — Lineage of K161164, 1997–2016Source: 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
*K142935CareEvent
Summary page 4
…6310, I OUG Medical Device Data System III. Predicate device information Trade name: CareEvent Manufacturer: Philips Medical Systems 510(k) clearance: K142935 Classification name Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Device class: Class I…
Philips Medical Systems2015—

What descends from it?

No later submission names this one as a predicate yet.

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

Recalls of this device

DateClassRecallRoot causeReason
Feb 28, 2024Class IIZ-1387-2024Under Investigation by firmIt was found that the Care Assist mobile application (version 4.1.1 and earlier) would not play custom ringtones when iOS device screens were locked with a passcode.
Nov 28, 2023Class IIZ-0731-2024Software designPush notifications may fail to send to the user under certain conditions. This could potentially result in patient harm due to delay in detection of a change in patient condition.
Nov 28, 2023Class IIZ-0732-2024Software designPush notifications may fail to send to the user under certain conditions. This could potentially result in patient harm due to delay in detection of a change in patient condition.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 19 years and passes through 4 companies; a new generation was cleared every 1.8 years on median.
  • None of the 9 ancestors has a recall.

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. 2016, this device’s year, is highlighted.

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 intended use of Philips CareEvent is to deliver supplemental medical device data associated with physiological alarms, technical alarms, clinical notifications, nurse call alarms and informational messages to a healthcare professional’s end device. The user may receive visual or audible notifications, and/or other message notification types based on the communicator in use. Philips CareEvent is a component of a distributed alarming system. It does…

Read the full statement (173 words)

The intended use of Philips CareEvent is to deliver supplemental medical device data associated with physiological alarms, technical alarms, clinical notifications, nurse call alarms and informational messages to a healthcare professional’s end device. The user may receive visual or audible notifications, and/or other message notification types based on the communicator in use.

Philips CareEvent is a component of a distributed alarming system. It does not generate the alarm, alter the behavior of the alarm-generating system, replace the alarming system that generates the alarms, nor is it intended to provide real-time information, therefore the device producing the alarm or event remains the primary notification system. Philips CareEvent provides confirmed delivery features when it is used with the Philips CareEvent mobile application on Philips-approved devices. The Philips CareEvent mobile application either communicates alarm information that is sent from the Philips CareEvent server, or the user is notified that communication is not possible. Receipt of alarm messages or events by all other external devices is not confirmed and delivery to the end device is not guaranteed.

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. “K161164: CareEvent inclusive of the CareEvent Mobile Application accessory.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K161164

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