Devices › Implantable pulse generator, pacemaker (non-crt)
Device brand name · Implantable pulse generator pacemaker non-crt
Eno: medical device reports filed with FDA
430 reports name it, 2019–2026. Manufacturer given most often on reports: Microport Crm. Product code LWP.
- 430
- device reports naming the brand
- 0% of all MAUDE reports · about 59 a year
- 43
- reports, 12 months to August 2026
- 50 in the 12 months before
- 97.4%
- classified as malfunction
- 41.5% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 430 reports that name the brand "Eno" (implantable pulse generator pacemaker non-crt), received between March 2019 and August 2026; the manufacturer given most often on reports is Microport Crm. Spellings of one product vary from report to report.
43 reports arrived in the 12 months to August 2026, down 14% from 50 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 (97.4%) and injury (2.6%); across all implantable pulse generator, pacemaker (non-crt) reports (product code LWP) death is recorded in 1.2% and malfunction in 41.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are battery problem (20.5%), connection problem (15.3%) and pacing problem (5.6%). The patient problems coded most often are no patient involvement, 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
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 157,494 reports carrying product code LWP. 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 |
|---|---|---|---|
| Battery problema problem with the battery | 88 | 20.5% | 3.4% |
| Connection problema connection problem | 66 | 15.3% | 1.6% |
| Pacing problem | 24 | 5.6% | 5.6% |
| High impedance | 19 | 4.4% | 9% |
| No pacing | 15 | 3.5% | 0.6% |
| Over-sensing | 15 | 3.5% | 8.4% |
| Pacemaker found in back-up mode | 15 | 3.5% | 3.2% |
| Premature discharge of battery | 14 | 3.3% | 22.3% |
| Incomplete or inadequate connection | 13 | 3% | 0% |
| Pacing inadequately | 11 | 2.6% | 0.1% |
| Device markings/labelling problema problem with the device markings or label | 10 | 2.3% | 0% |
| Battery problem: high impedance | 9 | 2.1% | 0% |
| Failure to capture | 9 | 2.1% | 5.3% |
| High capture threshold | 9 | 2.1% | 2.6% |
| Display or visual feedback problem | 8 | 1.9% | 0.1% |
| Unexpected mode switch | 8 | 1.9% | 0.3% |
| Program or algorithm execution problem | 7 | 1.6% | 0% |
| Blocked connection | 6 | 1.4% | 0% |
| Capturing problem | 4 | 0.9% | 1.8% |
| Failure to interrogate | 4 | 0.9% | 1.8% |
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 | 10 | 2.3% |
| Dizzinesslight-headedness or unsteadiness | 9 | 2.1% |
| Syncope/fainting | 5 | 1.2% |
| Bacterial infectiona bacterial infection | 4 | 0.9% |
| Cardiac arrestthe heart stopped | 4 | 0.9% |
| Discomfortdiscomfort | 4 | 0.9% |
| Tachycardiafast heart rate | 4 | 0.9% |
| Bradycardiaslow heart rate | 3 | 0.7% |
| Pocket erosion | 3 | 0.7% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 2 | 0.5% |
| Cancer | 2 | 0.5% |
| Chest painchest pain | 2 | 0.5% |
| Fatiguetiredness | 2 | 0.5% |
| Itching sensation | 2 | 0.5% |
| Malaisegeneral feeling of being unwell | 2 | 0.5% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Eno | Product code LWP | All MAUDE reports |
|---|---|---|---|
| Reports | 430 | 157,494 | 26,136,888 |
| Share of that pool | — | 0.3% | 0% |
| Classified as death, per 1,000 reports | 0 | 12 | 9 |
| Classified as injury | 2.6% | 57.3% | 36.2% |
| Classified as malfunction | 97.4% | 41.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 LWP
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Assurity Mri | 18,995 | 2,035 | 1.8% |
| Teligen | 16,537 | 47 | 0.6% |
| Ingenio | 7,539 | 493 | 0.8% |
| Cognis | 8,694 | 6 | 1.5% |
| Ingevity | 9,039 | 299 | 0.9% |
| Accolade | 4,335 | 4 | 1.5% |
| Attain Otw | 7,773 | 0 | 9.1% |
| Energen | 5,237 | 0 | 0.6% |
| Energen Icd | 3,151 | 142 | 0.2% |
| ACUITY X4 Spiral S | 2,816 | 424 | 0.5% |
| ACUITY X4 Straight | 2,672 | 382 | 0.4% |
| Incepta Icd | 2,497 | 126 | 0.1% |
| Altrua | 4,122 | 0 | 2.4% |
| Incepta | 4,327 | 0 | 0.7% |
| Revo MRI SureScan | 1,996 | 12 | 2.9% |
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 Eno reports
How many FDA reports name Eno?
430 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 43 in the latest 12 months.
What kinds of events are reported?
malfunction (97.4%) and injury (2.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
battery problem (20.5%), connection problem (15.3%), pacing problem (5.6%), high impedance (4.4%) and no pacing (3.5%). 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 Eno 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.