OO Incubator Implementation Guide, published by HL7 International / Orders and Observations. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/oo-incubator/ and changes regularly. See the Directory of published versions

IG Home

Official URL: http://hl7.org/fhir/uv/oo-incubator/ImplementationGuide/hl7.fhir.uv.oo-incubator				Version: 0.1.0	Highlight text changes?
IG Standards status: Trial-use				Maturity Level: 1	Computable Name: OOIncubatorImplementationGuide

OO Incubator

The Orders & Observations (OO) Incubator Implementation Guide serves as a consolidated workspace for emerging specifications, including FHIR resources, profiles, operations, vocabularies, and artifacts developed by the HL7 Orders & Observations Work Group. It includes resources that are actively evolving and have not yet reached normative status under the FHIR Maturity Model, but may still be suitable for trial use, pilot implementations, and even production deployments where appropriate. These artifacts reflect the current direction of ongoing work but should not be interpreted as stable normative specifications.

Implementers may choose to use these artifacts for trial use, pilot testing, or even production deployments, but should do so with the understanding that:

• Artifacts may change significantly as they progress through the FHIR Maturity Model
• Backward compatibility is not guaranteed
• Items may be promoted into official HL7 balloted specifications, or removed if superseded or no longer aligned with Work Group direction
• Implementer feedback is a critical input and may directly influence future revisions

This IG defines the scope of exploration for the Orders & Observations Work Group and provides early visibility into emerging content. Implementers are encouraged to assess their risk tolerance, track updates regularly, and participate in the standards development process where possible.

Migrated Resources

MedicalProductOfHumanOrigin	This profile is designed for biologically derived products that are derived from a human donor and intended for clinical application in a human recipient. Donor and recipient might, or might not, be the same individual. Products of this nature are referred to as medical products of human origin (MPHO) and have specific traceability requirements to ensure that the bi-directional link between donor and recipient is maintained. The profile specifies the essential identifiers for traceability as required elements.
BiologicallyDerivedProductDispense	A record of dispensation of a biologically derived product.
DeviceDispense	Indicates that a device is to be or has been dispensed for a named person/patient. This includes a description of the product (supply) provided and the instructions for using the device.
DeviceUsage	A record of a device being used by a patient where the record is the result of a report from the patient or a clinician.
InventoryItem	functional description of an inventory item used in inventory and supply-related workflows.
InventoryReport	A report of inventory or stock items.
SupplyDelivery	Record of delivery of what is supplied.
SupplyRequest	A record of a non-patient specific request for a medication, substance, device, certain types of biologically derived product, and nutrition product used in the healthcare setting.
Transport	Record of transport.

Migrated Profiles

These profiles do not have a parent Resource in the Incubator and instead further extend FHIR Core resources.

MedicalProductOfHumanOrigin

This profile is designed for biologically derived products that are derived from a human donor and intended for clinical application in a human recipient. Donor and recipient might, or might not, be the same individual. Products of this nature are referred to as medical products of human origin (MPHO) and have specific traceability requirements to ensure that the bi-directional link between donor and recipient is maintained. The profile specifies the essential identifiers for traceability as required elements.

IP Statements

This publication includes IP covered under the following statements.

• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): Condition/cond-example, DeviceUsage, SNOMEDCTSupplyItemValueSet, SupplyRequest and SupplyRequestWhenValueSet
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  • Condition Category Codes: Condition/cond-example
  • Condition Clinical Status Codes: Condition/cond-example
  • ConditionVerificationStatus: Condition/cond-example
  • Location type: City Hospital Lab Location, Hospital Lab, Lab A and Lab A Location
  • Supply Item Type: TransportTypeValueSet
  • Supply Type: SupplyRequest and SupplyTypeValueSet
  • SupplyRequestReason: SupplyRequest and SupplyRequestReasonValueSet
  • event: Transport and TransportReasonValueSet
  • contactRole2: Patient/pat-example and Patient/pat1
  • identifierType: Patient/pat-example and Patient/pat1
  • RoleCode: Hospital Lab and Lab A