Submitted by klmoniz on
Continued ICCBBA support for inclusion of BDP data elements
ICCBBA continues to strongly support the inclusion of the Biologically Derived Product data elements in the USCDI. We specifically support the MPHO Unique Identifier, Product Codes, Source Identifier, Division, and Processing Facility coding.
With the recent enhancements to the BiologicallyDerivedProduct Resource of HL7®FHIR® Standard (Release 5), these elements are now more readily accessible. The maturity of the data elements based on the ISBT 128 Standard, in use for decades, is clearly established. In addition to these key elements of traceability being readily accessed from the bar codes or 2D Data Matrix symbols on an ISBT 128 label, they are also widely incorporated into blood product administration modules of multiple software platforms.
The inclusion of the Biologically Derived Product data elements in the USCDI will further enhance the ability of electronic medical records to support both traceability and biovigilance across the full spectrum of Medical Products of Human Origin (MPHO) by providing the ability to link key MPHO information in a standard manner to the recipient’s record.
Submitted by Leah Stone on
AABB Support for Biologically Derived Product Data Element
The Association for the Advancement of Blood and Biotherapies (AABB) continues to support the addition of a Biologically Derived Product data element to the USCDI. Interoperability in this area is aligned with the goals expressed in the January 2023 ONC Health IT Standards Bulletin of facilitating patient access, promoting health equity, reducing disparities, supporting underserved communities, and advancing public health data interoperability. For instance, a Biologically Derived Product data element has the potential to facilitate the ability of providers to have access to a patient’s transfusion history, regardless of where a previous transfusion occurred. This capability would help advance ONC’s goals by helping to prevent incompatible transfusions, supporting red blood cell antigen matching, and ultimately improving health outcomes for chronically transfused individuals, such as patients with sickle cell disease. As another example, a Biologically Derived Product data element would support patients’ access to care because it could be used to assess whether the current supply of specific blood components is adequate to satisfy patients’ needs. It would also serve as a tool to advance hemovigilance capabilities and improve health outcomes for patients who receive blood transfusions. For example, it could help identify non-infectious complications, such as transfusion-associated circulatory overload (TACO), transfusion-related acute lung injury (TRALI), and transfusion of an incompatible unit of blood.