Devices › Monitor, physiological, patient(with arrhythmia detection or alarms)
Device brand name · Intellivue mx450 patient monitor
IntelliVue MX450 Patient Monitor: medical device reports filed with FDA
448 reports name it, 2014–2026. Manufacturer given most often on reports: Philips Medizin Systeme B Blingen. Product code MHX.
- 448
- device reports naming the brand
- 0% of all MAUDE reports · about 37 a year
- 123
- reports, 12 months to August 2026
- 72 in the 12 months before
- 84.8%
- classified as malfunction
- 82.1% across the product code
- 7.6%
- classified as death, as reported
- 34 reports · not verified by FDA
448 medical device reports received by FDA name the brand "IntelliVue MX450 Patient Monitor" (intellivue mx450 patient monitor); the manufacturer given most often on reports is Philips Medizin Systeme B Blingen; received from June 2014 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
123 reports arrived in the 12 months to August 2026, up 71% from 72 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are malfunction (84.8%), death (7.6%) and injury (7.6%); across all monitor, physiological, patient(with arrhythmia detection or alarms) reports (product code MHX) death is recorded in 5.9% and malfunction in 82.1%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are no audible alarm (35.9%), defective alarm (13.8%) and no audible prompt/feedback (12.7%). The patient problems coded most often are no patient involvement, death and cardiac arrest. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 32,636 reports carrying product code MHX. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| No audible alarm | 161 | 35.9% | 11.5% |
| Defective alarm | 62 | 13.8% | 3.4% |
| No audible prompt/feedback | 57 | 12.7% | 3.5% |
| Device alarm system | 27 | 6% | 8.1% |
| Incorrect measurementthe device measured wrongly | 21 | 4.7% | 1.7% |
| Device displays incorrect message | 11 | 2.5% | 4.3% |
| Application program freezes or fails to launch | 10 | 2.2% | 1.5% |
| Incorrect, inadequate or imprecise result or readings | 8 | 1.8% | 1.2% |
| Therapeutic or diagnostic output failure | 8 | 1.8% | 0.5% |
| Device operates differently than expectedthe device behaved unexpectedly | 7 | 1.6% | 9.3% |
| Excessive heating | 6 | 1.3% | 0.1% |
| Audible prompt/feedback problem | 5 | 1.1% | 0.3% |
| Defective component | 5 | 1.1% | 0.5% |
| Display or visual feedback problem | 5 | 1.1% | 3.2% |
| No device output | 5 | 1.1% | 1% |
| Unable to obtain readings | 5 | 1.1% | 2.3% |
| Alarm not visible | 4 | 0.9% | 0.6% |
| Device fell | 4 | 0.9% | 0.3% |
| Low readingsreadings were too low | 4 | 0.9% | 0.4% |
| No display/image | 4 | 0.9% | 4.1% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| No patient involvement | 19 | 4.2% |
| Deaththe patient died; cause not stated by this term | 15 | 3.3% |
| Cardiac arrestthe heart stopped | 6 | 1.3% |
| Low oxygen saturation | 5 | 1.1% |
| Bradycardiaslow heart rate | 4 | 0.9% |
| Electric shockan electric shock | 3 | 0.7% |
| Asystole | 2 | 0.4% |
| Cardiopulmonary arrest | 2 | 0.4% |
| Hypoxialow oxygen | 2 | 0.4% |
| Injurya physical injury | 2 | 0.4% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 1 | 0.2% |
| Cyanosis | 1 | 0.2% |
| Heart failure | 1 | 0.2% |
| Pneumonialung infection | 1 | 0.2% |
| Sepsisa severe body-wide response to infection | 1 | 0.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | IntelliVue MX450 Patient Monitor | Product code MHX | All MAUDE reports |
|---|---|---|---|
| Reports | 448 | 32,636 | 26,136,888 |
| Share of that pool | — | 1.4% | 0% |
| Classified as death, per 1,000 reports | 76 | 59 | 9 |
| Classified as injury | 7.6% | 11.2% | 36.2% |
| Classified as malfunction | 84.8% | 82.1% | 62.3% |
| Filed by the manufacturer | 99.6% | 93.4% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code MHX
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Patient Information Center iX | 1,941 | 619 | 10.4% |
| uCor Heart Failure and Arrhythmia Management System | 1,877 | 762 | 0% |
| Tempus Pro | 1,850 | 108 | 0.5% |
| Cns-6201a | 1,720 | 0 | 0.8% |
| IntelliVue Multi Measurement Server X2 | 1,924 | 135 | 1.7% |
| Cns-6801a | 1,058 | 0 | 1.5% |
| Intellivue Information Center Ix | 952 | 0 | 7.5% |
| Intellivue X3 | 777 | 0 | 1.5% |
| Tempus Pro, Printer | 562 | 400 | 0% |
| Piic Ix Hardware | 538 | 0 | 4.6% |
| Xhibit Central Station | 492 | 154 | 0.8% |
| IntelliVue Multi-Measurement Module X3 | 478 | 401 | 1.7% |
| Pu-681ra | 437 | 222 | 1.4% |
| Cns-9700a | 393 | 0 | 0.3% |
| Arrhythmia Management System | 381 | 4 | 0% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about IntelliVue MX450 Patient Monitor reports
How many FDA reports name IntelliVue MX450 Patient Monitor?
448 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 123 in the latest 12 months.
What kinds of events are reported?
malfunction (84.8%), death (7.6%) and injury (7.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
no audible alarm (35.9%), defective alarm (13.8%), no audible prompt/feedback (12.7%), device alarm system (6%) and incorrect measurement (4.7%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.6%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that IntelliVue MX450 Patient Monitor was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.