A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one".

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: RequestOrchestration.reason additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Condition), CodeableReference(http://hl7.org/fhir/StructureDefinition/Observation), CodeableReference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport), CodeableReference(http://hl7.org/fhir/StructureDefinition/DocumentReference))

Element RequestOrchestration.reason is mapped to FHIR R4 element RequestGroup.reasonCode as SourceIsBroaderThanTarget. Element RequestOrchestration.reason is mapped to FHIR R4 element RequestGroup.reasonReference as SourceIsBroaderThanTarget. The mappings for RequestOrchestration.reason do not cover the following types: CodeableReference.

R5: RequestOrchestration.goal (new:Reference(Goal))

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

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.

The current state of the request. For request groups, the status reflects the status of all the requests in the group.

Codes identifying the lifecycle stage of a request.

Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.

Codes indicating the degree of authority/intentionality associated with a request.

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

R5: RequestOrchestration.reason additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Condition), CodeableReference(http://hl7.org/fhir/StructureDefinition/Observation), CodeableReference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport), CodeableReference(http://hl7.org/fhir/StructureDefinition/DocumentReference))

Element RequestOrchestration.reason is mapped to FHIR R4 element RequestGroup.reasonCode as SourceIsBroaderThanTarget. Element RequestOrchestration.reason is mapped to FHIR R4 element RequestGroup.reasonReference as SourceIsBroaderThanTarget. The mappings for RequestOrchestration.reason do not cover the following types: CodeableReference.

R5: RequestOrchestration.goal (new:Reference(Goal))

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

R5: RequestOrchestration.subject

Element RequestOrchestration.subject is mapped to FHIR R4 element RequestGroup.subject as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element RequestOrchestration.subject with unmapped reference targets: CareTeam, Device, HealthcareService, Location, Organization, Practitioner, PractitionerRole, RelatedPerson.

R5: RequestOrchestration.action.linkId (new:string)

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

R5: RequestOrchestration.action.goal (new:Reference(Goal))

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

R5: RequestOrchestration.action.input (new:BackboneElement)

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

R5: RequestOrchestration.action.output (new:BackboneElement)

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

R5: RequestOrchestration.action.location (new:CodeableReference(Location))

Element RequestOrchestration.action.location has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.location has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May reference a specific clinical location or may just identify a type of location.

R5: RequestOrchestration.action.definition[x] (new:canonical(ActivityDefinition,ObservationDefinition,PlanDefinition,Questionnaire,SpecimenDefinition), uri)

Element RequestOrchestration.action.definition[x] has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.definition[x] has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that the definition is optional, and if no definition is specified, a dynamicValue with a root ($this) path can be used to define the entire resource dynamically.

R5: RequestOrchestration.action.transform (new:canonical(StructureMap))

Element RequestOrchestration.action.transform has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.transform has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that when a referenced ActivityDefinition also defines a transform, the transform specified here generally takes precedence. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.

R5: RequestOrchestration.action.dynamicValue (new:BackboneElement)

Element RequestOrchestration.action.dynamicValue has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.dynamicValue has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Dynamic values are applied in the order in which they are defined in the RequestOrchestration resource. Note that when dynamic values are also specified by a referenced ActivityDefinition, the dynamicValues from the ActivityDefinition are applied first, followed by the dynamicValues specified here. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.

R5: RequestOrchestration.action.relatedAction.endRelationship (new:code)

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

R5: RequestOrchestration.action.participant.type (new:code)

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

R5: RequestOrchestration.action.participant.typeCanonical (new:canonical(CapabilityStatement))

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

R5: RequestOrchestration.action.participant.typeReference (new:Reference(CareTeam,Device,DeviceDefinition,Endpoint,Group,HealthcareService,Location,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))

Element RequestOrchestration.action.participant.typeReference has a context of RequestGroup.action.participant based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.participant.typeReference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).

R5: RequestOrchestration.action.participant.role (new:CodeableConcept)

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

R5: RequestOrchestration.action.participant.function (new:CodeableConcept)

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

R5: RequestOrchestration.action.participant.actor[x] (new:canonical(CapabilityStatement), Reference(CareTeam,Device,DeviceDefinition,Endpoint,Group,HealthcareService,Location,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))

Element RequestOrchestration.action.participant.actor[x] has a context of RequestGroup.action.participant based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.participant.actor[x] has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

A group of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one".

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: RequestOrchestration.reason additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/Condition), CodeableReference(http://hl7.org/fhir/StructureDefinition/Observation), CodeableReference(http://hl7.org/fhir/StructureDefinition/DiagnosticReport), CodeableReference(http://hl7.org/fhir/StructureDefinition/DocumentReference))

Element RequestOrchestration.reason is mapped to FHIR R4 element RequestGroup.reasonCode as SourceIsBroaderThanTarget. Element RequestOrchestration.reason is mapped to FHIR R4 element RequestGroup.reasonReference as SourceIsBroaderThanTarget. The mappings for RequestOrchestration.reason do not cover the following types: CodeableReference.

R5: RequestOrchestration.goal (new:Reference(Goal))

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

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.

Allows a service to provide a unique, business identifier for the request.

Allows identification of the request as it is known by various participating systems and in a way that remains consistent across servers.

A canonical URL referencing a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.

A URL referencing an externally defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.

A plan, proposal or order that is fulfilled in whole or in part by this request.

Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.

Completed or terminated request(s) whose function is taken by this new request.

The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.

Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.

A shared identifier common to all requests that were authorized more or less simultaneously by a single author, representing the identifier of the requisition, prescription or similar form.

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

Some business processes need to know if multiple items were ordered as part of the same "prescription" or "requisition" for billing or other purposes.

The current state of the request. For request groups, the status reflects the status of all the requests in the group.

Codes identifying the lifecycle stage of a request.

Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.

Codes indicating the degree of authority/intentionality associated with a request.

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

Indicates how quickly the request should be addressed with respect to other requests.

Identifies the level of importance to be assigned to actioning the request.

A code that identifies what the overall request group is.

This element can be used to provide a code that captures the meaning of the request group as a whole, as opposed to the code of the action element, which captures the meaning of the individual actions within the request group.

The subject for which the request group was created.

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

An Extension

R5: RequestOrchestration.subject

Element RequestOrchestration.subject is mapped to FHIR R4 element RequestGroup.subject as SourceIsBroaderThanTarget. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element RequestOrchestration.subject with unmapped reference targets: CareTeam, Device, HealthcareService, Location, Organization, Practitioner, PractitionerRole, RelatedPerson.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|4.0.1)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Describes the context of the request group, if any.

Indicates when the request group was created.

Provides a reference to the author of the request group.

Describes the reason for the request group in coded or textual form.

Indicates another resource whose existence justifies this request group.

Provides a mechanism to communicate additional information about the response.

The actions, if any, produced by the evaluation of the artifact.

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

An Extension

R5: RequestOrchestration.action.linkId (new:string)

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

R5: RequestOrchestration.action.goal (new:Reference(Goal))

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

R5: RequestOrchestration.action.input (new:BackboneElement)

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

R5: RequestOrchestration.action.output (new:BackboneElement)

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

R5: RequestOrchestration.action.location (new:CodeableReference(Location))

Element RequestOrchestration.action.location has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.location has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May reference a specific clinical location or may just identify a type of location.

R5: RequestOrchestration.action.definition[x] (new:canonical(ActivityDefinition,ObservationDefinition,PlanDefinition,Questionnaire,SpecimenDefinition), uri)

Element RequestOrchestration.action.definition[x] has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.definition[x] has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that the definition is optional, and if no definition is specified, a dynamicValue with a root ($this) path can be used to define the entire resource dynamically.

R5: RequestOrchestration.action.transform (new:canonical(StructureMap))

Element RequestOrchestration.action.transform has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.transform has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that when a referenced ActivityDefinition also defines a transform, the transform specified here generally takes precedence. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.

R5: RequestOrchestration.action.dynamicValue (new:BackboneElement)

Element RequestOrchestration.action.dynamicValue has a context of RequestGroup.action based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.dynamicValue has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Dynamic values are applied in the order in which they are defined in the RequestOrchestration resource. Note that when dynamic values are also specified by a referenced ActivityDefinition, the dynamicValues from the ActivityDefinition are applied first, followed by the dynamicValues specified here. In addition, if both a transform and dynamic values are specific, the dynamic values are applied to the result of the transform.

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.

A user-visible prefix for the action.

The title of the action displayed to a user.

A short description of the action used to provide a summary to display to the user.

A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that might not be capable of interpreting it dynamically.

Indicates how quickly the action should be addressed with respect to other actions.

Identifies the level of importance to be assigned to actioning the request.

A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a section of a documentation template.

Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources.

An expression that describes applicability criteria, or start/stop conditions for the action.

When multiple conditions of the same kind are present, the effects are combined using AND semantics, so the overall condition is true only if all of the conditions are true.

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.

The kind of condition.

Applicability criteria are used to determine immediate applicability when a plan definition is applied to a given context. Start and stop criteria are carried through application and used to describe enter/exit criteria for an action.

The kind of condition for the action.

An expression that returns true or false, indicating whether or not the condition is satisfied.

The expression may be inlined, or may be a reference to a named expression within a logic library referenced by the library element.

A relationship to another action such as "before" or "30-60 minutes after start of".

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

An Extension

R5: RequestOrchestration.action.relatedAction.endRelationship (new:code)

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

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.

The element id of the action this is related to.

The relationship of this action to the related action.

Defines the types of relationships between actions.

A duration or range of durations to apply to the relationship. For example, 30-60 minutes before.

An optional value describing when the action should be performed.

The participant that should perform or be responsible for this action.

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

An Extension

R5: RequestOrchestration.action.participant.type (new:code)

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

R5: RequestOrchestration.action.participant.typeCanonical (new:canonical(CapabilityStatement))

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

R5: RequestOrchestration.action.participant.typeReference (new:Reference(CareTeam,Device,DeviceDefinition,Endpoint,Group,HealthcareService,Location,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))

Element RequestOrchestration.action.participant.typeReference has a context of RequestGroup.action.participant based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.participant.typeReference has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When this element is a reference, it SHOULD be a reference to a definitional resource (for example, a location type, rather than a specific location).

R5: RequestOrchestration.action.participant.role (new:CodeableConcept)

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

R5: RequestOrchestration.action.participant.function (new:CodeableConcept)

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

R5: RequestOrchestration.action.participant.actor[x] (new:canonical(CapabilityStatement), Reference(CareTeam,Device,DeviceDefinition,Endpoint,Group,HealthcareService,Location,Organization,Patient,Practitioner,PractitionerRole,RelatedPerson))

Element RequestOrchestration.action.participant.actor[x] has a context of RequestGroup.action.participant based on following the parent source element upwards and mapping to RequestGroup. Element RequestOrchestration.action.participant.actor[x] has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|4.0.1)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

The type of action to perform (create, update, remove).

The type of action to be performed.

Defines the grouping behavior for the action and its children.

Defines organization behavior of a group.

Defines the selection behavior for the action and its children.

Defines selection behavior of a group.

Defines expectations around whether an action is required.

Defines expectations around whether an action or action group is required.

Defines whether the action should usually be preselected.

Defines selection frequency behavior for an action or group.

Defines whether the action can be selected multiple times.

Defines behavior for an action or a group for how many times that item may be repeated.

The resource that is the target of the action (e.g. CommunicationRequest).

The target resource SHALL be a Request resource with a Request.intent set to "option".

Sub actions.