- FHIR Biologically Derived Product Resource
- Electronic Health Records Exchange Through FHIR
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
Biologically Derived Product
Biologically Derived Product is 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.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
A material substance originating from a biological entity intended to be transplanted or infused into another (possibly the same) biological entity.
– hematopoietic stem cells (bone marrow, peripheral blood, or cord blood extraction)
– blood (whole, extracted cells, plasma, etc.)
– tissues (porcine valves, skin, bovine cardiac tissue, etc.)
– manipulated cells (e.g. CAR T-cells)
The workflow using this resource (e.g., request, administration) should be discussed and implemented in a consistent way as other similar resources are handled (e.g., device, medication)
– Boundaries and Relationships
This resource relates to these other resource:
– Procedure Request (for collection)
– Patient (“receiver” and “source”)
– Practitioner (who collected product)
– Substance (product processing) American Medical Informatics Association (AMIA)
– Diagnostic Report (containing HLA-typing)
– Biologically Derived Product (“parent” product for multi-day collections)
– Procedure (one for collection and one for transplantation, will need to add BiologicallyDerivedProduct to the “usedReference”)
Fast Healthcare Interoperability Resources (FHIR) is a draft standard describing data formats and elements (known as “resources”) and an application programming interface (API) for exchanging electronic health records. The standard was created by the Health Level Seven International (HL7) health-care standards organization.
Its goal is to facilitate interoperation between legacy healthcare systems, to make it easy to provide healthcare information to healthcare providers and individuals on a wide variety of devices from computers to tablets to cell phones, and to allow third-party application developers to provide medical applications which can be easily integrated into existing systems.
FHIR provides an alternative to document-centric approaches by directly exposing discrete data elements as services. For example, basic elements of healthcare like patients, admissions, diagnostic reports and medications can each be retrieved and manipulated via their own resource URLs (Uniform Resource Locators). FHIR was supported at an American Medical Informatics Association meeting by many EHR (Electronic Health Record) vendors which value its open and extensible nature.
About this Dataset
John Snow Labs; Health Level Seven International;
|Source License URL
|Source License Requirements
FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR
FHIR Biologically Derived Product Resource, Electronic Health Records Exchange Through FHIR
|Name of the concept in the FHIR structure
|required : 1
|A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.
|The type the structure describes.
|A free text natural language description of the structure and its use
|The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.
|The enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique.
|The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.
|The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.
|Computer Ready Name
|This is a BiologicallyDerivedProduct resource
|The logical id of the resource
|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
|Extensions for implicitRules
|The base language in which the resource is written.
|Extensions for 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
|These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently
|May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable