| Model Number |
24967 |
| Medical Device Problem Code |
Communication or Transmission Problem (2896)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
04/03/2026
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Product analysis: performance data collected from the mobile programmer was received and analyzed.Analysis of the service logs found the customer comment that the patient connector had a disconnect was confirmed.Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Additional Manufacturer Narrative
|
|
Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Event or Problem Description
|
|
T was reported that the patient connector had a repeated bluetooth disconnect when attempting to interrogate the cardiovascular implantable electronic device (cied), and when it was connected, the implantable device was unable to be located.Troubleshooting steps were taken to reset the bluetooth connection on the host tablet settings, followed by re-pairing within the mobile programmer application which resolved the issue.No patient complications have been reported as a result of this event.Application version: 4.5.2 host tablet os version: 26.2.1.
|
| |
|
Search Alerts/Recalls
|