SORIN GROUP ITALIA S.R.L. - CRM FACILITY REPLY 200; IMPLANTABLE PULSE GENERATOR, PACEMAKER (NON-CRT)
|
Back to Search Results |
|
Model Number REPLY 200 DR |
Device Problem
Loss of Data (2903)
|
Patient Problem
No Information (3190)
|
Event Date 11/13/2017 |
Event Type
malfunction
|
Manufacturer Narrative
|
The device model involved in this mdr report is not approved in the united states; however, it is similar to a device manufactured by livanova that was cleared or approved by fda for marketing in the united states.
|
|
Event Description
|
Reportedly, on (b)(6) 2017 a pacemaker replacement procedure was performed.While still in the box, the subject device was reprogrammed to operate at 50 min-1 in aai mode.The pacemaker was then taken out of the package and connected to the atrial and ventricular leads.After the pocket was closed, when the device was interrogated, it was found that aida had not been activated.After ¿aida programming¿ was manually performed in the aida screen, the programming session ended.The pacemaker was then re-interrogated, but aida had still not been activated.The pacing mode was reprogrammed to safer.This time, aida had been activated and statistical data such as the pacing rate had been recorded.With the pacing mode remaining in safer, the basic rate was programmed to 50 min-1 (max.130 min-1).On (b)(6) 2017 the device was interrogated; however, no data had been recorded in the device memory.The pacemaker was reprogrammed back to aai mode without no further examination regarding the behavior related to aida.After the pacemaker was reprogrammed from safer mode to operate in aai mode at 50 min-1, aida programming was performed to ensure a proper activation of aida.
|
|
Manufacturer Narrative
|
Please refer to the attached analysis report.
|
|
Event Description
|
Reportedly, on (b)(6) 2017 a pacemaker replacement procedure was performed.While still in the box, the subject device was reprogrammed to operate at 50 min-1 in aai mode.The pacemaker was then taken out of the package and connected to the atrial and ventricular leads.After the pocket was closed, when the device was interrogated, it was found that aida had not been activated.After ¿aida programming¿ was manually performed in the aida screen, the programming session ended.The pacemaker was then re-interrogated, but aida had still not been activated.The pacing mode was reprogrammed to safer.This time, aida had been activated and statistical data such as the pacing rate had been recorded.With the pacing mode remaining in safer, the basic rate was programmed to 50 min-1 (max.130 min-1).On (b)(6) 2017 the device was interrogated; however, no data had been recorded in the device memory.The pacemaker was reprogrammed back to aai mode without no further examination regarding the behavior related to aida.After the pacemaker was reprogrammed from safer mode to operate in aai mode at 50 min-1, aida programming was performed to ensure a proper activation of aida.
|
|
Manufacturer Narrative
|
Preliminary analysis did not reveal any device malfunction.
|
|
Event Description
|
Reportedly, on (b)(6) 2017 a pacemaker replacement procedure was performed.While still in the box, the subject device was reprogrammed to operate at 50 min-1 in aai mode.The pacemaker was then taken out of the package and connected to the atrial and ventricular leads.After the pocket was closed, when the device was interrogated, it was found that aida had not been activated.After ¿aida programming¿ was manually performed in the aida screen, the programming session ended.The pacemaker was then re-interrogated, but aida had still not been activated.The pacing mode was reprogrammed to safer.This time, aida had been activated and statistical data such as the pacing rate had been recorded.With the pacing mode remaining in safer, the basic rate was programmed to 50 min-1 (max.130 min-1).On (b)(6) 2017 the device was interrogated; however, no data had been recorded in the device memory.The pacemaker was reprogrammed back to aai mode without no further examination regarding the behavior related to aida.After the pacemaker was reprogrammed from safer mode to operate in aai mode at 50 min-1, aida programming was performed to ensure a proper activation of aida.
|
|
Manufacturer Narrative
|
Additional analysis confirmed that device memory was unexpectedly deactivated.
|
|
Event Description
|
Reportedly, on (b)(6) 2017 a pacemaker replacement procedure was performed.While still in the box, the subject device was reprogrammed to operate at 50 min-1 in aai mode.The pacemaker was then taken out of the package and connected to the atrial and ventricular leads.After the pocket was closed, when the device was interrogated, it was found that aida had not been activated.After ¿aida programming¿ was manually performed in the aida screen, the programming session ended.The pacemaker was then re-interrogated, but aida had still not been activated.The pacing mode was reprogrammed to safer.This time, aida had been activated and statistical data such as the pacing rate had been recorded.With the pacing mode remaining in safer, the basic rate was programmed to 50 min-1 (max.130 min-1).On (b)(6) 2017 the device was interrogated; however, no data had been recorded in the device memory.The pacemaker was reprogrammed back to aai mode without no further examination regarding the behavior related to aida.After the pacemaker was reprogrammed from safer mode to operate in aai mode at 50 min-1, aida programming was performed to ensure a proper activation of aida.
|
|
Search Alerts/Recalls
|
|
|