pub struct MessageHeaderSource {Show 13 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub endpoint: Option<MessageHeaderSourceEndpoint>,
pub endpoint_ext: Option<MessageHeaderSourceEndpointExtension>,
pub name: Option<String>,
pub name_ext: Option<FieldExtension>,
pub software: Option<String>,
pub software_ext: Option<FieldExtension>,
pub version: Option<String>,
pub version_ext: Option<FieldExtension>,
pub contact: Option<ContactPoint>,
pub contact_ext: Option<FieldExtension>,
}
Expand description
Sub-fields of the source field in MessageHeader
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.
endpoint: Option<MessageHeaderSourceEndpoint>
Actual source address or Endpoint resource
Identifies the routing target to send acknowledgements to.
The url may be a non-resolvable URI for systems that do not use standard network-based addresses.
endpoint_ext: Option<MessageHeaderSourceEndpointExtension>
Extension field.
name: Option<String>
Name of system
Human-readable name for the source system.
name_ext: Option<FieldExtension>
Extension field.
software: Option<String>
Name of software running the system
May include configuration or other information useful in debugging.
software_ext: Option<FieldExtension>
Extension field.
version: Option<String>
Version of software running
Can convey versions of multiple systems in situations where a message passes through multiple hands.
version_ext: Option<FieldExtension>
Extension field.
contact: Option<ContactPoint>
Human contact for problems
An e-mail, phone, website or other contact point to use to resolve issues with message communications.
contact_ext: Option<FieldExtension>
Extension field.
Implementations§
Source§impl MessageHeaderSource
impl MessageHeaderSource
Sourcepub fn builder() -> MessageHeaderSourceBuilder
pub fn builder() -> MessageHeaderSourceBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for MessageHeaderSource
impl Clone for MessageHeaderSource
Source§fn clone(&self) -> MessageHeaderSource
fn clone(&self) -> MessageHeaderSource
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more