Devices › Implantable pulse generator, pacemaker (non-crt)
Device brand name · Implantable pulse generator pacemaker non-crt
Reply 200: medical device reports filed with FDA
270 reports name it, 2013–2021. Manufacturer given most often on reports: Sorin Group Italia - Crm Facility. Product code LWP.
- 270
- device reports naming the brand
- 0% of all MAUDE reports · about 21 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 98.1%
- classified as malfunction
- 41.5% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
270 medical device reports received by FDA name the brand "Reply 200" (implantable pulse generator pacemaker non-crt); the manufacturer given most often on reports is Sorin Group Italia - Crm Facility; received from October 2013 to December 2021. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
0 reports arrived in the 12 months to August 2026, and none 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 (98.1%) and injury (1.9%); 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 over-sensing (11.9%), no pacing (11.1%) and pacemaker found in back-up mode (10.4%). The patient problems coded most often are no patient involvement, bradycardia and syncope. 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 |
|---|---|---|---|
| Over-sensing | 32 | 11.9% | 8.4% |
| No pacing | 30 | 11.1% | 0.6% |
| Pacemaker found in back-up mode | 28 | 10.4% | 3.2% |
| High impedance | 20 | 7.4% | 9% |
| Connection problema connection problem | 17 | 6.3% | 1.6% |
| Display or visual feedback problem | 9 | 3.3% | 0.1% |
| Pacing inadequately | 8 | 3% | 0.1% |
| Data problem | 6 | 2.2% | 0.8% |
| Premature discharge of battery | 6 | 2.2% | 22.3% |
| Device operates differently than expectedthe device behaved unexpectedly | 5 | 1.9% | 2.9% |
| Failure to capture | 5 | 1.9% | 5.3% |
| High capture threshold | 5 | 1.9% | 2.6% |
| Failure to sense | 4 | 1.5% | 0.2% |
| Loose or intermittent connection | 4 | 1.5% | 0.3% |
| Pacing problem | 4 | 1.5% | 5.6% |
| Decoupling | 3 | 1.1% | 0% |
| Device operational issue | 3 | 1.1% | 0% |
| Low impedance | 3 | 1.1% | 2% |
| Application interface becomes non-functional or program exits abnormally | 2 | 0.7% | 0% |
| Battery problema problem with the battery | 2 | 0.7% | 3.4% |
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 | 20 | 7.4% |
| Bradycardiaslow heart rate | 16 | 5.9% |
| Syncopefainting | 9 | 3.3% |
| Dizzinesslight-headedness or unsteadiness | 4 | 1.5% |
| Chest painchest pain | 3 | 1.1% |
| Deaththe patient died; cause not stated by this term | 3 | 1.1% |
| Discomfortdiscomfort | 3 | 1.1% |
| Loss of consciousnesspassing out | 3 | 1.1% |
| Muscle stimulation | 3 | 1.1% |
| Not applicable | 3 | 1.1% |
| Atrial fibrillationan irregular heart rhythm | 2 | 0.7% |
| Dyspneashortness of breath | 2 | 0.7% |
| Fatiguetiredness | 2 | 0.7% |
| Necrosisdeath of tissue | 2 | 0.7% |
| Palpitationsawareness of the heartbeat | 2 | 0.7% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Reply 200 | Product code LWP | All MAUDE reports |
|---|---|---|---|
| Reports | 270 | 157,494 | 26,136,888 |
| Share of that pool | — | 0.2% | 0% |
| Classified as death, per 1,000 reports | 0 | 12 | 9 |
| Classified as injury | 1.9% | 57.3% | 36.2% |
| Classified as malfunction | 98.1% | 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 Reply 200 reports
How many FDA reports name Reply 200?
270 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
malfunction (98.1%) and injury (1.9%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
over-sensing (11.9%), no pacing (11.1%), pacemaker found in back-up mode (10.4%), high impedance (7.4%) and connection problem (6.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 Reply 200 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.