Reported Reactions

Devices › Permanent pacemaker electrode

Device brand name · Permanent pacemaker electrode

CapSure Sense Lead MRI SureScan: medical device reports filed with FDA

8,774 reports name it, 2012–2026. Manufacturer given most often on reports: Mpri. Product code DTB.

8,774
device reports naming the brand
0% of all MAUDE reports · about 616 a year
1,337
reports, 12 months to August 2026
1,382 in the 12 months before
51.9%
classified as malfunction
43.9% across the product code
1%
classified as death, as reported
89 reports · not verified by FDA

8,774 medical device reports received by FDA name the brand "CapSure Sense Lead MRI SureScan" (permanent pacemaker electrode); the manufacturer given most often on reports is Mpri; received from April 2012 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.

1,337 reports arrived in the 12 months to August 2026, close to the 1,382 of 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 (51.9%), injury (47%) and death (1%); across all permanent pacemaker electrode reports (product code DTB) death is recorded in 2.9% and malfunction in 43.9%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are under-sensing (26.5%), high capture threshold (25.5%) and device dislodged or dislocated (11.3%). The patient problems coded most often are bradycardia, dizziness and syncope/fainting. 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

087174Sep 2021: 91Oct 2021: 59Nov 2021: 81Dec 2021: 742022Jan 2022: 83Feb 2022: 59Mar 2022: 75Apr 2022: 74May 2022: 94Jun 2022: 83Jul 2022: 110Aug 2022: 79Sep 2022: 98Oct 2022: 100Nov 2022: 105Dec 2022: 862023Jan 2023: 124Feb 2023: 113Mar 2023: 113Apr 2023: 105May 2023: 127Jun 2023: 128Jul 2023: 139Aug 2023: 140Sep 2023: 150Oct 2023: 144Nov 2023: 174Dec 2023: 862024Jan 2024: 107Feb 2024: 102Mar 2024: 125Apr 2024: 115May 2024: 106Jun 2024: 88Jul 2024: 105Aug 2024: 101Sep 2024: 87Oct 2024: 119Nov 2024: 137Dec 2024: 1022025Jan 2025: 125Feb 2025: 114Mar 2025: 89Apr 2025: 133May 2025: 132Jun 2025: 109Jul 2025: 128Aug 2025: 107Sep 2025: 152Oct 2025: 111Nov 2025: 101Dec 2025: 1002026Jan 2026: 110Feb 2026: 98Mar 2026: 120Apr 2026: 112May 2026: 111Jun 2026: 117Jul 2026: 110Aug 2026: 95

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

07721,5432012: 320122015: 42016: 520162017: 62018: 1620182019: 6052020: 95920202021: 1,0192022: 1,04620222023: 1,5432024: 1,29420242025: 1,4012026: 8732026

Event type and report source

Event type, as classified on the report

Death1%89
Injury47%4,127
Malfunction51.9%4,558
Other0%0
Not given0%0

Who filed the report

Manufacturer report100%8,774
Voluntary report0%0
User facility report0%0
Distributor report0%0
Not given0%0

Grey bar: all 327,317 reports carrying product code DTB. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Under-sensing2,32426.5%17.1%
High capture threshold2,24125.5%12.3%
Device dislodged or dislocated98911.3%9.1%
High impedance8649.8%10.7%
Failure to capture8159.3%9.7%
Over-sensing8049.2%13.2%
Pacing problem6557.5%5%
Capturing problem6107%4.2%
Impedance problem5386.1%4.3%
Decreased sensitivity3844.4%2.4%
Positioning problem3734.3%2.2%
Electrical /electronic property probleman electrical or electronic problem3474%2.1%
Unstable capture threshold2933.3%1.4%
Signal artifact/noise2763.1%5.2%
Fracturea broken bone2613%4.8%
Low impedance1792%5.3%
Intermittent capture1661.9%1.4%
Breakthe device broke1421.6%1.8%
Device sensing problem1391.6%1.9%
Material integrity problema problem with the device material410.5%1.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)ReportsShare
Bradycardiaslow heart rate1531.7%
Dizzinesslight-headedness or unsteadiness1441.6%
Syncope/fainting1341.5%
Chest painchest pain1111.3%
Dyspneashortness of breath1021.2%
Erosion991.1%
Pocket erosion951.1%
Erythemaskin redness941.1%
Arrhythmia891%
Discomfortdiscomfort851%
Swelling/ edema700.8%
Bacterial infectiona bacterial infection680.8%
Medical device site infectioninfection at the device site650.7%
Painpain, site not specified640.7%
Falla fall530.6%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

MeasureCapSure Sense Lead MRI SureScanProduct code DTBAll MAUDE reports
Reports8,774327,31726,136,888
Share of that pool—2.7%0%
Classified as death, per 1,000 reports10299
Classified as injury47%53.1%36.2%
Classified as malfunction51.9%43.9%62.3%
Filed by the manufacturer100%96.8%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 DTB

BrandReportsLatest 12 monthsClassified as death
CapSureFix Novus Lead MRI SureScan108,10317,5541%
Capsurefix Novus57,53846.8%
CapSureFix Novus MRI SureScan18,9093,2431.3%
CapSure SP8,2232263.9%
Capsurefix7,28406.3%
Permanent Pacemaker Electrode5,0413320.4%
Capsure Sp Novus4,80309.5%
Capsure Sense4,74006.4%
Flextend6,8362030.7%
Attain Otw7,77309.1%
Tendril Sdx8,31632.3%
CapSure Epicardial Lead4,8427601.5%
Tendril Sts54,0364,3203.1%
CapSure SP Novus Lead2,7153311.1%
Tendril St20,1565475.2%

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 CapSure Sense Lead MRI SureScan reports

How many FDA reports name CapSure Sense Lead MRI SureScan?

8,774 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 1,337 in the latest 12 months.

What kinds of events are reported?

malfunction (51.9%), injury (47%) and death (1%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

under-sensing (26.5%), high capture threshold (25.5%), device dislodged or dislocated (11.3%), high impedance (9.8%) and failure to capture (9.3%). 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 CapSure Sense Lead MRI SureScan 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.