pub struct MessageHeaderInner {Show 28 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 event: MessageHeaderEvent,
pub event_ext: Option<MessageHeaderEventExtension>,
pub destination: Vec<Option<MessageHeaderDestination>>,
pub destination_ext: Vec<Option<FieldExtension>>,
pub sender: Option<Reference>,
pub sender_ext: Option<FieldExtension>,
pub author: Option<Reference>,
pub author_ext: Option<FieldExtension>,
pub source: MessageHeaderSource,
pub source_ext: Option<FieldExtension>,
pub responsible: Option<Reference>,
pub responsible_ext: Option<FieldExtension>,
pub reason: Option<CodeableConcept>,
pub reason_ext: Option<FieldExtension>,
pub response: Option<MessageHeaderResponse>,
pub response_ext: Option<FieldExtension>,
pub focus: Vec<Option<Reference>>,
pub focus_ext: Vec<Option<FieldExtension>>,
pub definition: Option<String>,
pub definition_ext: Option<FieldExtension>,
/* private fields */
}Expand description
The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
MessageHeader v5.0.0
A resource that describes a message that is exchanged between systems
The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle.
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.
event: MessageHeaderEventEvent code or link to EventDefinition
Code that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification are defined by the implementation. Alternatively a canonical uri to the EventDefinition.
The time of the event will be found in the focus resource. The time of the message will be found in Bundle.timestamp.
event_ext: Option<MessageHeaderEventExtension>Extension field.
destination: Vec<Option<MessageHeaderDestination>>Message destination application(s)
The destination application which the message is intended for.
There SHOULD be at least one destination, but in some circumstances, the source system is unaware of any particular destination system.
destination_ext: Vec<Option<FieldExtension>>Extension field.
sender: Option<Reference>Real world sender of the message
Identifies the sending system to allow the use of a trust relationship.
Use case is for where a (trusted) sending system is responsible for multiple organizations, and therefore cannot differentiate based on source endpoint / authentication alone. Proposing to remove and rely on Task to convey this information.
sender_ext: Option<FieldExtension>Extension field.
The source of the decision
The logical author of the message - the personor device that decided the described event should happen. When there is more than one candidate, pick the most proximal to the MessageHeader. Can provide other authors in extensions.
Usually only for the request but can be used in a response.Proposing to remove and rely on Task to convey this information.
Extension field.
source: MessageHeaderSourceMessage source application
The source application from which this message originated.
source_ext: Option<FieldExtension>Extension field.
responsible: Option<Reference>Final responsibility for event
The person or organization that accepts overall responsibility for the contents of the message. The implication is that the message event happened under the policies of the responsible party.
Usually only for the request but can be used in a response.Proposing to remove and rely on Task to convey this information.
responsible_ext: Option<FieldExtension>Extension field.
reason: Option<CodeableConcept>EventReason; Cause of event
Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this message.
reason_ext: Option<FieldExtension>Extension field.
response: Option<MessageHeaderResponse>If this is a reply to prior message
Information about the message that this message is a response to. Only present if this message is a response.
response_ext: Option<FieldExtension>Extension field.
focus: Vec<Option<Reference>>The actual content of the message
The actual data of the message - a reference to the root/focus class of the event. This is allowed to be a Parameters resource.
The data is defined where the transaction type is defined. The transaction data is always included in the bundle that is the full message. Only the root resource is specified. The resources it references should be contained in the bundle but are not also listed here. Multiple repetitions are allowed to cater for merges and other situations with multiple focal targets.
focus_ext: Vec<Option<FieldExtension>>Extension field.
definition: Option<String>Link to the definition for this message
Permanent link to the MessageDefinition for this message.
definition_ext: Option<FieldExtension>Extension field.
Trait Implementations§
Source§impl Clone for MessageHeaderInner
impl Clone for MessageHeaderInner
Source§fn clone(&self) -> MessageHeaderInner
fn clone(&self) -> MessageHeaderInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more