IntelliSpace Event Management 11.03Recalls & reported problems
Philips Medical Systems Hsg · Class 2
Data updated Oct 18, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 6
- Deaths reported
- 3
- Injuries reported
- 2
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 6 adverse event reports that list this exact device (DI 00884838031746), received between Jan 24, 2018 and May 30, 2024 — classified as 3 deaths, 2 injuries, 1 malfunction.
The most frequently reported specific device problem is “Defective Alarm” (2 reports).
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.
Reports received per month
Most reported problems
Device problems
- Defective Alarm2
- Delayed Alarm2
- Adverse Event Without Identified Device or Use Problem1
- Communication or Transmission Problem1
- Improper or Incorrect Procedure or Method1
Patient problems
- Asystole2
- Death2
- Cardiac Arrest1
- No Clinical Signs, Symptoms or Conditions1
- No Known Impact Or Consequence To Patient1
Recent adverse event reports
The 6 most recent of 6 reports, in the reporter's own words as published by the FDA.
MalfunctionMay 30, 2024Defective Alarm; Communication or Transmission Problem; Defective Alarm; Communication or Transmission Problem
THE CUSTOMER REPORTED THAT THERE WAS NO RED ALARM ON CENTRAL MONITORING. IT IS UNKNOWN IF THE DEVICE WAS IN USE AT TIME OF EVENT, AND THERE WAS NO ADVERSE EVENT REPORTED.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 19425278 ↗InjurySep 12, 2022Delayed Alarm; Delayed Alarm
IT WAS REPORTED THAT THERE WAS A DELAY IN RECEIVING THE ALERT FOR AN ASYSTOLE ALARM FROM THE INTELLISPACE EVENT MANAGEMENT (IEM) SYSTEM AND, AS A RESULT, THE PATIENT HAD EXPERIENCED AN ADVERSE EVENT AND IT WAS NECESSARY TO TRANSFER THE PATIENT TO THE INTENSIVE CARE UNIT (ICU).
Patient problems: Asystole
MAUDE report 15403156 ↗DeathFeb 24, 2022Improper or Incorrect Procedure or Method; Improper or Incorrect Procedure or Method
HOLD SMP 2.24IT WAS REPORTED THAT ALARMS WERE NOT PAGED FOR BED 09B ON (B)(6) 2022 BETWEEN 06:45 AND 19:00 RESULTING IN A PATIENT DEATH.
Patient problems: Asystole
MAUDE report 13591204 ↗DeathSep 26, 2019Adverse Event Without Identified Device or Use Problem
THE CUSTOMER REPORTED THAT THEY NEED ACTIVITY LOG FOR (B)(6) 2019 AT 10:06AM FOR BED RM 334 TELE-V-FIB/TACH, DUE TO A RECENT PAGING ISSUE RELATED TO TELEMETRY ALERTS WITH THE EMERGIN (IEM) PAGING SYSTEM (PART 865206). THE SITE RELIES ON THE PHILIPS IEM PAGING AND VOCERA PHONE SYSTEM FOR PRIMARY ALERTS. THE PATIENT HAD A CARDIAC ARREST AND DIED.
Patient problems: Cardiac Arrest; Death
MAUDE report 9125090 ↗InjuryJun 11, 2019Delayed Alarm
THE CUSTOMER REPORTED THAT ROOM 306 ALERTED A VTACH ON (B)(6) 2019 AT 9:47:03. THERE WAS A DELAY OF ALARMS VIA THE PAGING SYSTEM. NO INFORMATION WAS RECEIVED INDICATING THE DEVICE WAS NOT A CONTRIBUTING FACTOR IN THE EVENT. THE TYPE OF ADVERSE EVENT WAS NOT PROVIDED AT THE TIME OF THIS REPORT.
Patient problems: No Known Impact Or Consequence To Patient
MAUDE report 8686332 ↗DeathJan 24, 2018Defective Alarm
THE CUSTOMER REPORTED THAT ON (B)(6) 2018, AS ALARMING STOPPED THROUGH THE PAGING (IEM) SYSTEM AT 10:17AM. THE PATIENT LEADS OFF OF TELEMETRY STARTING HAPPENING AT 17:30PM, AND NO IEM LEADS OFF ALERTS WERE RECEIVED. AT 19:00, THEY FOUND THE PATIENT IN ROOM 335 IN 3 SOUTH EXPIRED. THE PATIENT DIED.
Patient problems: Death
MAUDE report 7215509 ↗
Other SYSTEM,NETWORK AND COMMUNICATION,PHYSIOLOGICAL MONITORS devices
- Xhibit Xhibit CentralSpacelabs Healthcare (Washington), Inc · System, network and communication, physiological monitors3 deaths218 reports
- Infinity M540 MS26372Draeger Medical Systems, Inc. · System,Network And Communication,Physiological Monitors2 recalls9 reports
- CareEventPhilips Medical Systems Hsg · System, network and communication, physiological monitors2 recalls4 deaths7 reports
- XTR 96280Spacelabs Healthcare (Washington), Inc · SYSTEM,NETWORK AND COMMUNICATION,PHYSIOLOGICAL MONITORS2 recalls0 reports
- CNS-2101 Central MonitorNihon Kohden Corporation · System, Network And Communication, Physiological Monitors3 deaths76 reports
- BeneVision Central Monitoring SystemShenzhen Mindray Bio-Medical Electronics Co., Ltd. · System, Network And Communication, Physiological Monitors1 recall2 deaths5 reports
- eCareManager 4.5Visicu, Inc. · System, network and communication, physiological monitors1 recall1 death1 report
- eCareManager 4.6Visicu, Inc. · System, network and communication, physiological monitors1 recall0 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 18, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page