Reported Reactions

Devices › Permanent pacemaker electrode

Device brand name · Permanent pacemaker electrode

Screw-In Lead: medical device reports filed with FDA

1,191 reports name it, 2015–2026. Manufacturer given most often on reports: Mpri. Product code DTB.

1,191
device reports naming the brand
0% of all MAUDE reports · about 106 a year
163
reports, 12 months to August 2026
189 in the 12 months before
36.1%
classified as malfunction
43.9% across the product code
0.6%
classified as death, as reported
7 reports · not verified by FDA

1,191 medical device reports received by FDA name the brand "Screw-In Lead" (permanent pacemaker electrode); the manufacturer given most often on reports is Mpri; received from April 2015 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.

163 reports arrived in the 12 months to August 2026, down 14% from 189 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 injury (63.3%), malfunction (36.1%) and death (0.6%); 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 high capture threshold (42.9%), failure to capture (15.1%) and low impedance (11.1%). The patient problems coded most often are bradycardia, syncope/fainting and device overstimulation of tissue. 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

01224Sep 2021: 8Oct 2021: 7Nov 2021: 16Dec 2021: 82022Jan 2022: 13Feb 2022: 20Mar 2022: 4Apr 2022: 13May 2022: 4Jun 2022: 13Jul 2022: 9Aug 2022: 12Sep 2022: 17Oct 2022: 16Nov 2022: 10Dec 2022: 112023Jan 2023: 13Feb 2023: 9Mar 2023: 22Apr 2023: 10May 2023: 23Jun 2023: 9Jul 2023: 7Aug 2023: 15Sep 2023: 15Oct 2023: 23Nov 2023: 15Dec 2023: 142024Jan 2024: 12Feb 2024: 6Mar 2024: 14Apr 2024: 14May 2024: 8Jun 2024: 9Jul 2024: 12Aug 2024: 13Sep 2024: 22Oct 2024: 14Nov 2024: 23Dec 2024: 182025Jan 2025: 14Feb 2025: 16Mar 2025: 15Apr 2025: 24May 2025: 9Jun 2025: 12Jul 2025: 10Aug 2025: 12Sep 2025: 12Oct 2025: 15Nov 2025: 10Dec 2025: 142026Jan 2026: 10Feb 2026: 8Mar 2026: 12Apr 2026: 22May 2026: 15Jun 2026: 15Jul 2026: 14Aug 2026: 16

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

0881752015: 420152017: 52018: 820182019: 1012020: 15120202021: 1652022: 14220222023: 1752024: 16520242025: 1632026: 1122026

Event type and report source

Event type, as classified on the report

Death0.6%7
Injury63.3%754
Malfunction36.1%430
Other0%0
Not given0%0

Who filed the report

Manufacturer report99.9%1,190
Voluntary report0.1%1
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
High capture threshold51142.9%12.3%
Failure to capture18015.1%9.7%
Low impedance13211.1%5.3%
High impedance12710.7%10.7%
Over-sensing1038.6%13.2%
Capturing problem988.2%4.2%
Impedance problem877.3%4.3%
Fracturea broken bone655.5%4.8%
Under-sensing453.8%17.1%
Signal artifact/noise423.5%5.2%
Pacing problem373.1%5%
Intermittent capture352.9%1.4%
Electrical /electronic property probleman electrical or electronic problem312.6%2.1%
Unstable capture threshold292.4%1.4%
Breakthe device broke121%1.8%
Decreased sensitivity121%2.4%
Device dislodged or dislocated70.6%9.1%
Device sensing problem60.5%1.9%
Connection problema connection problem40.3%0.2%
Positioning problem40.3%2.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)ReportsShare
Bradycardiaslow heart rate252.1%
Syncope/fainting252.1%
Device overstimulation of tissue191.6%
Dyspneashortness of breath151.3%
Erosion151.3%
Bacterial infectiona bacterial infection131.1%
Erythemaskin redness110.9%
Medical device site infectioninfection at the device site110.9%
Discomfortdiscomfort100.8%
Purulent discharge100.8%
Chest painchest pain90.8%
Heart failure/congestive heart failure80.7%
Fever70.6%
Hematomaa collection of blood under the skin or in tissue70.6%
Painpain, site not specified70.6%

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

In context

MeasureScrew-In LeadProduct code DTBAll MAUDE reports
Reports1,191327,31726,136,888
Share of that pool—0.4%0%
Classified as death, per 1,000 reports6299
Classified as injury63.3%53.1%36.2%
Classified as malfunction36.1%43.9%62.3%
Filed by the manufacturer99.9%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%
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%

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 Screw-In Lead reports

How many FDA reports name Screw-In Lead?

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

What kinds of events are reported?

injury (63.3%), malfunction (36.1%) and death (0.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

high capture threshold (42.9%), failure to capture (15.1%), low impedance (11.1%), high impedance (10.7%) and over-sensing (8.6%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (99.9%) and voluntary 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 Screw-In Lead 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.