Model Number REPLY 200 SR |
Device Problems
Display or Visual Feedback Problem (1184); Pacemaker Found in Back-Up Mode (1440)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 07/19/2023 |
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
|
On (b)(6) 2023, the customs found an anomaly (reply 200 sr/sn:(b)(6) in the on-site medical inspection of the warehouse.The anomaly is as follows: 1.The programmer cannot read the information for the first time (other pacemaker models are normal); 2.The programmer cannot be read after multiple operations (1 minute (no information), 3 minutes and 15 seconds (no information).3.Reset (confirm) exit, restart the programmer to read the information (pacemaker name and serial number) for 5 minutes and 32 seconds and the programmer crashes and cannot continue the program.
|
|
Event Description
|
Msc received the waybill /(b)(6) pacemaker *173 sets.On 2023-07-20, the customs found an anomaly (reply 200 sr/sn:(b)(6)) in the on-site medical inspection of msc warehouse.The anomaly is as follows: 1.The programmer cannot read the information for the first time (other pacemaker models are normal); the programmer is shown in picture.2.The programmer cannot be read after multiple operations (1 minute (no information), 3 minutes and 15 seconds (no information)).The programmer still displays as shown in figure 1; it is normal to switch to other pacemaker models midway; 3.Reset (confirm) exit, restart the programmer to read the information (pacemaker name and serial number) for 5 minutes and 32 seconds, as shown in figure 2, and then the instant programmer crashes and cannot continue the program.
|
|
Manufacturer Narrative
|
Additional patient files have been received and therefore new analysis has been performed with the following conclusions: - the device has switched in standby mode most probably due to a crosstalk that had occurred between devices being in a too close vicinity of each other at the time of interrogation (potentially leading to data inconsistencies).- the subject device has been correctly reinitialized on 20th july 2023 and has not switched in standby mode since.- a new interrogation should be performed.In case of normal functioning has been correctly restored, it is considered that the device can be implanted.
|
|
Event Description
|
Msc received the waybill /trn36735009 pacemaker *173 sets.On 2023-07-20, the customs found an anomaly (reply 200 sr/sn:(b)(6) ) in the on-site medical inspection of msc warehouse.The anomaly is as follows: the programmer cannot read the information for the first time (other pacemaker models are normal); the programmer is shown in picture.The programmer cannot be read after multiple operations (1 minute (no information), 3 minutes and 15 seconds (no information)).The programmer still displays as shown in figure 1; it is normal to switch to other pacemaker models midway; 3.Reset (confirm) exit, restart the programmer to read the information (pacemaker name and serial number) for 5 minutes and 32 seconds, as shown in figure 2, and then the instant programmer crashes and cannot continue the program.
|
|
Manufacturer Narrative
|
The reason of this switch in standby mode cannot be determined since no patient files at that date are available (19 of july 2023).- the files dated of 1st of august 2023 have shown that the subject device has been correctly reinitialized on 20th july 2023 and has not switched in standby mode since.- the root cause could not be determined since the files dated of the event date are missing.
|
|
Search Alerts/Recalls
|