Model Number ALIZEA DR 1600 |
Device Problem
Patient Device Interaction Problem (4001)
|
Patient Problem
Tachycardia (2095)
|
Event Date 04/27/2022 |
Event Type
malfunction
|
Manufacturer Narrative
|
The device involved in this mdr report is not approved in the united states; however, it is similar to a device manufactured by microport crm that was cleared or approved by fda for marketing in the united states.
|
|
Event Description
|
Reportedly, this patient was implanted with an alizea dr to replace an earlier pacemaker having reached it's recommended replacement time.After implantation, the pacemaker was programmed to the safer-r mode.The patient was paced faster than usual presenting with ddd alike behaviour.After several mode changes, the heart rate became normal and spontaneous r waves became sensed.We can't explain what happened.Preliminary analysis is suggestive for the user not giving the system enough time to stabilize.
|
|
Event Description
|
Reportedly, this patient was implanted with an alizea dr to replace an earlier pacemaker having reached it's recommended replacement time.After implantation, the pacemaker was programmed to the safer-r mode.The patient was paced faster than usual presenting with ddd alike behaviour.After several mode changes, the heart rate became normal and spontaneous r waves became sensed.We can't explain what happened.Preliminary analysis is suggestive for the user not giving the system enough time to stabilize.
|
|
Manufacturer Narrative
|
The device involved in this mdr report is not approved in the united states; however, it is similar to a device manufactured by microport crm that was cleared or approved by fda for marketing in the united states.Please find below the conclusion of the analysis provided to the subsidiary (sent by mail on 31/08/2022): "it can be seen that there was a long and ¿rapid¿ sequence of tests and re-programming (annotations in red in the first column correspond to the real time of the launch of each of these activities).Consequently, the time for the system to get in a ¿steady state¿ was limited furthermore: all along the test / reprogramming's r-wave amplitude was on the small side.Certain functionalities and internal parameters may get disabled / re-initialized during testing.There are a number of dynamic criteria / triggers proper to the safer mode that may cause a temporary switch / a prolonged stay in ddd.It¿s not possible to retrtrieve the status of these at any time / any beat.The same goes for the observed temporary increases of the pacing rate overall it seems, once the system came in a steady state, spontaneous r-waves were given priority over ventricular pacing (which of course is the aim of the safer mode) therefore no issue is suspected with the device.".
|
|
Search Alerts/Recalls
|