Devices › Detector and alarm, arrhythmia
Device brand name · Detector and alarm arrhythmia
Patient Connector: medical device reports filed with FDA
207 reports name it, 2020–2026. Manufacturer given most often on reports: Medtronic. Product code DSI.
- 207
- device reports naming the brand
- 0% of all MAUDE reports · about 33 a year
- 83
- reports, 12 months to August 2026
- 67 in the 12 months before
- 96.1%
- classified as malfunction
- 90.5% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
207 medical device reports received by FDA name the brand "Patient Connector" (detector and alarm arrhythmia); the manufacturer given most often on reports is Medtronic; received from April 2020 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
83 reports arrived in the 12 months to August 2026, up 24% from 67 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 (96.1%) and injury (3.9%); 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 communication or transmission problem (84.1%), display or visual feedback problem (10.6%) and output problem (10.6%). The patient problems coded most often are asystole, heart block and arrhythmia. 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 |
|---|---|---|---|
| Communication or transmission problemthe device could not communicate or transmit | 174 | 84.1% | 3.3% |
| Display or visual feedback problem | 22 | 10.6% | 0.3% |
| Output problem | 22 | 10.6% | 0.4% |
| Computer software problema software problem | 14 | 6.8% | 0.1% |
| Computer operating system problem | 12 | 5.8% | 0.4% |
| Unexpected shutdown | 9 | 4.3% | 0% |
| Device difficult to program or calibrate | 8 | 3.9% | 0.2% |
| Battery problema problem with the battery | 7 | 3.4% | 1.2% |
| Failure to interrogate | 7 | 3.4% | 2.1% |
| Data problem | 6 | 2.9% | 0.5% |
| Inadequate user interface | 6 | 2.9% | 0% |
| Problem with software installation | 4 | 1.9% | 0% |
| Application program freezes or fails to launch | 2 | 1% | 0% |
| Capturing problem | 1 | 0.5% | 0% |
| Device sensing problem | 1 | 0.5% | 4.8% |
| Electrical /electronic property probleman electrical or electronic problem | 1 | 0.5% | 0.1% |
| Electromagnetic interference | 1 | 0.5% | 1.3% |
| High capture threshold | 1 | 0.5% | 0% |
| Material integrity problema problem with the device material | 1 | 0.5% | 0% |
| Premature discharge of battery | 1 | 0.5% | 10.2% |
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 |
|---|---|---|
| Asystole | 2 | 1% |
| Heart block | 2 | 1% |
| Arrhythmia | 1 | 0.5% |
| Bradycardiaslow heart rate | 1 | 0.5% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Patient Connector | Product code DSI | All MAUDE reports |
|---|---|---|---|
| Reports | 207 | 33,398 | 26,136,888 |
| Share of that pool | — | 0.6% | 0% |
| Classified as death, per 1,000 reports | 0 | 15 | 9 |
| Classified as injury | 3.9% | 7.8% | 36.2% |
| Classified as malfunction | 96.1% | 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% |
| MX40 1.4 GHz Smart Hopping | 5,135 | 6 | 1.3% |
| 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% |
| 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 Patient Connector reports
How many FDA reports name Patient Connector?
207 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 83 in the latest 12 months.
What kinds of events are reported?
malfunction (96.1%) and injury (3.9%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
communication or transmission problem (84.1%), display or visual feedback problem (10.6%), output problem (10.6%), computer software problem (6.8%) and computer operating system problem (5.8%). 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 Patient Connector 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.