Reported Reactions

Devices › Permanent pacemaker electrode

Device brand name · Permanent pacemaker electrode

Permanent Pacemaker Electrode: medical device reports filed with FDA

5,041 reports name it, 2020–2026. Manufacturer given most often on reports: Medtronic. Product code DTB.

5,041
device reports naming the brand
0% of all MAUDE reports · about 787 a year
332
reports, 12 months to August 2026
370 in the 12 months before
69.7%
classified as malfunction
43.9% across the product code
0.4%
classified as death, as reported
21 reports · not verified by FDA

FDA's MAUDE database holds 5,041 reports that name the brand "Permanent Pacemaker Electrode" (permanent pacemaker electrode), received between February 2020 and June 2026; the manufacturer given most often on reports is Medtronic. Spellings of one product vary from report to report.

332 reports arrived in the 12 months to August 2026, down 10% from 370 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 (69.7%), injury (29.8%) and death (0.4%); 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 insufficient device problem information (13.8%), signal artifact/noise (10.2%) and over-sensing (7.8%). The patient problems coded most often are foreign body in patient, failure of implant and pocket erosion. 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

01,9053,810Sep 2021: 0Oct 2021: 0Nov 2021: 0Dec 2021: 02022Jan 2022: 0Feb 2022: 0Mar 2022: 0Apr 2022: 0May 2022: 0Jun 2022: 0Jul 2022: 0Aug 2022: 0Sep 2022: 0Oct 2022: 0Nov 2022: 0Dec 2022: 02023Jan 2023: 0Feb 2023: 0Mar 2023: 0Apr 2023: 0May 2023: 0Jun 2023: 0Jul 2023: 50Aug 2023: 3,810Sep 2023: 36Oct 2023: 93Nov 2023: 2Dec 2023: 322024Jan 2024: 7Feb 2024: 63Mar 2024: 74Apr 2024: 20May 2024: 51Jun 2024: 53Jul 2024: 21Aug 2024: 23Sep 2024: 30Oct 2024: 0Nov 2024: 0Dec 2024: 292025Jan 2025: 38Feb 2025: 72Mar 2025: 51Apr 2025: 41May 2025: 43Jun 2025: 32Jul 2025: 34Aug 2025: 0Sep 2025: 23Oct 2025: 63Nov 2025: 35Dec 2025: 392026Jan 2026: 31Feb 2026: 36Mar 2026: 31Apr 2026: 22May 2026: 37Jun 2026: 15Jul 2026: 0Aug 2026: 0

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

02,0124,0232020: 420202023: 4,02320232024: 37120242025: 47120252026: 1722026

Event type and report source

Event type, as classified on the report

Death0.4%21
Injury29.8%1,504
Malfunction69.7%3,513
Other0.1%3
Not given0%0

Who filed the report

Manufacturer report0.1%4
Voluntary report99.9%5,037
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
Insufficient device problem information69513.8%1%
Signal artifact/noise51210.2%5.2%
Over-sensing3957.8%13.2%
Therapeutic or diagnostic output failure3136.2%0.1%
High impedance2855.7%10.7%
Impedance problem2855.7%4.3%
Under-sensing1763.5%17.1%
High capture threshold1593.2%12.3%
Failure to capture1452.9%9.7%
Low impedance1372.7%5.3%
Pacing problem1152.3%5%
Pacemaker found in back-up mode881.7%0%
Product quality problem881.7%0%
Device sensing problem821.6%1.9%
Fracturea broken bone801.6%4.8%
Device dislodged or dislocated731.4%9.1%
No pacing671.3%0.1%
High sensing threshold661.3%2.3%
Inappropriate/inadequate shock/stimulation621.2%0.3%
Output problem611.2%0%

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
Foreign body in patientpart of a device left in the patient2484.9%
Failure of implant2044%
Pocket erosion641.3%
Sepsisa severe body-wide response to infection621.2%
Syncope/fainting541.1%
Tachycardiafast heart rate420.8%
Shock from patient lead(s)380.8%
Arrhythmia330.7%
Atrial fibrillationan irregular heart rhythm330.7%
Dizzinesslight-headedness or unsteadiness280.6%
Appropriate clinical signs, symptoms and conditions term/code not available250.5%
Asystole240.5%
Endocarditis240.5%
Undesired nerve stimulation210.4%
Bradycardiaslow heart rate170.3%

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

In context

MeasurePermanent Pacemaker ElectrodeProduct code DTBAll MAUDE reports
Reports5,041327,31726,136,888
Share of that pool—1.5%0%
Classified as death, per 1,000 reports4299
Classified as injury29.8%53.1%36.2%
Classified as malfunction69.7%43.9%62.3%
Filed by the manufacturer0.1%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 Sense Lead MRI SureScan8,7741,3371%
CapSure SP8,2232263.9%
Capsurefix7,28406.3%
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 Permanent Pacemaker Electrode reports

How many FDA reports name Permanent Pacemaker Electrode?

5,041 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 332 in the latest 12 months.

What kinds of events are reported?

malfunction (69.7%), injury (29.8%) and death (0.4%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

insufficient device problem information (13.8%), signal artifact/noise (10.2%), over-sensing (7.8%), therapeutic or diagnostic output failure (6.2%) and high impedance (5.7%). These are FDA's device problem codes as entered on the report.

Who files these reports?

voluntary reports (99.9%) and manufacturer reports (0.1%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that Permanent Pacemaker Electrode 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.