pub struct RequestOrchestrationInner {Show 44 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub instantiates_canonical: Vec<Option<String>>,
pub instantiates_canonical_ext: Vec<Option<FieldExtension>>,
pub instantiates_uri: Vec<Option<String>>,
pub instantiates_uri_ext: Vec<Option<FieldExtension>>,
pub based_on: Vec<Option<Reference>>,
pub based_on_ext: Vec<Option<FieldExtension>>,
pub replaces: Vec<Option<Reference>>,
pub replaces_ext: Vec<Option<FieldExtension>>,
pub group_identifier: Option<Identifier>,
pub group_identifier_ext: Option<FieldExtension>,
pub status: RequestStatus,
pub status_ext: Option<FieldExtension>,
pub intent: RequestIntent,
pub intent_ext: Option<FieldExtension>,
pub priority: Option<RequestPriority>,
pub priority_ext: Option<FieldExtension>,
pub code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub subject: Option<Reference>,
pub subject_ext: Option<FieldExtension>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub authored_on: Option<DateTime>,
pub authored_on_ext: Option<FieldExtension>,
pub author: Option<Reference>,
pub author_ext: Option<FieldExtension>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub goal: Vec<Option<Reference>>,
pub goal_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub action: Vec<Option<RequestOrchestrationAction>>,
pub action_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
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”.
RequestOrchestration v5.0.0
A set of related requests
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”.
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
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.
implicit_rules: Option<String>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. 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 its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
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: Option<Narrative>Text summary of the resource, for human interpretation
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 a 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.
contained: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
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.
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 resource. 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
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 managable, 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.
identifier: Vec<Option<Identifier>>Business identifier
Allows a service to provide a unique, business identifier for the request.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_canonical: Vec<Option<String>>Instantiates FHIR protocol or definition
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.
instantiates_canonical_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_uri: Vec<Option<String>>Instantiates external protocol or definition
A URL referencing an externally defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this request.
instantiates_uri_ext: Vec<Option<FieldExtension>>Extension field.
based_on: Vec<Option<Reference>>Fulfills plan, proposal, or order
A plan, proposal or order that is fulfilled in whole or in part by this request.
based_on_ext: Vec<Option<FieldExtension>>Extension field.
replaces: Vec<Option<Reference>>Request(s) replaced by this request
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.
replaces_ext: Vec<Option<FieldExtension>>Extension field.
group_identifier: Option<Identifier>Composite request this is part of
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.
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.
group_identifier_ext: Option<FieldExtension>Extension field.
status: RequestStatusRequestStatus; draft | active | on-hold | revoked | completed | entered-in-error | unknown
The current state of the request. For request orchestrations, the status reflects the status of all the requests in the orchestration.
status_ext: Option<FieldExtension>Extension field.
intent: RequestIntentRequestIntent; proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Indicates the level of authority/intentionality associated with the request and where the request fits into the workflow chain.
intent_ext: Option<FieldExtension>Extension field.
priority: Option<RequestPriority>RequestPriority; routine | urgent | asap | stat
Indicates how quickly the request should be addressed with respect to other requests.
priority_ext: Option<FieldExtension>Extension field.
code: Option<CodeableConcept>RequestCode; What’s being requested/ordered
A code that identifies what the overall request orchestration is.
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.
code_ext: Option<FieldExtension>Extension field.
subject: Option<Reference>Who the request orchestration is about
The subject for which the request orchestration was created.
subject_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>Created as part of
Describes the context of the request orchestration, if any.
encounter_ext: Option<FieldExtension>Extension field.
When the request orchestration was authored
Indicates when the request orchestration was created.
Extension field.
Device or practitioner that authored the request orchestration
Provides a reference to the author of the request orchestration.
Extension field.
reason: Vec<Option<CodeableReference>>ActionReasonCode; Why the request orchestration is needed
Describes the reason for the request orchestration in coded or textual form.
reason_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 RequestOrchestration.
goal_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Additional notes about the response
Provides a mechanism to communicate additional information about the response.
note_ext: Vec<Option<FieldExtension>>Extension field.
action: Vec<Option<RequestOrchestrationAction>>Proposed actions, if any
The actions, if any, produced by the evaluation of the artifact.
action_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for RequestOrchestrationInner
impl Clone for RequestOrchestrationInner
Source§fn clone(&self) -> RequestOrchestrationInner
fn clone(&self) -> RequestOrchestrationInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more