Verifies accuracy of labeling of ABO/Rh via bar code reader by comparing the scanned ABO/RH label to the ABO/RH results for that unit ID.
Prevents the same tech doing both labeling and verifying if labeling/release is done manually based on a comparison of the identity of the user attempting to release the unit with the entry in the Tech Labeling field (#.06) for that specific unit.
For each component which is labeled/released, assigns a final disposition of RELEASE to each component in the BLOOD DONOR file (#65.5) and automatically creates a new entry in the BLOOD INVENTORY file (#65) with specific associated data elements.
Assigns the division of the user who is labeling/ releasing the unit into inventory to the unit when the unit is assigned a final disposition in the BLOOD DONOR file (#65.5) and unit is entered into the BLOOD INVENTORY file (#65).
Puts an entry of ‘YES’ in the Pos/Incomp. Screening Tests field (#8) for both allogeneic (homologous) and autologous units which are released to inventory with incomplete transfusion transmitted disease marker testing such that those units are identified if subsequent attempts are made to modify the unit into another blood component or to ship the unit to another facility.
Puts an entry of ‘YES’ in the Pos/Incomp. Screening Tests field (#8) for autologous units released to inventory with positive/incomplete testing such that those units cannot be released for use by other patients and cannot be modified into other non-autologous components.
Based on entry in the LABORATORY SITE PARAMETERS file (#69.9) for the FIRST DEFAULT for the BLOOD DONOR, determines whether ABO/Rh confirmatory testing results are to be transferred to the BLOOD INVENTORY file (#65). If NO, data is not transferred and unit contains red cells (based on the entry in the BLOOD PRODUCT file (#66) for that component), adds the unit to the queue for inclusion on the Inventory ABO/Rh worklist. If YES, data is transferred and the unit in not added to the queue for inclusion on the Inventory ABO/Rh worklist even if the unit contains red cells.
Donor Software Requirements Specifications
Requires a higher level of security access (LRBL SUPER key) to make changes in status from ‘quarantine’.
Laboratory V. 5.2 Blood Bank User Manual