pub struct RequestOrchestrationAction {Show 57 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub link_id: Option<String>,
pub link_id_ext: Option<FieldExtension>,
pub prefix: Option<String>,
pub prefix_ext: Option<FieldExtension>,
pub title: Option<String>,
pub title_ext: Option<FieldExtension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub text_equivalent: Option<String>,
pub text_equivalent_ext: Option<FieldExtension>,
pub priority: Option<RequestPriority>,
pub priority_ext: Option<FieldExtension>,
pub code: Vec<Option<CodeableConcept>>,
pub code_ext: Vec<Option<FieldExtension>>,
pub documentation: Vec<Option<RelatedArtifact>>,
pub documentation_ext: Vec<Option<FieldExtension>>,
pub goal: Vec<Option<Reference>>,
pub goal_ext: Vec<Option<FieldExtension>>,
pub condition: Vec<Option<RequestOrchestrationActionCondition>>,
pub condition_ext: Vec<Option<FieldExtension>>,
pub input: Vec<Option<RequestOrchestrationActionInput>>,
pub input_ext: Vec<Option<FieldExtension>>,
pub output: Vec<Option<RequestOrchestrationActionOutput>>,
pub output_ext: Vec<Option<FieldExtension>>,
pub related_action: Vec<Option<RequestOrchestrationActionRelatedAction>>,
pub related_action_ext: Vec<Option<FieldExtension>>,
pub timing: Option<RequestOrchestrationActionTiming>,
pub timing_ext: Option<RequestOrchestrationActionTimingExtension>,
pub location: Option<CodeableReference>,
pub location_ext: Option<FieldExtension>,
pub participant: Vec<Option<RequestOrchestrationActionParticipant>>,
pub participant_ext: Vec<Option<FieldExtension>>,
pub type: Option<CodeableConcept>,
pub type_ext: Option<FieldExtension>,
pub grouping_behavior: Option<ActionGroupingBehavior>,
pub grouping_behavior_ext: Option<FieldExtension>,
pub selection_behavior: Option<ActionSelectionBehavior>,
pub selection_behavior_ext: Option<FieldExtension>,
pub required_behavior: Option<ActionRequiredBehavior>,
pub required_behavior_ext: Option<FieldExtension>,
pub precheck_behavior: Option<ActionPrecheckBehavior>,
pub precheck_behavior_ext: Option<FieldExtension>,
pub cardinality_behavior: Option<ActionCardinalityBehavior>,
pub cardinality_behavior_ext: Option<FieldExtension>,
pub resource: Option<Reference>,
pub resource_ext: Option<FieldExtension>,
pub definition: Option<RequestOrchestrationActionDefinition>,
pub definition_ext: Option<RequestOrchestrationActionDefinitionExtension>,
pub transform: Option<String>,
pub transform_ext: Option<FieldExtension>,
pub dynamic_value: Vec<Option<RequestOrchestrationActionDynamicValue>>,
pub dynamic_value_ext: Vec<Option<FieldExtension>>,
pub action: Vec<Option<RequestOrchestrationAction>>,
pub action_ext: Vec<Option<FieldExtension>>,
}Expand description
Sub-fields of the action field in RequestOrchestration
Fields§
§id: Option<String>Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
extension: Vec<Extension>Additional content defined by implementations
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 managable, 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.
modifier_extension: Vec<Extension>Extensions that cannot be ignored even if unrecognized
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 managable, 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.
link_id: Option<String>Pointer to specific item from the PlanDefinition
The linkId of the action from the PlanDefinition that corresponds to this action in the RequestOrchestration resource.
link_id_ext: Option<FieldExtension>Extension field.
prefix: Option<String>User-visible prefix for the action (e.g. 1. or A.)
A user-visible prefix for the action. For example a section or item numbering such as 1. or A.
prefix_ext: Option<FieldExtension>Extension field.
title: Option<String>User-visible title
The title of the action displayed to a user.
title_ext: Option<FieldExtension>Extension field.
description: Option<String>Short description of the action
A short description of the action used to provide a summary to display to the user.
description_ext: Option<FieldExtension>Extension field.
text_equivalent: Option<String>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 might not be capable of interpreting it dynamically.
text_equivalent_ext: Option<FieldExtension>Extension field.
priority: Option<RequestPriority>RequestPriority; routine | urgent | asap | stat
Indicates how quickly the action should be addressed with respect to other actions.
priority_ext: Option<FieldExtension>Extension field.
code: Vec<Option<CodeableConcept>>ActionCode; 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 section of a documentation template.
code_ext: Vec<Option<FieldExtension>>Extension field.
documentation: Vec<Option<RelatedArtifact>>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.
documentation_ext: Vec<Option<FieldExtension>>Extension field.
goal: Vec<Option<Reference>>What goals
Goals that are intended to be achieved by following the requests in this action.
goal_ext: Vec<Option<FieldExtension>>Extension field.
condition: Vec<Option<RequestOrchestrationActionCondition>>Whether or not the action is applicable
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.
condition_ext: Vec<Option<FieldExtension>>Extension field.
input: Vec<Option<RequestOrchestrationActionInput>>Input data requirements
Defines input data requirements for the action.
input_ext: Vec<Option<FieldExtension>>Extension field.
output: Vec<Option<RequestOrchestrationActionOutput>>Output data definition
Defines the outputs of the action, if any.
output_ext: Vec<Option<FieldExtension>>Extension field.
Relationship to another action
A relationship to another action such as “before” or “30-60 minutes after start of”.
Extension field.
timing: Option<RequestOrchestrationActionTiming>When the action should take place
An optional value describing when the action should be performed.
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.
timing_ext: Option<RequestOrchestrationActionTimingExtension>Extension field.
location: Option<CodeableReference>Where it should happen
Identifies the facility where the action will occur; e.g. home, hospital, specific clinic, etc.
May reference a specific clinical location or may just identify a type of location.
location_ext: Option<FieldExtension>Extension field.
participant: Vec<Option<RequestOrchestrationActionParticipant>>Who should perform the action
The participant that should perform or be responsible for this action.
Because request orchestrations represent potential options for performing activities, some specific participants may still be unknown, so this element allows for both definitional participants (in the same way they are specified in ActivityDefinition and PlanDefinition resources) as well as identifying specific participants when they are known.
participant_ext: Vec<Option<FieldExtension>>Extension field.
type: Option<CodeableConcept>ActionType; create | update | remove | fire-event
The type of action to perform (create, update, remove).
type_ext: Option<FieldExtension>Extension field.
grouping_behavior: Option<ActionGroupingBehavior>ActionGroupingBehavior; visual-group | logical-group | sentence-group
Defines the grouping behavior for the action and its children.
grouping_behavior_ext: Option<FieldExtension>Extension field.
selection_behavior: Option<ActionSelectionBehavior>ActionSelectionBehavior; any | all | all-or-none | exactly-one | at-most-one | one-or-more
Defines the selection behavior for the action and its children.
selection_behavior_ext: Option<FieldExtension>Extension field.
required_behavior: Option<ActionRequiredBehavior>ActionRequiredBehavior; must | could | must-unless-documented
Defines expectations around whether an action is required.
required_behavior_ext: Option<FieldExtension>Extension field.
precheck_behavior: Option<ActionPrecheckBehavior>ActionPrecheckBehavior; yes | no
Defines whether the action should usually be preselected.
precheck_behavior_ext: Option<FieldExtension>Extension field.
cardinality_behavior: Option<ActionCardinalityBehavior>ActionCardinalityBehavior; single | multiple
Defines whether the action can be selected multiple times.
cardinality_behavior_ext: Option<FieldExtension>Extension field.
resource: Option<Reference>The target of the action
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”.
resource_ext: Option<FieldExtension>Extension field.
definition: Option<RequestOrchestrationActionDefinition>Description of the activity to be performed
A reference to an ActivityDefinition that describes the action to be taken in detail, 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, or an ObservationDefinition that specifies what observation should be captured.
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.
definition_ext: Option<RequestOrchestrationActionDefinitionExtension>Extension field.
transform: Option<String>Transform to apply the template
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.
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.
transform_ext: Option<FieldExtension>Extension field.
dynamic_value: Vec<Option<RequestOrchestrationActionDynamicValue>>Dynamic aspects of the definition
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.
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.
dynamic_value_ext: Vec<Option<FieldExtension>>Extension field.
action: Vec<Option<RequestOrchestrationAction>>Sub action
Sub actions.
action_ext: Vec<Option<FieldExtension>>Extension field.
Implementations§
Source§impl RequestOrchestrationAction
impl RequestOrchestrationAction
Sourcepub fn builder() -> RequestOrchestrationActionBuilder
pub fn builder() -> RequestOrchestrationActionBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for RequestOrchestrationAction
impl Clone for RequestOrchestrationAction
Source§fn clone(&self) -> RequestOrchestrationAction
fn clone(&self) -> RequestOrchestrationAction
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more