| Catalog Number |
D134804 |
| Medical Device Problem Code |
Patient Device Interaction Problem (4001)
|
| Health Effect - Clinical Code |
Cardiac Tamponade (2226)
|
| Date of Event |
12/03/2025
|
|
Type of Reportable Event
|
Serious Injury
|
|
Additional Manufacturer Narrative
|
|
Device investigation details: an analysis of the product could not be performed since a physical sample was not received for evaluation.An evaluation of the manufacturing record could not be performed as the required product identification number was not provided to complete the evaluation.However, if the product is received at a later date, the investigation will be updated as applicable.As part of our company quality system process, all devices are manufactured, inspected, and distributed to approved specifications.Note: for field d4: udi: as the lot number for the device involved in the event was not provided, the full udi is currently not available.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.Manufacturer's ref.# (b)(4).
|
| |
|
Event or Problem Description
|
|
A patient underwent an atrial fibrillation (afib) ablation procedure with a thermocool smarttouch sf catheter, the patient experienced hypotension and pericardial effusion treated with pericardiocentesis and extended hospitalization because of pericardiocentesis as well as additional fluid draining overnight after procedure, and for monitoring.The report indicated that after an afib case, a pericardial effusion was noticed.There were no issues with the patient during the procedure.The patient became hypotensive when the patient was in post-op.The pericardial effusion was confirmed by echo.The medical intervention provided was pericardiocentesis.The patient was in stable condition.The physician¿s opinion on the cause of this adverse event was that it was procedure related.Physician believes it was after ablation and during the ventricular electrophysiology (ep) study when pacing off ablation catheter in ventricle.The outcome of the adverse event was fully recovered (no residual effects).The patient required extended hospitalization because of pericardiocentesis as well as additional fluid draining overnight after procedure, and for monitoring.The relevant tests/laboratory data was a transesophageal echocardiogram (tte).The procedural activated clotting time (act) was greater than 350.One transseptal puncture site was performed during the procedure with an abbott brk needle.The number of performed ablations was 55 with radio frequency (rf) energy for all ablations.47 ablations were performed within the pulmonary veins.8 ablations were performed outside the pulmonary veins for cavotricuspid ishmus (cti).No evidence of steam pop.The flow settings were 0-30w-8ml/min, 30+w-15 ml/min, pre ablation high flow -2sec., and low flow-2ml/min.The patient did not require cardiac surgery.The correct catheter settings were selected on the ngen¿ generator.No issues with flow rate change at the start of ablation.The force visualization features used were graph, dashboard, vector and visitag.The visitag module parameters for stability used were max distance:1.5 ml and min time: 3 sec.The visitag filter used was fot 25% at 3g respiration adjustment.The color option used prospectively was surpoint tag index.
|
| |
|
Additional Manufacturer Narrative
|
|
Correction: on 8-jan-2026, it was noticed the h6.Health effect - impact code of ¿surgical intervention (f19)¿ was inadvertently omitted from the 3500a initial medwatch.It has now been added.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
|
|