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 reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

R5: BiologicallyDerivedProduct.biologicalSourceEvent (new:Identifier)

Element BiologicallyDerivedProduct.biologicalSourceEvent has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.biologicalSourceEvent has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.

R5: BiologicallyDerivedProduct.processingFacility (new:Reference(Organization))

Element BiologicallyDerivedProduct.processingFacility has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.processingFacility has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.division (new:string)

Element BiologicallyDerivedProduct.division has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.division has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.expirationDate (new:dateTime)

Element BiologicallyDerivedProduct.expirationDate has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.expirationDate has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.storageTempRequirements (new:Range)

Element BiologicallyDerivedProduct.storageTempRequirements has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.storageTempRequirements has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May be extracted from information held in the Product Description Code.

R5: BiologicallyDerivedProduct.property (new:BackboneElement)

Element BiologicallyDerivedProduct.property has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.property has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Property can be used to provide information on a wide range of additional information specific to a particular biologicallyDerivedProduct.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

R5: BiologicallyDerivedProduct.biologicalSourceEvent (new:Identifier)

Element BiologicallyDerivedProduct.biologicalSourceEvent has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.biologicalSourceEvent has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.

R5: BiologicallyDerivedProduct.processingFacility (new:Reference(Organization))

Element BiologicallyDerivedProduct.processingFacility has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.processingFacility has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.division (new:string)

Element BiologicallyDerivedProduct.division has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.division has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.expirationDate (new:dateTime)

Element BiologicallyDerivedProduct.expirationDate has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.expirationDate has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.storageTempRequirements (new:Range)

Element BiologicallyDerivedProduct.storageTempRequirements has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.storageTempRequirements has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May be extracted from information held in the Product Description Code.

R5: BiologicallyDerivedProduct.property (new:BackboneElement)

Element BiologicallyDerivedProduct.property has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.property has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Property can be used to provide information on a wide range of additional information specific to a particular biologicallyDerivedProduct.

R5: BiologicallyDerivedProduct.productCategory additional types (Coding) additional types from child elements (userSelected)

Element BiologicallyDerivedProduct.productCategory is mapped to FHIR R4 element BiologicallyDerivedProduct.productCategory as SourceIsBroaderThanTarget. The mappings for BiologicallyDerivedProduct.productCategory do not cover the following types: Coding. The mappings for BiologicallyDerivedProduct.productCategory do not cover the following types based on type expansion: userSelected.

R5: BiologicallyDerivedProduct.productStatus additional types (Coding) additional types from child elements (userSelected)

Element BiologicallyDerivedProduct.productStatus is mapped to FHIR R4 element BiologicallyDerivedProduct.status as SourceIsBroaderThanTarget. The mappings for BiologicallyDerivedProduct.productStatus do not cover the following types: Coding. The mappings for BiologicallyDerivedProduct.productStatus do not cover the following types based on type expansion: userSelected.

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.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

The codes SHOULD be taken from CommonLanguages
(preferred to http://hl7.org/fhir/ValueSet/languages|4.0.1)

A human language.

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

R5: BiologicallyDerivedProduct.biologicalSourceEvent (new:Identifier)

Element BiologicallyDerivedProduct.biologicalSourceEvent has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.biologicalSourceEvent has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.

R5: BiologicallyDerivedProduct.processingFacility (new:Reference(Organization))

Element BiologicallyDerivedProduct.processingFacility has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.processingFacility has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.division (new:string)

Element BiologicallyDerivedProduct.division has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.division has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.expirationDate (new:dateTime)

Element BiologicallyDerivedProduct.expirationDate has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.expirationDate has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: BiologicallyDerivedProduct.storageTempRequirements (new:Range)

Element BiologicallyDerivedProduct.storageTempRequirements has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.storageTempRequirements has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May be extracted from information held in the Product Description Code.

R5: BiologicallyDerivedProduct.property (new:BackboneElement)

Element BiologicallyDerivedProduct.property has a context of BiologicallyDerivedProduct based on following the parent source element upwards and mapping to BiologicallyDerivedProduct. Element BiologicallyDerivedProduct.property has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Property can be used to provide information on a wide range of additional information specific to a particular biologicallyDerivedProduct.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

This records identifiers associated with this biologically derived product instance that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

Broad category of this product.

Biologically Derived Product Category.

unique id for the element within a resource (for internal references)

An Extension

R5: BiologicallyDerivedProduct.productCategory additional types (Coding) additional types from child elements (userSelected)

Element BiologicallyDerivedProduct.productCategory is mapped to FHIR R4 element BiologicallyDerivedProduct.productCategory as SourceIsBroaderThanTarget. The mappings for BiologicallyDerivedProduct.productCategory do not cover the following types: Coding. The mappings for BiologicallyDerivedProduct.productCategory do not cover the following types based on type expansion: userSelected.

Primitive value for code

A code that identifies the kind of this biologically derived product (SNOMED Ctcode).

Biologically Derived Product Code.

Whether the product is currently available.

Biologically Derived Product Status.

unique id for the element within a resource (for internal references)

An Extension

R5: BiologicallyDerivedProduct.productStatus additional types (Coding) additional types from child elements (userSelected)

Element BiologicallyDerivedProduct.productStatus is mapped to FHIR R4 element BiologicallyDerivedProduct.status as SourceIsBroaderThanTarget. The mappings for BiologicallyDerivedProduct.productStatus do not cover the following types: Coding. The mappings for BiologicallyDerivedProduct.productStatus do not cover the following types based on type expansion: userSelected.

Primitive value for code

Procedure request to obtain this biologically derived product.

Number of discrete units within this product.

Parent product (if any).

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.

How this product was collected.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Healthcare professional who is performing the collection.

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

Time of product collection.

Any processing of the product during collection that does not change the fundamental nature of the product. For example adding anti-coagulants during the collection of Peripheral Blood Stem Cells.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Description of of processing.

Procesing code.

Biologically Derived Product Procedure.

Substance added during processing.

Time of processing.

Any manipulation of product post-collection that is intended to alter the product. For example a buffy-coat enrichment or CD8 reduction of Peripheral Blood Stem Cells to make it more suitable for infusion.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Description of manipulation.

Time of manipulation.

Product storage.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Description of storage.

Storage temperature.

Temperature scale used.

BiologicallyDerived Product Storage Scale.

Storage timeperiod.