Generated Narrative: StructureDefinition profile-RequestOrchestration-for-RequestGroup Name Flags Card. Type Description & Constraints RequestGroup 0..* RequestGroup A group of related requests #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:instantiatesUri 0..* uri R5: Instantiates external protocol or definition (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.instantiatesUri #xD; extension:code 0..1 CodeableConcept R5: What's being requested/ordered (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.code Binding: R5ActionCodeForR3 (0.1.0) (example) #xD; extension:reason 0..* (Complex) R5: Why the request orchestration is needed additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.reason #xD; extension:goal 0..* Reference(Cross-version Profile for R5.Goal for use in FHIR STU3(0.1.0) | Goal) R5: What goals (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.goal #xD; definition #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:instantiatesCanonical 0..* uri R5: Instantiates FHIR protocol or definition additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.instantiatesCanonical #xD; basedOn #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:basedOn 0..* ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: basedOn additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; replaces #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:replaces 0..* ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: replaces additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; intent #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:intent 0..1 code R5: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.intent Binding: RequestIntent (required): Codes indicating the degree of authority/intentionality associated with a request. #xD; subject #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:subject 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: Who the request orchestration is about URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; context #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:encounter 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: Created as part of additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; author #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:author 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: Device or practitioner that authored the request orchestration URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; action #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:linkId 0..1 string R5: Pointer to specific item from the PlanDefinition (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.linkId #xD; extension:priority 0..1 code R5: routine | urgent | asap | stat (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.priority Binding: MedicationRequestPriority (required): Identifies the level of importance to be assigned to actioning the request. #xD; extension:goal 0..* Reference(Cross-version Profile for R5.Goal for use in FHIR STU3(0.1.0) | Goal) R5: What goals (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.goal #xD; extension:input 0..* (Complex) R5: Input data requirements (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.input #xD; extension:output 0..* (Complex) R5: Output data definition (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.output #xD; extension:timing 0..1 Age R5: timing additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.timing #xD; extension:location 0..1 (Complex) R5: Where it should happen (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.location #xD; extension:definition 0..1 uri R5: Description of the activity to be performed (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.definition #xD; extension:transform 0..1 uri R5: Transform to apply the template (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.transform #xD; extension:dynamicValue 0..* (Complex) R5: Dynamic aspects of the definition (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.dynamicValue #xD; relatedAction #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:endRelationship 0..1 code R5: before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.relatedAction.endRelationship Binding: ActionRelationshipType (required): Defines the types of relationships between actions. #xD; participant #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 code R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.participant.type Binding: R5ActionParticipantTypeForR3 (0.1.0) (required): The type of participant in the activity. #xD; extension:typeCanonical 0..1 uri R5: Who or what can participate (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.participant.typeCanonical #xD; extension:typeReference 0..1 Reference(Cross-version Profile for R5.CareTeam for use in FHIR STU3(0.1.0) | CareTeam | Cross-version Profile for R5.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R5.DeviceDefinition for use in FHIR STU3(0.1.0) | Basic | Cross-version Profile for R5.Endpoint for use in FHIR STU3(0.1.0) | Endpoint | Cross-version Profile for R5.Group for use in FHIR STU3(0.1.0) | Group | Cross-version Profile for R5.HealthcareService for use in FHIR STU3(0.1.0) | HealthcareService | Cross-version Profile for R5.Location for use in FHIR STU3(0.1.0) | Location | Cross-version Profile for R5.Organization for use in FHIR STU3(0.1.0) | Organization | Cross-version Profile for R5.Patient for use in FHIR STU3(0.1.0) | Patient | Cross-version Profile for R5.Practitioner for use in FHIR STU3(0.1.0) | Practitioner | Cross-version Profile for R5.PractitionerRole for use in FHIR STU3(0.1.0) | PractitionerRole | Cross-version Profile for R5.RelatedPerson for use in FHIR STU3(0.1.0) | RelatedPerson) R5: Who or what can participate (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.participant.typeReference #xD; extension:role 0..1 CodeableConcept R5: E.g. Nurse, Surgeon, Parent, etc (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.participant.role #xD; extension:function 0..1 CodeableConcept R5: E.g. Author, Reviewer, Witness, etc (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.participant.function Binding: R5ActionParticipantFunctionForR3 (0.1.0) (example) #xD; extension:actor 0..1 uri, Reference(Cross-version Profile for R5.CareTeam for use in FHIR STU3(0.1.0) | CareTeam | Cross-version Profile for R5.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R5.DeviceDefinition for use in FHIR STU3(0.1.0) | Basic | Cross-version Profile for R5.Endpoint for use in FHIR STU3(0.1.0) | Endpoint | Cross-version Profile for R5.Group for use in FHIR STU3(0.1.0) | Group | Cross-version Profile for R5.HealthcareService for use in FHIR STU3(0.1.0) | HealthcareService | Cross-version Profile for R5.Location for use in FHIR STU3(0.1.0) | Location | Cross-version Profile for R5.Organization for use in FHIR STU3(0.1.0) | Organization | Cross-version Profile for R5.Patient for use in FHIR STU3(0.1.0) | Patient | Cross-version Profile for R5.Practitioner for use in FHIR STU3(0.1.0) | Practitioner | Cross-version Profile for R5.PractitionerRole for use in FHIR STU3(0.1.0) | PractitionerRole | Cross-version Profile for R5.RelatedPerson for use in FHIR STU3(0.1.0) | RelatedPerson) R5: Who/what is participating? (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.participant.actor #xD; type #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 CodeableConcept R5: type additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-RequestOrchestration.action.type Binding: ActionType (extensible): The type of action to be performed. #xD; resource #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:resource 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: resource additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; Documentation for this format
Cross-version Profile for R5.RequestOrchestration for use in FHIR STU3
This cross-version profile allows R5 RequestOrchestration content to be represented via FHIR STU3 RequestGroup resources.
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".
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
contained.where(('#'+id in %resource.descendants().reference).not()).empty()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
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 may not always be associated with version changes to the resource.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
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).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource, and may 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 in formation 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.
R5: Instantiates external protocol or definition (new)
R5: `RequestOrchestration.instantiatesUri` (new:uri)
Element `RequestOrchestration.instantiatesUri` has a context of RequestGroup based on following the parent source element upwards and mapping to `RequestGroup`. Element `RequestOrchestration.instantiatesUri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
R5: What's being requested/ordered (new)
R5: `RequestOrchestration.code` (new:CodeableConcept)
Element `RequestOrchestration.code` has a context of RequestGroup based on following the parent source element upwards and mapping to `RequestGroup`. Element `RequestOrchestration.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This element can be used to provide a code that captures the meaning of the request orchestration as a whole, as opposed to the code of the action element, which captures the meaning of the individual actions within the request orchestration.
R5: Why the request orchestration is needed additional types
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 STU3 element `RequestGroup.reason[x]` as `RelatedTo`. The mappings for `RequestOrchestration.reason` do not cover the following types: CodeableReference. The target context `RequestGroup.reason[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `RequestGroup`.
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 STU3. 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. Usually modifier elements provide negation or qualification. In order 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.
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.
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 protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
R5: Instantiates FHIR protocol or definition additional types
R5: `RequestOrchestration.instantiatesCanonical` additional types (canonical) additional types from child elements (value)
Element `RequestOrchestration.instantiatesCanonical` is mapped to FHIR STU3 element `RequestGroup.definition` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.instantiatesCanonical` do not cover the following types: canonical. The mappings for `RequestOrchestration.instantiatesCanonical` do not cover the following types based on type expansion: value.
Literal reference, Relative, internal or absolute URL
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.
Logical reference, when literal reference is not known
An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity 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.
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.
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.
R5: `RequestOrchestration.basedOn` additional types from child elements (display, identifier, reference, type)
Element `RequestOrchestration.basedOn` is mapped to FHIR STU3 element `RequestGroup.basedOn` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.basedOn` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `RequestOrchestration.basedOn` with unmapped reference targets: Resource.
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.
R5: `RequestOrchestration.replaces` additional types from child elements (display, identifier, reference, type)
Element `RequestOrchestration.replaces` is mapped to FHIR STU3 element `RequestGroup.replaces` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.replaces` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `RequestOrchestration.replaces` with unmapped reference targets: Resource. 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.
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.
draft | active | suspended | cancelled | completed | entered-in-error | unknown
The current state of the request. For request groups, the status reflects the status of all the requests in the group.
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Codes identifying the stage lifecycle stage of a request
Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.
This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.
Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.
Codes indicating the degree of authority/intentionality associated with a request
unique id for the element within a resource (for internal references)
R5: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Element `RequestOrchestration.intent` is mapped to FHIR STU3 element `RequestGroup.intent` as `SourceIsBroaderThanTarget`. The target context `RequestGroup.intent` is a modifier element, so this extension does not need to be defined as a modifier.
Indicates how quickly the request should be addressed with respect to other requests.
If missing, this request should be performed with normal priority
Identifies the level of importance to be assigned to actioning the request
The subject for which the request group was created.
R5: Who the request orchestration is about
Element `RequestOrchestration.subject` is mapped to FHIR STU3 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, Group, HealthcareService, Location, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson.
Encounter or Episode for the request group
Describes the context of the request group, if any.
R5: `RequestOrchestration.encounter` additional types from child elements (display, identifier, reference, type)
Element `RequestOrchestration.encounter` is mapped to FHIR STU3 element `RequestGroup.context` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.encounter` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `RequestOrchestration.encounter` with unmapped reference targets: Encounter.
Indicates when the request group was created.
Device or practitioner that authored the request group
Provides a reference to the author of the request group.
R5: Device or practitioner that authored the request orchestration
Element `RequestOrchestration.author` is mapped to FHIR STU3 element `RequestGroup.author` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `RequestOrchestration.author` with unmapped reference targets: Device, Practitioner, PractitionerRole.
Indicates the reason the request group was created. This is typically provided as a parameter to the evaluation and echoed by the service, although for some use cases, such as subscription- or event-based scenarios, it may provide an indication of the cause for the response.
Provides a mechanism to communicate additional information about the response.
The actions, if any, produced by the evaluation of the artifact.
Must have resource or action but not both
R5: Pointer to specific item from the PlanDefinition (new)
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 STU3. Typically, this is because the element has been added (is a new element).
R5: routine | urgent | asap | stat (new)
R5: `RequestOrchestration.action.priority` (new:code)
Element `RequestOrchestration.action.priority` has a context of RequestGroup.action based on following the parent source element upwards and mapping to `RequestGroup`. Element `RequestOrchestration.action.priority` has no mapping targets in FHIR STU3. 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 STU3. 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 STU3. 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 STU3. Typically, this is because the element has been added (is a new element).
R5: `RequestOrchestration.action.timing[x]` additional types (Age)
Element `RequestOrchestration.action.timing[x]` is mapped to FHIR STU3 element `RequestGroup.action.timing[x]` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.action.timing[x]` do not cover the following types: Age. The target context `RequestGroup.action.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `RequestGroup.action`. The intent of the timing element is to provide timing for when the action should be performed. The timing may be absolute (specified as a dateTime or Period) or relative (specified as an Age, Duration, or Range), or it may be a more complex, potentially repeating timing specified using Timing.
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 STU3. 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: Description of the activity to be performed (new)
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 STU3. 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: Transform to apply the template (new)
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 STU3. 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: Dynamic aspects of the definition (new)
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 STU3. 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 that contains it. Usually modifier elements provide negation or qualification. In order 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.
User-visible label for the action (e.g. 1. or A.)
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.
Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system
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 may not be capable of interpreting it dynamically.
Code representing the meaning of the action or sub-actions
A code that provides meaning for the action or action group. For example, a section may have a LOINC code for a the section of a documentation template.
Supporting documentation for the intended performer of the action
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.
Additional Content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. In order 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.
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 when enter/exit criteria for an action.
Natural language description of the condition
A brief, natural language description of the condition that effectively communicates the intended semantics.
The media type of the language for the expression.
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".
R5: before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end (new)
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 STU3. Typically, this is because the element has been added (is a new element).
The element id of the action this is related to.
before-start | before | before-end | concurrent-with-start | concurrent | concurrent-with-end | after-start | after | after-end
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.
R5: careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson (new)
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 STU3. 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 STU3. 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 STU3. 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: E.g. Nurse, Surgeon, Parent, etc (new)
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 STU3. Typically, this is because the element has been added (is a new element).
R5: E.g. Author, Reviewer, Witness, etc (new)
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 STU3. 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 STU3. Typically, this is because the element has been added (is a new element).
The type of action to perform (create, update, remove).
R5: `RequestOrchestration.action.type` additional types (CodeableConcept) additional types from child elements (text)
Element `RequestOrchestration.action.type` is mapped to FHIR STU3 element `RequestGroup.action.type` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.action.type` do not cover the following types: CodeableConcept. The mappings for `RequestOrchestration.action.type` do not cover the following types based on type expansion: text.
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
visual-group | logical-group | sentence-group
Defines the grouping behavior for the action and its children.
Defines organization behavior of a group
any | all | all-or-none | exactly-one | at-most-one | one-or-more
Defines the selection behavior for the action and its children.
Defines the requiredness behavior for the action.
Defines requiredness behavior for selecting an action or an action group
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](http://hl7.org/fhir/STU3/request.html) resource with a Request.intent set to "option".
R5: `RequestOrchestration.action.resource` additional types from child elements (display, identifier, reference, type)
Element `RequestOrchestration.action.resource` is mapped to FHIR STU3 element `RequestGroup.action.resource` as `SourceIsBroaderThanTarget`. The mappings for `RequestOrchestration.action.resource` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `RequestOrchestration.action.resource` with unmapped reference targets: Resource. The target resource SHALL be a [Request](https://hl7.org/fhir/request.html) resource with a Request.intent set to "option".