| Model Number |
BREV200 |
| Medical Device Problem Code |
Computer Software Problem (1112)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
09/13/2022
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
It was reported that a patient underwent a brevera biopsy procedure on (b)(6) 2022.The brevera console and the disposable were all successfully tested.The needle was then inserted into the patient breast at the target, but an error message (device driver loss communication) was displayed on the console; therefore the biopsy would not start.The needle was removed, the unit was rebooted but this could not solve the issue.The procedure with brevera system was then abandoned.The medical team decided to use another method: the patient was removed from compression, repositioned and a new target acquired; a second incision was made and the biopsy was completed using another biopsy device.No patient injury (other than a second incision made) or any adverse event was reported related to this incident.The involved brevera needle will not be returned for evaluation, as it was discarded.
|
| |
|
Additional Manufacturer Narrative
|
|
Hologic is submitting this report in accordance with 21.Cfr part 803.The submission is based upon the currently available information.The submission of this report does not represent a confirmation of device malfunction involving the hologic products in the event described.A device history record (dhr) review was conducted for the reported lot/serial number.The device was released meeting all qa specifications.We are currently unable to establish a relationship between the device and the issue reported.A field engineer (fe) visited the site to check the equipment and the reported console malfunction was confirmed.Fe found the error was coming from the driver, which had to be re-initialized.The driver is part of the machine that holds the needle for the biopsy.Once completed all the initialization steps, he simulated the driver firing and a biopsy procedure, which were all successfully completed.Fe confirmed that the root cause was the driver software which had to be re-initialized.The driver part itself did not require to be replaced.The system is working as intended.
|
| |
|
Search Alerts/Recalls
|