Devices › Detector and alarm, arrhythmia
Device brand name · Mx40 1 4 ghz smart hopping
MX40 1.4 GHz Smart Hopping: medical device reports filed with FDA
5,135 reports name it, 2012–2026. Manufacturer given most often on reports: Philips Medical Systems. Product code DSI.
- 5,135
- device reports naming the brand
- 0% of all MAUDE reports · about 356 a year
- 6
- reports, 12 months to August 2026
- 209 in the 12 months before
- 98.2%
- classified as malfunction
- 90.5% across the product code
- 1.3%
- classified as death, as reported
- 67 reports · not verified by FDA
FDA's MAUDE database holds 5,135 reports that name the brand "MX40 1.4 GHz Smart Hopping" (mx40 1 4 ghz smart hopping), received between February 2012 and August 2026; the manufacturer given most often on reports is Philips Medical Systems. Spellings of one product vary from report to report.
6 reports arrived in the 12 months to August 2026, down 97% from 209 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 (98.2%), death (1.3%) and injury (0.5%); across all detector and alarm, arrhythmia reports (product code DSI) death is recorded in 1.5% and malfunction in 90.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are no audible alarm (46.5%), no audible prompt/feedback (18.1%) and device operates differently than expected (8.1%). 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 33,398 reports carrying product code DSI. 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 | 2,387 | 46.5% | 11.1% |
| No audible prompt/feedback | 932 | 18.1% | 4.5% |
| Device operates differently than expectedthe device behaved unexpectedly | 418 | 8.1% | 2.9% |
| No device output | 315 | 6.1% | 1.3% |
| Device displays incorrect message | 277 | 5.4% | 1.5% |
| Inaudible or unclear audible prompt/feedback | 192 | 3.7% | 0.7% |
| Device alarm system | 136 | 2.6% | 2.9% |
| Device inoperablethe device could not be used | 69 | 1.3% | 0.5% |
| Defective devicethe device was defective | 67 | 1.3% | 0.4% |
| Component missing | 63 | 1.2% | 0.2% |
| Mechanical problema mechanical problem | 52 | 1% | 0.3% |
| Defective alarm | 49 | 1% | 0.7% |
| Defective component | 48 | 0.9% | 0.2% |
| Breakthe device broke | 42 | 0.8% | 0.2% |
| Communication or transmission problemthe device could not communicate or transmit | 36 | 0.7% | 3.3% |
| Output problem | 30 | 0.6% | 0.4% |
| Audible prompt/feedback problem | 28 | 0.5% | 0.1% |
| Low audible alarm | 22 | 0.4% | 0.1% |
| Alarm not visible | 20 | 0.4% | 0.1% |
| Display or visual feedback problem | 19 | 0.4% | 0.3% |
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 | 1,580 | 30.8% |
| Deaththe patient died; cause not stated by this term | 35 | 0.7% |
| Cardiac arrestthe heart stopped | 18 | 0.4% |
| Low oxygen saturation | 5 | 0.1% |
| Asystole | 4 | 0.1% |
| Bradycardiaslow heart rate | 3 | 0.1% |
| Cardiopulmonary arrest | 3 | 0.1% |
| Injurya physical injury | 3 | 0.1% |
| Elevated ketones/ diabetic ketoacidosis | 2 | 0% |
| Loss of consciousnesspassing out | 2 | 0% |
| Abnormal scarring | 1 | 0% |
| Arrhythmia | 1 | 0% |
| Atrial fibrillationan irregular heart rhythm | 1 | 0% |
| Burn(s)a burn | 1 | 0% |
| Burn, thermal | 1 | 0% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | MX40 1.4 GHz Smart Hopping | Product code DSI | All MAUDE reports |
|---|---|---|---|
| Reports | 5,135 | 33,398 | 26,136,888 |
| Share of that pool | — | 15.4% | 0% |
| Classified as death, per 1,000 reports | 13 | 15 | 9 |
| Classified as injury | 0.5% | 7.8% | 36.2% |
| Classified as malfunction | 98.2% | 90.5% | 62.3% |
| Filed by the manufacturer | 100% | 99.3% | 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 DSI
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Reveal LINQ | 19,184 | 264 | 0% |
| Reveal Xt | 2,037 | 0 | 0.1% |
| Mx40 2 4 Ghz Smart Hopping | 785 | 0 | 1.5% |
| Reveal Dx | 730 | 0 | 0.4% |
| Acuity Central Monitoring | 710 | 0 | 0% |
| Mp70 Intellivue Patient Monitor | 682 | 0 | 15.4% |
| IntelliVue Multi Measurement Server X2 | 1,924 | 135 | 1.7% |
| Intellivue Mx40 802 11a/B/G | 329 | 0 | 3% |
| Spacelabs Ultraview Sl Command Module | 200 | 4 | 8.5% |
| IntelliVue MX800 patient monitor | 502 | 54 | 10.6% |
| Patient Connector | 207 | 83 | 0% |
| IntelliVue MX40 2.4GHz | 192 | 56 | 6.8% |
| Passport 2 Monitor | 469 | 0 | 0.2% |
| IntelliVue MP5 | 261 | 73 | 10.7% |
| Zio AT | 711 | 90 | 3.5% |
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 MX40 1.4 GHz Smart Hopping reports
How many FDA reports name MX40 1.4 GHz Smart Hopping?
5,135 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 6 in the latest 12 months.
What kinds of events are reported?
malfunction (98.2%), death (1.3%) and injury (0.5%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
no audible alarm (46.5%), no audible prompt/feedback (18.1%), device operates differently than expected (8.1%), no device output (6.1%) and device displays incorrect message (5.4%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that MX40 1.4 GHz Smart Hopping 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.