|
Catalog Number FG560000 |
Device Problems
Display or Visual Feedback Problem (1184); Electrical /Electronic Property Problem (1198); Communication or Transmission Problem (2896)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 10/03/2023 |
Event Type
malfunction
|
Manufacturer Narrative
|
The hardware investigation has begun but it has not been completed at this time.When the investigational analysis has been completed, a supplemental 3500a report will be submitted.This report is being submitted pursuant to the provisions of 21 cfr, part 803.This report may be based on information which has not been investigated or verified prior to the required reporting date.This report does not reflect a conclusion by biosense webster inc., or its employees that the report constitutes an admission that the product, biosense webster inc., or its employees caused or contributed to the potential event described in this report.If information is obtained that was not available for the initial report, a follow-up report will be filed as appropriate.If additional information is received regarding this event, a supplemental 3500a report will be submitted to the fda.Manufacturer's ref# (b)(4).
|
|
Event Description
|
It was reported that a patient underwent an atrial fibrillation (afib) ablation procedure with a carto® 3 system and a map shift issue occurred.As we started the case, there was no error.We started ablating the left veins and while on the ridge physician complained that there is a map shift.I checked my patched by pressing ctrl+ p and they looked all okay, but when i brought up the metal values, the values were high for patch 5 and patch 6 (front patch).We started remapping and after some time, multiple errors popped up like spu synchronization error, illegal pacing channel selection and finally the piu communication error.I restarted the piu and ngen and everything started working fine.When we started ablating the right veins the map shift didn't look that serious as left side.The issue occurred during ablation and it was around 3cm.There were no errors provided by the system, only physician thought that the catheter movement was not aligning with the fast anatomical mapping (fam).No cardioversion was performed, neither did the patient moved as the whole procedure was performed under general anesthesia.There was a 15 minute delay in the procedure but it was completed successfully.
|
|
Manufacturer Narrative
|
It was reported that a patient underwent an atrial fibrillation (afib) ablation procedure with a carto® 3 system and a map shift issue occurred.As we started the case, there was no error.We started ablating the left veins and while on the ridge physician complained that there is a map shift.The issue occurred during ablation and it was around 3cm.There were no errors provided by the system, only physician thought that the catheter movement was not aligning with the fast anatomical mapping (fam).No cardioversion was performed, neither did the patient moved as the whole procedure was performed under general anesthesia.Device evaluation details: an investigation was initiated by the device manufacturer.After reviewing the received data, it was found that the reported map shift was caused due to mapping with high metal values that were indicated on the screen by an error messages.Issue is related to user error.In addition, multiple errors popped up like spu synchronization error, illegal pacing channel selection and finally the patient interface unit (piu) communication error.It was confirmed that the errors were not duplicated after rebooting the piu and the ngen rf generator.The system is ready for use.The history of customer complaints reported during the last year associated with carto 3 system #r10032 was reviewed.No similar complaints were found.The manufacturing record evaluation was performed on carto 3 system #r10032, and no internal actions related to the reported complaint condition were identified.If additional information is received regarding this event, a supplemental 3500a report will be submitted to the fda.Manufacturer's ref.# (b)(4).
|
|
Search Alerts/Recalls
|
|
|