Material substance originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.

Comment

Submitted by barbee.whitaker on

Response to IMO

We thank IMO for providing their thoughts on the Biologically Derived Product data class submission. While we agree that the FHIR Resource Biologically Derived Product in R5 Draft Ballot is not widely used (because R5 is not yet in Normative status), the R4 version of the resource has been agreed to be raised to FMM Level 2, indicating implementation across a number of implementers that are capturing and exchanging this data in FHIR. The BDP resource will then be on its way to FMM Level 3, following a formal round of balloting with comments from implementers.

It is also important to note that the underlying data elements that are being proposed under the Biologically Derived Product data class have been mapped to ICCBBA ISBT data elements which are widely used in capturing and exchanging data around biologically derived products in the US and internationally. As noted in our submission, ISBT labeling is required for all blood and blood components, as well as various tissues and transplant products in the United States, in order to be accredited by accrediting organizations in the United States and many other countries. These accrediting organizations require their members to use ISBT 128 coding and labeling for cellular therapies and ocular tissue (AABB [https://www.aabb.org/news-resources/resources/cellular-therapies/isbt-128-for-cellular-therapy], the Foundation for the Accreditation of Cellular Therapy (FACT) [https://news.factwebsite.org/isbt-128-audit-tool-for-cellular-therapy-provides-additional-resource-for-verifying-labels/] and the Eye Bank Association of America (EBAA) [http://restoresight.org/wp-content/uploads/2016/01/ISBT-Webpage-Implementation-Guide-Use-of-ISBT-128-in-North-American-Eye-Banks-v130.pdf]). This results in these data elements being captured physically on all blood bags and blood components, as well as other biologically derived products.

As such, ISBT-related data elements are captured in blood banking, laboratory information systems (LIS), and pathology software used across providers in the United States, and are being exchanged in HL7 formats today [reference: https://www.iccbba.org/uploads/8b/eb/8beb16a5f9e2c0c420a3e5f099f49b03/RT042-ISBT-128-Data-References-for-use-in-Electronic-Messages.pdf], as well as for reporting to NHSN and to FDA for hemovigilance and product safety purposes. We believe that inclusion of this data class in the next version of USCDI will encourage providers to capture these data elements in FHIR format, rather than in older HL7 formats, in an effort to move towards a modern FHIR API-based exchange of these very important data elements for patient access, as well as for coordination of care.

Submitted by minigrrl on

Support for Biologically Derived Product

Inclusion of the Biologically Derived Product element in USCDI, including the use of ISBT-128 standard codes, is vital for public health, regulatory, and research activities related to biological product effectiveness and safety, including hemovigilance surveillance supported by CDC’s National Healthcare Safety Network (NHSN). Current tracking of adverse events related to biologically derived products (e.g., blood transfusion-associated adverse events) is hindered by lack of accurate identifiers for transfusions amenable to fully electronic extraction from the electronic health record. The capability of identifying biologically derived products using this identifier would facilitate automated reporting for transfusions/transplants, reduce burden of reporting on providers, and significantly improve accuracy of hemovigilance and other patient safety activities.

Ongoing surveillance for blood safety in the United States is conducted through the CDC’s National Healthcare Safety Network (NHSN) Hemovigilance (HV) module, which is part of the Biovigilance component of NHSN. The NHSN HV module captures several types of transfusion-associated adverse events as well as monthly totals of blood use, by component type, at participating facilities. This surveillance is used to track the incidence and prevalence of transfusion-associated adverse events with the goal of informing strategies to reduce such events and improve overall patient safety.  In addition, CDC performs investigations and other studies as needed that do not currently make use of automated capture of electronic health records but are potential candidates for such automation in the future.

Lantana supports NHSN in hemovigilance surveillance and strongly recommends inclusion of a Biologically Derived Product in USCDI, including the use of ISBT-128 standard codes. A Biologically Derived Product data element would enable capture of individual blood components as well as adverse events for hemovigilance. Current tracking of adverse events in the NHSN HV module requires manual input of adverse events (including ISBT-128 codes for all implicated products), which can be burdensome and may not always yield complete information. Inclusion of a Biologically Derived Product element is vital for hemovigilance surveillance for multiple reasons, including reducing burden on providers by facilitating more automated reporting, improving overall participation in hemovigilance activities, and strengthening robustness and accuracy of reporting.

Inclusion of the Biologically Derived Product data element now is important for future consideration regarding how the standard will need to be expanded to meet the needs of hemovigilance and overall surveillance of biologically derived products in the future. It is vital that the USCDI engages with stakeholders in hemovigilance and other areas of surveillance of biologically derived products to ensure the standards are harmonized with the community-consensus definitions of adverse events, and to facilitate automated capture of essential safety information.

The Biologically Derived Product data element is relevant to all U.S. healthcare settings where blood transfusions, transplants, and other biological products are administered.

Use Case: https://www.cdc.gov/nhsn/biovigilance/blood-safety/index.html

In addition to the NHSN HV module, Lantana is leading work that relies on accurate information from electronic health records regarding identity of biologically derived products, https://www.lantanagroup.com/resources/blood-bank-ig/. This initiative is seeking to establish FHIR standards for blood product phenotyping. A biologically derived product element in USCDI is vital to support interoperability of data exchange to improve blood product inventory, facilitate safer transfusions, and contribute to more efficient adverse event reporting.

Additionally, Lantana is engaged on work led by IBM and FDA on adverse event reporting related to transfusions, which could benefit from inclusion of the Biologically Derived Product data element in USCDI: https://build.fhir.org/ig/HL7/fhir-icsr-ae-reporting/branches/main/index.html.

Submitted by Anna Razatos on

Terumo Supports a Biologically Derived Product Unique Identifier

Terumo Blood and Cell Technologies is a medical technology company. Our products, software and services enable customers to collect and prepare blood and cells to help treat challenging diseases and conditions. Our associates around the world believe in the potential of blood and cells to do even more for patients than they do today.  Terumo Blood and Cell Technologies supports the addition of a Biologically Derived Product data element to the United States Core Data for Interoperability (USCDI). Addition of the Medical Product of Human Origin (MPHO) Unique Identifier to USCDI will enhance the industries’ ability to track blood utilization and will enable more efficient hemovigilance activities such as disease transmission tracing, transfusion reaction investigations and preventing the transfusion of an incompatible unit of blood. Including the existing ISBT-128 label information into the MPHO Unique Identifier will provide seamless traceability of a transfusion from the donor to the patient. This simple act can help improve the health outcomes for all transfused patients and especially sickle cell and other chronically transfused individuals.

Submitted by jevans@america… on

ABC Supports a Biologically Derived Product Unique Identifier

America’s Blood Centers (ABC) represents 46 independent blood centers throughout the United States and a portion of Canada, who collect and distribute 60% of the U.S. blood supply.  ABC member centers support efforts to improve transfusion safety, including measures to increase traceability for blood, blood products and cellular therapies.

Blood centers already label blood products with a plethora of identifying information about the contents of the product, the method of collection and production, and a unique product code to allow for tracing a product from the donor to the recipient.  However, no standard mechanism currently exists for entering transfusion/infusion related information into a patient’s electronic health record (EHR).

ABC supports the addition of a Medical Product of Human Origin (MPHO) Unique Identifier that utilizes the existing information and codes already generated by blood centers as a part of the blood label.  Adding an MPHO to the U.S. Core Data for Interoperability (USCDI) data set will allow for easier data collection and tracing, without creating any additional work for blood collectors.

Capturing existing ISBT-128 data elements (donation number, product code, and division number), into the MPHO Unique Identifier will provide critical traceability to the donor and collection/processing facility, providing a more efficient and accurate process for disease transmission look-back activities and transfusion reaction investigations.

Interoperability will provide patients and health care providers access to previous transfusion records, which is critical in managing individuals with unexpected antibodies (e.g. sickle cell disease patients) or a history of adverse transfusion events.

ABC supports the creation of a new standardized data element utilizing existing ISBT-128 blood labeling information to increase transfusion safety, improve patient outcomes and enhance data collection valuable to monitoring blood utilization. 

Submitted by barbee.whitaker on

FDA CBER Biologically Derived Product Submission Clarifications

FDA’s Center for Biologics Evaluation and Research appreciates the comments shared by numerous stakeholders related to the Biologically Derived Product submission. As of April 2021, there are three aspects worth noting:

  1. Resubmission: A revised version of the Biologically Derived Product submission was resubmitted in January 2021 following an update to the ONDEC guidance. This version has not yet been updated on the ONC USCDI website as of April 2021. See attachment for details.
  2. Product Information Elements: Based on other stakeholder comments, the submission could be further modified to incorporate division number and derived or concatenated identifiers (i.e., Medical Products of Human Origin).
  3. Policy: Based on other stakeholder comments, the submission could be further modified to clarify that inclusion of Biologically Derived Product in USCDI would not require the use of a particular identification standard if it is not currently being exchanged by an organization. The current submission references code systems/identifiers (i.e., ISBT-128, RxNorm, and NDC) that are widely used and support a majority of use cases.

As demonstrated above, the ONDEC process has enabled a valuable platform for stakeholders to discuss specifics related to the Biologically Derived Product domain. Continued discussion will be critical to ensure this submission is sufficiently robust to meet criteria for inclusion in USCDI.

FDA CBER ONDEC BioDerProd Resubmission 2021-01.docx

Submitted by Leah Stone on

Support for “Biologically Derived Product” Data Element

AABB is an international, not-for-profit association representing institutions and individuals involved in transfusion medicine and cellular therapies. The association is committed to “improving lives by making transfusion medicine and biotherapies safe, available and effective worldwide.” AABB works toward this vision by developing and delivering standards, accreditation, and educational programs that focus on optimizing patient and donor care and safety. AABB individual membership includes physicians, nurses, scientists, researchers, administrators, medical technologists, and other health care providers.

AABB supports the addition of a Biologically Derived Product data element to the United States Core Data for Interoperability (USCDI) and believes that using the ISBT-128 standard will enhance the nation’s understanding of blood availability and utilization, advance hemovigilance capabilities and improve health outcomes.  

A Biologically Derived Product data element would enable providers to uniformly capture the utilization of individual blood components as well as adverse events for hemovigilance. As noted in the FDA’s use case description, the absence of interoperability in this area was particularly problematic during the rollout of COVID-19 convalescent plasma (CCP) and limited the ability of regulators and researchers to perform safety and effectiveness surveillance. The data could be used to assess whether the current supply of specific blood components is adequate to satisfy patient needs and to monitor safety and effectiveness.

Additionally, a Biologically Derived Product data element has the potential to inform policies and guide clinical practices early in the course of treatment (e.g., capturing blood group genotyping in chronically transfused patients or patients initiating novel monoclonal therapies known to cause complication in transfusion workups). It would also serve as a tool to help identify non-infectious complications, such as transfusion-associated circulatory overload (TACO), the transfusion-related acute lung injury (TRALI), and transfusion of an incompatible unit of blood. Importantly, interoperability in this area would facilitate the ability of providers to have access to a patient’s transfusion history, regardless of where a previous transfusion occurred. This can help prevent incompatible transfusions, support red blood cell antigen matching, and ultimately improve health outcomes for chronically transfused individuals, such as patients with sickle cell disease.

AABB believes that adding a Biologically Derived Product data element to the USCDI is key to strengthening the nation’s blood system, advancing patient safety, and improving health outcomes.

Submitted by jnakashima@ehe… on

ISBT 128 Critically Needed as Biologics Unique Identifier

eHealth Exchange, the nation’s largest health information exchange network, wholeheartedly agrees the ISBT 128 international standard should be used in USCDI v2 as the globally-unique identifier for blood and other biologic products. The addition of Biologically Derived Products to USCDI v2 using the ISBT standard is critical to improving patient safety, coordination of care, and patient data portability for patients treated with biologic products of human origin. The addition of the Biologically Derived Products data class to USCDI v2 enables the exchange of granular details related to biologic products for the coordination of care between exchange participants, in addition to linkage of exposure records to adverse events that can be traced to specific biologic products of human origin

Submitted by barbee.whitaker on

FDA CBER Response to eHealth Exchange

Thank you for your comment. eHealth Exchange has identified important Use Cases that reinforce the need to include the Biologically Derived Product unique identifiers the USCDI.

Log in or register to post comments

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB