A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". A set 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 element is present, it must have either a @value, an @id, or extensions Allows a service to provide a unique, business identifier for the request. 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. Completed or terminated request(s) whose function is taken by this new request. A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time. The current state of the request. For request orchestrations, the status reflects the status of all the requests in the orchestration. Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain. Indicates how quickly the request should be addressed with respect to other requests. A code that identifies what the overall request orchestration is. The subject for which the request orchestration was created. Describes the context of the request orchestration, if any. Indicates when the request orchestration was created. Provides a reference to the author of the request orchestration. Describes the reason for the request orchestration in coded or textual form. Goals that are intended to be achieved by following the requests in this RequestOrchestration. Provides a mechanism to communicate additional information about the response. The actions, if any, produced by the evaluation of the artifact. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". The linkId of the action from the PlanDefinition that corresponds to this action in the RequestOrchestration resource. A user-visible prefix for the action. For example a section or item numbering such as 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. 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. 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. Goals that are intended to be achieved by following the requests in this action. An expression that describes applicability criteria, or start/stop conditions for the action. Defines input data requirements for the action. Defines the outputs of the action, if any. A relationship to another action such as "before" or "30-60 minutes after start of". An optional value describing when the action should be performed. Identifies the facility where the action will occur; e.g. home, hospital, specific clinic, etc. The participant that should perform or be responsible for this action. The type of action to perform (create, update, remove). All - meaning the applicability of each child action is evaluated independently; if a child action is applicable according to the applicability criteria, it is applied. Any - meaning that each child action is evaluated in order, and the first action that returns an applicability of true will be applied, and processing of the parent action will stop. If not specified, the default behavior of All is used. Defines the grouping behavior for the action and its children. Defines the selection behavior for the action and its children. Defines expectations around whether an action is required. Defines whether the action should usually be preselected. Defines whether the action can be selected multiple times. The resource that is the target of the action (e.g. CommunicationRequest). A reference to an ActivityDefinition that describes the action to be taken in detail, a Measure that specifies a measure to be evaluated, a MessageDefinition that specifies a message to be sent, a PlanDefinition that describes a series of actions to be taken, a Questionnaire that should be filled out, a SpecimenDefinition describing a specimen to be collected, an ObservationDefinition that specifies what observation should be captured, or an OperationDefinition that specifies what operation should be invoked. When the value is a uri, it is intended to be a reference to non-FHIR content that characterizes the action to be performed. This option is allowed to enable the PlanDefinition to be used to provide semi-structured representation, when the guidance is not computable, but there is still value in elaborating the overall structure with a PlanDefinition. The intended behavior when a definitionUri is realized as part of an apply is that it is copied to the resulting RequestOrchestration so that it is available to the consuming system. How that system interprets that uri is not specified. A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input. Customizations that should be applied to the statically defined resource. For example, if the dosage of a medication must be computed based on the patient's weight, a customization would be used to specify an expression that calculated the weight, and the path on the resource that would contain the result. Sub actions. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". The kind of condition. An expression that returns true or false, indicating whether or not the condition is satisfied. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". A human-readable label for the data requirement used to label data flows in BPMN or similar diagrams. Also provides a human readable label when rendering the data requirement that conveys its purpose to human readers. Defines the data that is to be provided as input to the action. Points to an existing input or output element that provides data to this input. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". A human-readable label for the data requirement used to label data flows in BPMN or similar diagrams. Also provides a human readable label when rendering the data requirement that conveys its purpose to human readers. Defines the data that results as output from the action. Points to an existing input or output element that is results as output from the action. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". The element id of the target related action. The relationship of this action to the related action. The relationship of the end of this action to the related action. A duration or range of durations to apply to the relationship. For example, 30-60 minutes before. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". The type of participant in the action. The type of participant in the action. The type of participant in the action. The role the participant should play in performing the described action. Indicates how the actor will be involved in the action - author, reviewer, witness, etc. A reference to the actual participant. A set of related requests that can be used to capture intended activities that have inter-dependencies such as "give this medication after that one". The path to the element to be customized. This is the path on the resource that will hold the result of the calculation defined by the expression. The specified path SHALL be a FHIRPath resolvable on the specified target type of the ActivityDefinition, and SHALL consist only of identifiers, constant indexers, and a restricted subset of functions. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details). An expression specifying the value of the customized element.