| Model Number |
M00558620 |
| Medical Device Problem Codes |
Leak/Splash (1354); Material Puncture/Hole (1504)
|
| Health Effect - Clinical Code |
No Consequences Or Impact To Patient (2199)
|
| Date of Event |
07/11/2020
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Investigation result a visual examination of the returned complaint device found that the balloon did not have any visual defects and was in a good condition.No damage was found on the catheter of the device.Functional analysis was performed, and the balloon was inflated without a problem; however, there was a pinhole over the shoulder of the body of the balloon.Based on the available information, the failure reported may be related to some factors, such as interaction with the scope that could have caused the physician to use force during insertion of the balloon in the working channel that could have resulted in the reported failure.The most probable root cause is adverse event related to procedure.A review of the device history record (dhr) was performed and confirmed that this device met all material, assembly and performance specifications.A labeling review was performed and from the information available, this device was not used per the directions for use (dfu)/product label as the balloon was pre-inflated.
|
| |
|
Event or Problem Description
|
|
It was reported to boston scientific corporation that a cre pro wireguided dilatation balloon was used in the common bile duct (cbd) during an endoscopic retrograde cholangiopancreatography (ercp) procedure performed on (b)(6) 2020.According to the complainant, during the procedure, the balloon was attempted to be inflated; however, it was noticed that the balloon was leaking.It was noted that the balloon had been pre-tested prior to use in the patient.The procedure was completed with another cre pro wireguided dilatation balloon.There were no patient complications reported as a result of this event.Investigation results revealed that this balloon had a pinhole; therefore, this is now an mdr reportable event.
|
| |
|
Search Alerts/Recalls
|