Devices › Stimulator, autonomic nerve, implanted for epilepsy
Device brand name · Programming software
Programming Software: medical device reports filed with FDA
7,453 reports name it, 2007–2025. Manufacturer given most often on reports: Cyberonics. Product code LYJ.
- 7,453
- device reports naming the brand
- 0% of all MAUDE reports · about 386 a year
- 1
- reports, 12 months to August 2026
- 5 in the 12 months before
- 99.3%
- classified as malfunction
- 58.7% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
7,453 medical device reports received by FDA name the brand "Programming Software" (programming software); the manufacturer given most often on reports is Cyberonics; received from March 2007 to December 2025. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
1 reports arrived in the 12 months to August 2026, down 80% from 5 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 (99.3%) and injury (0.6%); across all stimulator, autonomic nerve, implanted for epilepsy reports (product code LYJ) death is recorded in 5.6% and malfunction in 58.7%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are use of incorrect control/treatment settings (14.4%), device operates differently than expected (10.8%) and no display/image (10.5%). The patient problems coded most often are no patient involvement, therapeutic response, decreased and seizures. 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 52,004 reports carrying product code LYJ. 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 |
|---|---|---|---|
| Use of incorrect control/treatment settings | 1,073 | 14.4% | 2.3% |
| Device operates differently than expectedthe device behaved unexpectedly | 805 | 10.8% | 4.5% |
| No display/image | 782 | 10.5% | 1.5% |
| Device displays incorrect message | 639 | 8.6% | 2.1% |
| Programming issue | 548 | 7.4% | 1.3% |
| Failure of device to self-test | 513 | 6.9% | 1% |
| Failure to interrogate | 444 | 6% | 2.5% |
| Application interface becomes non-functional or program exits abnormally | 426 | 5.7% | 0.8% |
| Failure to charge | 413 | 5.5% | 0.8% |
| Communication or transmission problemthe device could not communicate or transmit | 390 | 5.2% | 1.6% |
| Computer software problema software problem | 380 | 5.1% | 0.7% |
| Failure to power up | 370 | 5% | 0.7% |
| Device inoperablethe device could not be used | 316 | 4.2% | 1.5% |
| Computer failure | 255 | 3.4% | 0.5% |
| Charging problem | 254 | 3.4% | 0.5% |
| Breakthe device broke | 236 | 3.2% | 1.9% |
| Repair | 228 | 3.1% | 0.7% |
| Loose or intermittent connection | 193 | 2.6% | 0.6% |
| Loss of powerthe device lost power | 136 | 1.8% | 0.4% |
| Replace | 134 | 1.8% | 2.6% |
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 | 583 | 7.8% |
| Therapeutic response, decreased | 161 | 2.2% |
| Seizures | 92 | 1.2% |
| Painpain, site not specified | 29 | 0.4% |
| Depressionlow mood | 10 | 0.1% |
| Undesired nerve stimulation | 8 | 0.1% |
| Therapeutic effects, unexpected | 6 | 0.1% |
| Therapy/non-surgical treatment, additional | 6 | 0.1% |
| Electric shockan electric shock | 5 | 0.1% |
| Emotional changes | 5 | 0.1% |
| Neck painneck pain | 5 | 0.1% |
| Device overstimulation of tissue | 4 | 0.1% |
| Dyspneashortness of breath | 4 | 0.1% |
| Therapy/non-surgical treatment, aborted/stopped | 4 | 0.1% |
| Chokingchoking | 3 | 0% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Programming Software | Product code LYJ | All MAUDE reports |
|---|---|---|---|
| Reports | 7,453 | 52,004 | 26,136,888 |
| Share of that pool | — | 14.3% | 0% |
| Classified as death, per 1,000 reports | 0 | 56 | 9 |
| Classified as injury | 0.6% | 35.5% | 36.2% |
| Classified as malfunction | 99.3% | 58.7% | 62.3% |
| Filed by the manufacturer | 100% | 99.5% | 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 LYJ
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Lead Model 302 | 7,259 | 136 | 0% |
| Pulse Gen Model 102 | 5,903 | 14 | 12.2% |
| Pulse Gen Model 103 | 4,518 | 34 | 8.5% |
| Pulse Gen Model 106 | 4,023 | 144 | 5.1% |
| Pulse Gen Model 1000 | 3,601 | 549 | 5.7% |
| Lead Model 304 | 3,329 | 272 | 0.1% |
| Bipol Lead Model 300 | 1,955 | 12 | 0.1% |
| Pulse Gen Model Unk | 1,914 | 7 | 13.6% |
| Ncp Pulse Generator | 1,272 | 0 | 30% |
| Lead Model Unknown | 1,253 | 46 | 1.6% |
| Pulse Gen Model 101 | 1,210 | 0 | 12.6% |
| Pulse Gen Model 105 | 1,191 | 7 | 6.7% |
| Vns Therapy Pulse | 1,064 | 0 | 10.7% |
| Pulse Gen Model 102r | 985 | 0 | 10.9% |
| Pulse Gen Model 104 | 864 | 4 | 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 Programming Software reports
How many FDA reports name Programming Software?
7,453 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 1 in the latest 12 months.
What kinds of events are reported?
malfunction (99.3%) and injury (0.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
use of incorrect control/treatment settings (14.4%), device operates differently than expected (10.8%), no display/image (10.5%), device displays incorrect message (8.6%) and programming issue (7.4%). 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 Programming Software 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.