|
An investigation was conducted: it was reported on (b)(6) 2025, that during a procedure the brevera system (b)(6) and brevera driver (b)(6) began experiencing driver errors.The tech shut down the system and restarted it, but the error did not clear.The procedure was aborted, and the patient was rescheduled.Since the patient was rescheduled, patient impact was reported.Dispatched field service engineer (fse) disconnected driver cable and restarted the unit.After plugging the driver back in the system recognized the driver.Neither the brevera system nor the brevera driver used in this complaint were returned for investigation.The brevera driver was 171 days old at the time of the complaint.Further investigation could not be performed as parts were not returned to pmqa.Since no parts were returned, a definitive root cause could not be determined.After reviewing the complaint, discussing the case with a hologic service sustainment engineer, and examining a previous investigation into this type of issue, the most probable root cause for the reported error codes is related to the needle not firing its fully designated firing distance.This root cause can be linked to insufficient spring force when firing into breast tissue causing excess drag and reducing needle travel velocity.As a result, the timing shaft can become jammed with the outer cannula fork and the wear plate, effectively blocking cam shaft rotation and preventing biopsy samples from being taken.Conclusion: as no parts were returned to pmqa for investigation, root cause for the reported issue was unable to be determined.Conversations with service engineering indicated that based off the error experienced, it is likely that the needle did not fire its full distance, and the cannula forks jammed with the timing shaft of the driver.Since the patient had to be rescheduled for an additional procedure due to an inability to retrieve biopsy samples, this was considered a reportable event to the fda.A new driver design has been created that will address the spring force issue.Pmqa will monitor the complaint data for this new driver design and look to see if trends for the driver being jammed are still occurring.Device history record (dhr) review: driver serial number: (b)(6) driver sku: brevdrv system serial number: (b)(6) driver manufacture date: 10/1/2024 driver installation date: (b)(6) 2024 udi: (b)(4).Driver dhr review was performed.The device history record for the serial number involved was reviewed and was found to have met all manufacturing requirements prior to shipment for distribution.This includes final inspection and packaging inspections.No deviations are mentioned within the dhr.
|