|
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.
|
|
It was reported that during right ventricular (rv) lead placement, the patient lost conduction and experienced asystole.It was noted that pacing using the mobile programmer application pacing system analyzer (psa) was attempted after rapid lead fixation.Pacing was initiated at 90 bpm.Approximately two minutes later, a reduction in pacing rate to 60 bpm was attempted; however, the psa did not accept the rate change.It was observed that the displayed rate changed to display question mark symbols and a pop-up message appeared stating that the parameter change was not confirmed.Multiple attempts to adjust the pacing rate were unsuccessful, and pacing continued at 90 bpm.Attempts to change the pacing mode from vvi to voo resulted in the same message, with no parameter changes applied.Troubleshooting steps were taken to include confirming wireless fidelity was turned off on the host tablet and verifying that the mobile programmer and patient connector were paired.The issue persisted despite these actions.Additional troubleshooting steps were taken to include swapping the mobile programmer for a legacy programmer which was used as an alternate psa, allowing the mobile programmer application psa to be force closed and restarted.Following the restart, the mobile programmer application psa functioned as expected.The rv lead was successfully implanted and remains in use.No further patient complications have been reported as a result of this event.Application version: 4.4.2 host tablet os version: 18.5.
|