This resource reflects an instance of a biologically derived product. A material substance originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.

Substances include, but are not limited to: whole blood, bone marrow, organs, and manipulated blood cells.

A category or classification of the product. Products may be assigned multiple categories, for example a human heart valve can be categorized as an 'MPHO' and 'tissue'.

A codified value that systematically supports characterization and classification of medical products of human origin inclusive of processing conditions such as additives, volumes and handling conditions.

Parent product (if any) for this biologically-derived product.

For products that have multiple collections. For example Peripheral Blood Stem Cells may be collected over several days from a single donor and the donation split into in multiple containers which must be linked to the parent donation.

Request to obtain and/or infuse this biologically derived product.

Unique instance identifiers assigned to a biologically derived product. Note: This is a business identifier, not a resource identifier.

This identifier should uniquely identify the product instance in the business domain. Ideally it should be a globally unique identifier under the control of an ISO/IEC 15459 Issuing Agency.

A shared identifier common to multiple independent BiologicallyDerivedProduct instances that are intended to be administered in the course of the same given therapy. The presence of the same identifier on each BiologicallyDerivedProduct ties those products together.

An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled.

Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.

Processing facilities responsible for the labeling and distribution of this biologically derived product.

A unique identifier for an aliquot of a product. Used to distinguish individual aliquots of a product carrying the same biologicalSource and productCode identifiers.

The current status of the product.

Date, and where relevant time, of expiration.

How this product was collected.

Healthcare professional who is performing the collection.

The patient providing the product.

The collection.source may reference an identifiable patient. Implementers shall ensure the appropriate data access controls are established.

The entity, such as a hospital or vendor in the case of a processed/manipulated/manufactured product, providing the product.

Time of product collection.

The procedure performed to collect the biologically derived product.

The temperature requirements for storage of the biologically-derived product.

May be extracted from information held in the productCode element.

A property that is specific to this BiologicallyDerviedProduct instance.

Property can be used to provide information on a wide range of additional information specific to a particular biologicallyDerivedProduct.

Code that specifies the property. It should reference an established coding system.

The element is identified by name and system URI in the type. Some types may have multiple occurrences.

Property values.

The value should be provided as a boolean, integer, CodeableConcept, period, quantity, range, ratio, or attachment. The description can be a string only when these others are not available.