|
|
| Catalog Number |
4824062 |
| Medical Device Problem Codes |
Adverse Event Without Identified Device or Use Problem (2993); Insufficient Device Problem Information (3190)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
09/04/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Investigation: the run data file (rdf) was analyzed for this event.The signals in the run data file indicate that the higher-than-expected wbc content in the platelet product was possibly the result of a wbc saturation of the lrs chamber that fell just under the detection threshold for flagging the platelet product for wbc verification, and which occurred at around 117 minutes into the procedure.The signals in the run data file also indicate that the device had difficulty establishing and maintaining steady state operation during the procedure, so it cannot be ruled out that the needle line access may have been suboptimal from the start of the collection, or that the needle line access may have shifted and could potentially have impacted the collection.Additionally, based on the signals in the run data file, it cannot be ruled out that the donor's platelets may have been activating in the channel and in the lrs chamber, disrupting the packed bed and causing platelets to exit the centrifuge in an inconsistent manner.Based on the available information, it cannot be ruled out that the higher-than-expected wbc content in the platelet product may have been donor-related.The device history records (dhr) were reviewed for this lot.There were no events noted in the dhr that would have contributed to the elevated wbc count experienced by the customer.Investigation is in process, a follow-up report will be provided.
|
| |
|
Event or Problem Description
|
|
The customer would like the run data file investigated to determine a possible cause for the elevated white blood cell (wbc) content in the platelet product.Donor unit#: (b)(6) there was not a transfusion recipient or patient involved at the time of the residual wbc testing; therefore, no patient information is reasonably known at the time of the event.The platelet collection set is not available for return because it was discarded by the customer.
|
| |
|
Additional Manufacturer Narrative
|
|
This report is being filed to provide additional information in d.4, h.6 and h.11.Investigation: the run data file (rdf) was analyzed for this event.The signals in the run data file indicate that the higher-than-expected wbc content in the platelet product was possibly the result of a wbc saturation of the lrs chamber that fell just under the detection threshold for flagging the platelet product for wbc verification, and which occurred at around 117 minutes into the procedure.The signals in the run data file also indicate that the device had difficulty establishing and maintaining steady state operation during the procedure, so it cannot be ruled out that the needle line access may have been suboptimal from the start of the collection, or that the needle line access may have shifted and could potentially have impacted the collection.Additionally, based on the signals in the run data file, it cannot be ruled out that the donor's platelets may have been activating in the channel and in the lrs chamber, disrupting the packed bed and causing platelets to exit the centrifuge in an inconsistent manner.Based on the available information, it cannot be ruled out that the higher-than-expected wbc content in the platelet product may have been donor-related.The device history records (dhr) were reviewed for this lot.There were no events noted in the dhr that would have contributed to the elevated wbc count experienced by the customer.A disposable complaint history search was performed for this lot and found no other reports for similar issues on this lot.Root cause: a root cause assessment was performed for this complaint.The signals in the run data file indicate that the higher-than-expected wbc content in the platelet product was possibly the result of a wbc saturation of the lrs chamber that fell just under the detection threshold for flagging the platelet product for wbc verification, and which occurred at around 117 minutes into the procedure.The signals in the run data file also indicate that the device had difficulty establishing and maintaining steady state operation during the procedure, so it cannot be ruled out that the needle line access may have been suboptimal from the start of the collection, or that the needle line access may have shifted and could potentially have impacted the collection.Additionally, based on the signals in the run data file, it cannot be ruled out that the donor's platelets may have been activating in the channel and in the lrs chamber, disrupting the packed bed and causing platelets to exit the centrifuge in an inconsistent manner.Based on the available information, it cannot be ruled out that the higher-than-expected wbc content in the platelet product may have been donor-related.
|
| |
|
Event or Problem Description
|
|
The customer would like the run data file investigated to determine a possible cause for the elevated white blood cell (wbc) content in the platelet product.Donor unit #: (b)(6).There was not a transfusion recipient or patient involved at the time of the residual wbc testing; therefore, no patient information is reasonably known at the time of the event.The platelet collection set is not available for return because it was discarded by the customer.
|
| |
|
Search Alerts/Recalls
|
|
|