ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

BiologicallyDerivedProduct — Biological product

A bag of red blood cells, an organ for transplant, stem cells: any biological product tracked from donor to recipient. The FHIR foundation for transfusion and transplant services.

Purpose

BiologicallyDerivedProduct covers products of biological origin intended to be administered or transplanted: blood products (RBC, plasma, platelets), organs (kidney, liver, heart), tissues (cornea, bone, skin), haematopoietic stem cells. Traceability is critical for transfusion safety and transplant.

The ISBT 128 identifier (Information Standard for Blood and Transplant) is the international standard for labelling blood and tissue products. It enables traceability from donor to recipient — a regulatory requirement in the EU (FACT/JACIE) and the US (FDA / AABB).

Key elements

FieldTypeCardinalityRole
productCategoryCodeableConcept0..1Category (organ, tissue, fluid, cells, biologicalAgent).
productCodeCodeableConcept0..1Product code (HL7 v2-0913 table or other).
parentReference(BiologicallyDerivedProduct)[]0..*Parent product on splitting.
requestReference(ServiceRequest)[]0..*Originating request.
identifierIdentifier[]0..*External identifiers (ISBT 128).
biologicalSourceEventIdentifier0..1Source collection event (DIN).
processingFacilityReference(Organization)[]0..*Processing facility.
divisionstring0..1Specific division of the bag.
productStatusCoding0..1Status (available, unavailable).
expirationDatedateTime0..1Expiry date.
collectionBackboneElement0..1Donor, collector, date.
storageBackboneElement[]0..*Temperature, duration, scale.

JSON example

Red blood cell bag labelled with ISBT 128:

json biologicallyderivedproduct-example.json
{
  "resourceType": "BiologicallyDerivedProduct",
  "id": "example-rbc-unit",
  "productCategory": {
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/biologicallyderived-productcategory",
      "code": "organ",
      "display": "Blood, Sub-component or Derivative"
    }]
  },
  "productCode": {
    "coding": [{
      "system": "http://terminology.hl7.org/CodeSystem/v2-0913",
      "code": "RBC",
      "display": "Red Blood Cells"
    }]
  },
  "productStatus": {
    "coding": [{
      "system": "http://hl7.org/fhir/biologicallyderived-productstatus",
      "code": "available"
    }]
  },
  "identifier": [{
    "system": "https://www.iccbba.org/isbt-128",
    "value": "A99991234567890"
  }],
  "biologicalSourceEvent": {
    "system": "https://hospital01.example.org/donation",
    "value": "DON-2026-04501"
  },
  "expirationDate": "2026-06-19",
  "collection": {
    "collector": {
      "reference": "Practitioner/donor-collector"
    },
    "source": {
      "reference": "Patient/donor-12345"
    },
    "collectedDateTime": "2026-05-15T14:30:00+00:00"
  },
  "storage": [{
    "description": "Stored at 4°C, continuous agitation",
    "temperature": 4,
    "scale": "celsius",
    "duration": {
      "start": "2026-05-15T15:00:00+00:00"
    }
  }]
}

Common pitfalls

  • Identifier without ISBT 128: prevents cross-facility consolidation and targeted recall on donor issues.
  • Missing storage: cold chain is critical for RBC and platelets. A breach invalidates the unit.
  • BiologicalSourceEvent vs Patient/donor: the donation event is distinct from donor identity — separation crucial for anonymity.