| Catalog Number |
4824102 |
| 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 |
06/17/2024
|
|
Type of Reportable Event
|
Malfunction
|
|
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)(4) 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
|
|
Investigation is in process, a follow-up report will be provided.
|
| |
|
Additional Manufacturer Narrative
|
|
This report is being filed to provide additional information in h.6 and h.11.Investigation: the run data file (rdf) was analyzed for this event.Alerts that are known to contribute to wbc contamination were not generated in this run data file.As the trima system cannot count the cells entering the platelet product bag, the rbc detector signals must see a significant change in the reflectance values to notify the operator of an lrs chamber saturation and to count the wbcs in the platelet product.In this case, the signals did not indicate that wbcs were escaping the lrs chamber.Therefore, the run data file reported that the platelet product could be labeled as leukoreduced.Although the trima system has several methods for detection of possible wbc contamination, it is possible that some events may elude the detection capability of the trima system.Analysis of the run data file showed that during the first 30 minutes of platelet collection the pumps stopped briefly due to low draw pressure.It is possible, though not conclusive the frequent pump pauses may have interrupted the steady state of the lrs chamber, causing some wbcs to escape from the lrs.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.
|
| |
|
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)(4).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 e.1, h.6 and h.11.Investigation: the run data file (rdf) was analyzed for this event.Alerts that are known to contribute to wbc contamination were not generated in this run data file.As the trima system cannot count the cells entering the platelet product bag, the rbc detector signals must see a significant change in the reflectance values to notify the operator of an lrs chamber saturation and to count the wbcs in the platelet product.In this case, the signals did not indicate that wbcs were escaping the lrs chamber.Therefore, the run data file reported that the platelet product could be labeled as leukoreduced.Although the trima system has several methods for detection of possible wbc contamination, it is possible that some events may elude the detection capability of the trima system.Analysis of the run data file showed that during the first 30 minutes of platelet collection the pumps stopped briefly due to low draw pressure.It is possible, though not conclusive the frequent pump pauses may have interrupted the steady state of the lrs chamber, causing some wbcs to escape from the lrs.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.Root cause: a root cause assessment was performed for this complaint.Alerts that are known to contribute to wbc contamination were not generated in this run data file.As the trima system cannot count the cells entering the platelet product bag, the rbc detector signals must see a significant change in the reflectance values to notify the operator of an lrs chamber saturation and to count the wbcs in the platelet product.In this case, the signals did not indicate that wbcs were escaping the lrs chamber.Therefore, the run data file reported that the platelet product could be labeled as leukoreduced.Although the trima system has several methods for detection of possible wbc contamination, it is possible that some events may elude the detection capability of the trima system.Analysis of the run data file showed that during the first 30 minutes of platelet collection the pumps stopped briefly due to low draw pressure.It is possible, though not conclusive the frequent pump pauses may have interrupted the steady state of the lrs chamber, causing some wbcs to escape from the lrs.
|
| |
|
Search Alerts/Recalls
|