Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: FHIR R5 Ballot Preview). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

2.16 Resource MessageHeader - Content

Infrastructure And Messaging Work GroupMaturity Level: 4 Trial UseSecurity Category: Not Classified Compartments: Device, Practitioner

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.

2.16.1 Scope and Usage

The MessageHeader resource is defined in order to support Messaging using FHIR resources. The principal usage of the MessageHeader resource is when messages are exchanged. However, as a resource that can be used with the RESTful framework, the MessageHeader resource has the normal resource end-point ([base-url]/MessageHeader), which is used to manage a set of static messages resources. This could be used to make an archive of past messages available. Creating or updating Message resources in this fashion does not represent the actual occurrence of any event, nor can it trigger any logic associated with the actual event. It is just for managing a set of message resources.

2.16.2 References to this Resource

No references for this Resource.

2.16.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. MessageHeader TUDomainResourceA resource that describes a message that is exchanged between systems

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... event[x] Σ1..1Event code or link to EventDefinition
MessageEvent (Example)
.... eventCodingCoding
.... eventCanonicalcanonical(EventDefinition)
... destination Σ0..*BackboneElementMessage destination application(s)

.... name Σ0..1stringName of system
.... target Σ0..1Reference(Device)Particular delivery destination within the destination
.... endpoint Σ0..1urlActual destination address or id
.... receiver Σ0..1Reference(Practitioner | PractitionerRole | Organization)Intended "real-world" recipient for the data
... sender Σ0..1Reference(Practitioner | PractitionerRole | Organization)Real world sender of the message
... author Σ0..1Reference(Practitioner | PractitionerRole)The source of the decision
... source Σ1..1BackboneElementMessage source application
.... name Σ0..1stringName of system
.... software Σ0..1stringName of software running the system
.... version Σ0..1stringVersion of software running
.... contact Σ0..1ContactPointHuman contact for problems
.... endpoint Σ0..1urlActual message source address or id
... responsible Σ0..1Reference(Practitioner | PractitionerRole | Organization)Final responsibility for event
... reason Σ0..1CodeableConceptCause of event
Example Message Reason Codes (Example)
... response Σ0..1BackboneElementIf this is a reply to prior message
.... identifier Σ1..1IdentifierId of original message
.... code Σ1..1codeok | transient-error | fatal-error
ResponseType (Required)
.... details Σ0..1Reference(OperationOutcome)Specific list of hints/warnings/errors
... focus Σ0..*Reference(Any)The actual content of the message

... definition Σ0..1canonical(MessageDefinition)Link to the definition for this message

doco Documentation for this format

See the Extensions for this resource

UML Diagram (Legend)

MessageHeader (DomainResource)Code that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification have the system value "http://terminology.hl7.org/CodeSystem/message-events". Alternatively a canonical uri to the EventDefinitionevent[x] : DataType [1..1] « Coding|canonical(EventDefinition); null (Strength=Example) MessageEvent?? »Identifies the sending system to allow the use of a trust relationshipsender : Reference [0..1] « Practitioner|PractitionerRole| Organization »The person or device that performed the data entry leading to this message. When there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensionsenterer : Reference [0..1] « Practitioner|PractitionerRole »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 extensionsauthor : Reference [0..1] « Practitioner|PractitionerRole »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 partyresponsible : Reference [0..1] « Practitioner|PractitionerRole| Organization »Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this messagereason : CodeableConcept [0..1] « null (Strength=Example)ExampleMessageReasonCodes?? »The actual data of the message - a reference to the root/focus class of the event. This is allowed to be a Parameters resourcefocus : Reference [0..*] « Any »Permanent link to the MessageDefinition for this messagedefinition : canonical [0..1] « MessageDefinition »MessageDestinationHuman-readable name for the target systemname : string [0..1]Identifies the target end system in situations where the initial message transmission is to an intermediary systemtarget : Reference [0..1] « Device »Indicates where the message should be routed toendpoint : url [0..1]Allows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficientreceiver : Reference [0..1] « Practitioner|PractitionerRole| Organization »MessageSourceHuman-readable name for the source systemname : string [0..1]May include configuration or other information useful in debuggingsoftware : string [0..1]Can convey versions of multiple systems in situations where a message passes through multiple handsversion : string [0..1]An e-mail, phone, website or other contact point to use to resolve issues with message communicationscontact : ContactPoint [0..1]Identifies the routing target to send acknowledgements toendpoint : url [0..1]ResponseThe MessageHeader.id of the message to which this message is a responseidentifier : Identifier [1..1]Code that identifies the type of response to the message - whether it was successful or not, and whether it should be resent or notcode : code [1..1] « null (Strength=Required)ResponseType! »Full details of any issues found in the messagedetails : Reference [0..1] « OperationOutcome »The destination application which the message is intended fordestination[0..*]The source application from which this message originatedsource[1..1]Information about the message that this message is a response to. Only present if this message is a responseresponse[0..1]

XML Template

<MessageHeader xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <event[x]><!-- 1..1 Coding|canonical(EventDefinition) Event code or link to EventDefinition --></event[x]>
 <destination>  <!-- 0..* Message destination application(s) -->
  <name value="[string]"/><!-- 0..1 Name of system -->
  <target><!-- 0..1 Reference(Device) Particular delivery destination within the destination --></target>
  <endpoint value="[url]"/><!-- 0..1 Actual destination address or id -->
  <receiver><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Intended "real-world" recipient for the data --></receiver>
 </destination>
 <sender><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Real world sender of the message --></sender>
 <enterer><!-- 0..1 Reference(Practitioner|PractitionerRole) The source of the data entry --></enterer>
 <author><!-- 0..1 Reference(Practitioner|PractitionerRole) The source of the decision --></author>
 <source>  <!-- 1..1 Message source application -->
  <name value="[string]"/><!-- 0..1 Name of system -->
  <software value="[string]"/><!-- 0..1 Name of software running the system -->
  <version value="[string]"/><!-- 0..1 Version of software running -->
  <contact><!-- 0..1 ContactPoint Human contact for problems --></contact>
  <endpoint value="[url]"/><!-- 0..1 Actual message source address or id -->
 </source>
 <responsible><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Final responsibility for event --></responsible>
 <reason><!-- 0..1 CodeableConcept Cause of event --></reason>
 <response>  <!-- 0..1 If this is a reply to prior message -->
  <identifier><!-- 1..1 Identifier Id of original message --></identifier>
  <code value="[code]"/><!-- 1..1 ok | transient-error | fatal-error -->
  <details><!-- 0..1 Reference(OperationOutcome) Specific list of hints/warnings/errors --></details>
 </response>
 <focus><!-- 0..* Reference(Any) The actual content of the message --></focus>
 <definition><!-- 0..1 canonical(MessageDefinition) Link to the definition for this message --></definition>
</MessageHeader>

JSON Template

{doco
  "resourceType" : "MessageHeader",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  // event[x]: Event code or link to EventDefinition. One of these 2:
  "eventCoding" : { Coding },
  "eventCanonical" : "<canonical(EventDefinition)>",
  "destination" : [{ // Message destination application(s)
    "name" : "<string>", // Name of system
    "target" : { Reference(Device) }, // Particular delivery destination within the destination
    "endpoint" : "<url>", // Actual destination address or id
    "receiver" : { Reference(Organization|Practitioner|PractitionerRole) } // Intended "real-world" recipient for the data
  }],
  "sender" : { Reference(Organization|Practitioner|PractitionerRole) }, // Real world sender of the message
  "enterer" : { Reference(Practitioner|PractitionerRole) }, // The source of the data entry
  "author" : { Reference(Practitioner|PractitionerRole) }, // The source of the decision
  "source" : { // R!  Message source application
    "name" : "<string>", // Name of system
    "software" : "<string>", // Name of software running the system
    "version" : "<string>", // Version of software running
    "contact" : { ContactPoint }, // Human contact for problems
    "endpoint" : "<url>" // Actual message source address or id
  },
  "responsible" : { Reference(Organization|Practitioner|PractitionerRole) }, // Final responsibility for event
  "reason" : { CodeableConcept }, // Cause of event
  "response" : { // If this is a reply to prior message
    "identifier" : { Identifier }, // R!  Id of original message
    "code" : "<code>", // R!  ok | transient-error | fatal-error
    "details" : { Reference(OperationOutcome) } // Specific list of hints/warnings/errors
  },
  "focus" : [{ Reference(Any) }], // The actual content of the message
  "definition" : "<canonical(MessageDefinition)>" // Link to the definition for this message
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:MessageHeader;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  # MessageHeader.event[x] : 1..1 Event code or link to EventDefinition. One of these 2
    fhir:MessageHeader.eventCoding [ Coding ]
    fhir:MessageHeader.eventCanonical [ canonical(EventDefinition) ]
  fhir:MessageHeader.destination [ # 0..* Message destination application(s)
    fhir:MessageHeader.destination.name [ string ]; # 0..1 Name of system
    fhir:MessageHeader.destination.target [ Reference(Device) ]; # 0..1 Particular delivery destination within the destination
    fhir:MessageHeader.destination.endpoint [ url ]; # 0..1 Actual destination address or id
    fhir:MessageHeader.destination.receiver [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Intended "real-world" recipient for the data
  ], ...;
  fhir:MessageHeader.sender [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Real world sender of the message
  fhir:MessageHeader.enterer [ Reference(Practitioner|PractitionerRole) ]; # 0..1 The source of the data entry
  fhir:MessageHeader.author [ Reference(Practitioner|PractitionerRole) ]; # 0..1 The source of the decision
  fhir:MessageHeader.source [ # 1..1 Message source application
    fhir:MessageHeader.source.name [ string ]; # 0..1 Name of system
    fhir:MessageHeader.source.software [ string ]; # 0..1 Name of software running the system
    fhir:MessageHeader.source.version [ string ]; # 0..1 Version of software running
    fhir:MessageHeader.source.contact [ ContactPoint ]; # 0..1 Human contact for problems
    fhir:MessageHeader.source.endpoint [ url ]; # 0..1 Actual message source address or id
  ];
  fhir:MessageHeader.responsible [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Final responsibility for event
  fhir:MessageHeader.reason [ CodeableConcept ]; # 0..1 Cause of event
  fhir:MessageHeader.response [ # 0..1 If this is a reply to prior message
    fhir:MessageHeader.response.identifier [ Identifier ]; # 1..1 Id of original message
    fhir:MessageHeader.response.code [ code ]; # 1..1 ok | transient-error | fatal-error
    fhir:MessageHeader.response.details [ Reference(OperationOutcome) ]; # 0..1 Specific list of hints/warnings/errors
  ];
  fhir:MessageHeader.focus [ Reference(Any) ], ... ; # 0..* The actual content of the message
  fhir:MessageHeader.definition [ canonical(MessageDefinition) ]; # 0..1 Link to the definition for this message
]

Changes since R4

MessageHeader
MessageHeader.event[x]
  • Add Type canonical(EventDefinition), canonical(EventDefinition)
  • Remove Type uri, uri
  • Remove Type uri, uri
MessageHeader.destination.endpoint
  • Min Cardinality changed from 1 to 0
  • Min Cardinality changed from 1 to 0
MessageHeader.source.endpoint
  • Min Cardinality changed from 1 to 0
  • Min Cardinality changed from 1 to 0
MessageHeader.response.identifier
  • Type changed from id to Identifier
  • Type changed from id to Identifier

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors).)

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. MessageHeader TUDomainResourceA resource that describes a message that is exchanged between systems

Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... event[x] Σ1..1Event code or link to EventDefinition
MessageEvent (Example)
.... eventCodingCoding
.... eventCanonicalcanonical(EventDefinition)
... destination Σ0..*BackboneElementMessage destination application(s)

.... name Σ0..1stringName of system
.... target Σ0..1Reference(Device)Particular delivery destination within the destination
.... endpoint Σ0..1urlActual destination address or id
.... receiver Σ0..1Reference(Practitioner | PractitionerRole | Organization)Intended "real-world" recipient for the data
... sender Σ0..1Reference(Practitioner | PractitionerRole | Organization)Real world sender of the message
... author Σ0..1Reference(Practitioner | PractitionerRole)The source of the decision
... source Σ1..1BackboneElementMessage source application
.... name Σ0..1stringName of system
.... software Σ0..1stringName of software running the system
.... version Σ0..1stringVersion of software running
.... contact Σ0..1ContactPointHuman contact for problems
.... endpoint Σ0..1urlActual message source address or id
... responsible Σ0..1Reference(Practitioner | PractitionerRole | Organization)Final responsibility for event
... reason Σ0..1CodeableConceptCause of event
Example Message Reason Codes (Example)
... response Σ0..1BackboneElementIf this is a reply to prior message
.... identifier Σ1..1IdentifierId of original message
.... code Σ1..1codeok | transient-error | fatal-error
ResponseType (Required)
.... details Σ0..1Reference(OperationOutcome)Specific list of hints/warnings/errors
... focus Σ0..*Reference(Any)The actual content of the message

... definition Σ0..1canonical(MessageDefinition)Link to the definition for this message

doco Documentation for this format

See the Extensions for this resource

UML Diagram (Legend)

MessageHeader (DomainResource)Code that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification have the system value "http://terminology.hl7.org/CodeSystem/message-events". Alternatively a canonical uri to the EventDefinitionevent[x] : DataType [1..1] « Coding|canonical(EventDefinition); null (Strength=Example) MessageEvent?? »Identifies the sending system to allow the use of a trust relationshipsender : Reference [0..1] « Practitioner|PractitionerRole| Organization »The person or device that performed the data entry leading to this message. When there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensionsenterer : Reference [0..1] « Practitioner|PractitionerRole »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 extensionsauthor : Reference [0..1] « Practitioner|PractitionerRole »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 partyresponsible : Reference [0..1] « Practitioner|PractitionerRole| Organization »Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this messagereason : CodeableConcept [0..1] « null (Strength=Example)ExampleMessageReasonCodes?? »The actual data of the message - a reference to the root/focus class of the event. This is allowed to be a Parameters resourcefocus : Reference [0..*] « Any »Permanent link to the MessageDefinition for this messagedefinition : canonical [0..1] « MessageDefinition »MessageDestinationHuman-readable name for the target systemname : string [0..1]Identifies the target end system in situations where the initial message transmission is to an intermediary systemtarget : Reference [0..1] « Device »Indicates where the message should be routed toendpoint : url [0..1]Allows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficientreceiver : Reference [0..1] « Practitioner|PractitionerRole| Organization »MessageSourceHuman-readable name for the source systemname : string [0..1]May include configuration or other information useful in debuggingsoftware : string [0..1]Can convey versions of multiple systems in situations where a message passes through multiple handsversion : string [0..1]An e-mail, phone, website or other contact point to use to resolve issues with message communicationscontact : ContactPoint [0..1]Identifies the routing target to send acknowledgements toendpoint : url [0..1]ResponseThe MessageHeader.id of the message to which this message is a responseidentifier : Identifier [1..1]Code that identifies the type of response to the message - whether it was successful or not, and whether it should be resent or notcode : code [1..1] « null (Strength=Required)ResponseType! »Full details of any issues found in the messagedetails : Reference [0..1] « OperationOutcome »The destination application which the message is intended fordestination[0..*]The source application from which this message originatedsource[1..1]Information about the message that this message is a response to. Only present if this message is a responseresponse[0..1]

XML Template

<MessageHeader xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <event[x]><!-- 1..1 Coding|canonical(EventDefinition) Event code or link to EventDefinition --></event[x]>
 <destination>  <!-- 0..* Message destination application(s) -->
  <name value="[string]"/><!-- 0..1 Name of system -->
  <target><!-- 0..1 Reference(Device) Particular delivery destination within the destination --></target>
  <endpoint value="[url]"/><!-- 0..1 Actual destination address or id -->
  <receiver><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Intended "real-world" recipient for the data --></receiver>
 </destination>
 <sender><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Real world sender of the message --></sender>
 <enterer><!-- 0..1 Reference(Practitioner|PractitionerRole) The source of the data entry --></enterer>
 <author><!-- 0..1 Reference(Practitioner|PractitionerRole) The source of the decision --></author>
 <source>  <!-- 1..1 Message source application -->
  <name value="[string]"/><!-- 0..1 Name of system -->
  <software value="[string]"/><!-- 0..1 Name of software running the system -->
  <version value="[string]"/><!-- 0..1 Version of software running -->
  <contact><!-- 0..1 ContactPoint Human contact for problems --></contact>
  <endpoint value="[url]"/><!-- 0..1 Actual message source address or id -->
 </source>
 <responsible><!-- 0..1 Reference(Organization|Practitioner|PractitionerRole) Final responsibility for event --></responsible>
 <reason><!-- 0..1 CodeableConcept Cause of event --></reason>
 <response>  <!-- 0..1 If this is a reply to prior message -->
  <identifier><!-- 1..1 Identifier Id of original message --></identifier>
  <code value="[code]"/><!-- 1..1 ok | transient-error | fatal-error -->
  <details><!-- 0..1 Reference(OperationOutcome) Specific list of hints/warnings/errors --></details>
 </response>
 <focus><!-- 0..* Reference(Any) The actual content of the message --></focus>
 <definition><!-- 0..1 canonical(MessageDefinition) Link to the definition for this message --></definition>
</MessageHeader>

JSON Template

{doco
  "resourceType" : "MessageHeader",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  // event[x]: Event code or link to EventDefinition. One of these 2:
  "eventCoding" : { Coding },
  "eventCanonical" : "<canonical(EventDefinition)>",
  "destination" : [{ // Message destination application(s)
    "name" : "<string>", // Name of system
    "target" : { Reference(Device) }, // Particular delivery destination within the destination
    "endpoint" : "<url>", // Actual destination address or id
    "receiver" : { Reference(Organization|Practitioner|PractitionerRole) } // Intended "real-world" recipient for the data
  }],
  "sender" : { Reference(Organization|Practitioner|PractitionerRole) }, // Real world sender of the message
  "enterer" : { Reference(Practitioner|PractitionerRole) }, // The source of the data entry
  "author" : { Reference(Practitioner|PractitionerRole) }, // The source of the decision
  "source" : { // R!  Message source application
    "name" : "<string>", // Name of system
    "software" : "<string>", // Name of software running the system
    "version" : "<string>", // Version of software running
    "contact" : { ContactPoint }, // Human contact for problems
    "endpoint" : "<url>" // Actual message source address or id
  },
  "responsible" : { Reference(Organization|Practitioner|PractitionerRole) }, // Final responsibility for event
  "reason" : { CodeableConcept }, // Cause of event
  "response" : { // If this is a reply to prior message
    "identifier" : { Identifier }, // R!  Id of original message
    "code" : "<code>", // R!  ok | transient-error | fatal-error
    "details" : { Reference(OperationOutcome) } // Specific list of hints/warnings/errors
  },
  "focus" : [{ Reference(Any) }], // The actual content of the message
  "definition" : "<canonical(MessageDefinition)>" // Link to the definition for this message
}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:MessageHeader;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  # MessageHeader.event[x] : 1..1 Event code or link to EventDefinition. One of these 2
    fhir:MessageHeader.eventCoding [ Coding ]
    fhir:MessageHeader.eventCanonical [ canonical(EventDefinition) ]
  fhir:MessageHeader.destination [ # 0..* Message destination application(s)
    fhir:MessageHeader.destination.name [ string ]; # 0..1 Name of system
    fhir:MessageHeader.destination.target [ Reference(Device) ]; # 0..1 Particular delivery destination within the destination
    fhir:MessageHeader.destination.endpoint [ url ]; # 0..1 Actual destination address or id
    fhir:MessageHeader.destination.receiver [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Intended "real-world" recipient for the data
  ], ...;
  fhir:MessageHeader.sender [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Real world sender of the message
  fhir:MessageHeader.enterer [ Reference(Practitioner|PractitionerRole) ]; # 0..1 The source of the data entry
  fhir:MessageHeader.author [ Reference(Practitioner|PractitionerRole) ]; # 0..1 The source of the decision
  fhir:MessageHeader.source [ # 1..1 Message source application
    fhir:MessageHeader.source.name [ string ]; # 0..1 Name of system
    fhir:MessageHeader.source.software [ string ]; # 0..1 Name of software running the system
    fhir:MessageHeader.source.version [ string ]; # 0..1 Version of software running
    fhir:MessageHeader.source.contact [ ContactPoint ]; # 0..1 Human contact for problems
    fhir:MessageHeader.source.endpoint [ url ]; # 0..1 Actual message source address or id
  ];
  fhir:MessageHeader.responsible [ Reference(Organization|Practitioner|PractitionerRole) ]; # 0..1 Final responsibility for event
  fhir:MessageHeader.reason [ CodeableConcept ]; # 0..1 Cause of event
  fhir:MessageHeader.response [ # 0..1 If this is a reply to prior message
    fhir:MessageHeader.response.identifier [ Identifier ]; # 1..1 Id of original message
    fhir:MessageHeader.response.code [ code ]; # 1..1 ok | transient-error | fatal-error
    fhir:MessageHeader.response.details [ Reference(OperationOutcome) ]; # 0..1 Specific list of hints/warnings/errors
  ];
  fhir:MessageHeader.focus [ Reference(Any) ], ... ; # 0..* The actual content of the message
  fhir:MessageHeader.definition [ canonical(MessageDefinition) ]; # 0..1 Link to the definition for this message
]

Changes since Release 4

MessageHeader
MessageHeader.event[x]
  • Add Type canonical(EventDefinition), canonical(EventDefinition)
  • Remove Type uri, uri
  • Remove Type uri, uri
MessageHeader.destination.endpoint
  • Min Cardinality changed from 1 to 0
  • Min Cardinality changed from 1 to 0
MessageHeader.source.endpoint
  • Min Cardinality changed from 1 to 0
  • Min Cardinality changed from 1 to 0
MessageHeader.response.identifier
  • Type changed from id to Identifier
  • Type changed from id to Identifier

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors).)

 

Additional definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions, the spreadsheet version & the dependency analysis

2.16.3.1 Terminology Bindings

PathDefinitionTypeReference
MessageHeader.event[x]

One of the message events defined as part of this version of FHIR.

ExampleMessageEvent
MessageHeader.reason

Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.

ExampleExampleMessageReasonCodes
MessageHeader.response.code

The kind of response to a message.

RequiredResponseType

2.16.4 Notes:

  • The resources referenced by the enterer, author and responsible elements may all be included in the message bundle or left out on the basis that the recipient (and any intermediaries) are able to locate/resolve the resources independently. The former would be suitable for loosely coupled systems, and the latter for tightly coupled systems. The messaging Capability statement for an application may reference a Structure Definition that describes how the bundling occurs
  • The actual content of the focus resource is specified for each message event (see the list on the messaging page). Any resources referenced in the focus element are always included in the bundle
  • If MessageHeader.source.endpoint and MessageHeader.destination.endpoint, are literal URLs, then they SHOULD identify the addresses to which messages can be delivered. If they are logical URIs (i.e. non-dereferenceable), message delivery intermediaries must know how to deliver the message to the destination application.
  • The time of the event will be found in the focus resource. The time of the message will be found in Bundle.timestamp
  • The author and the receiver are not the actual technical systems - these are the human or organizations that make use of the technical systems
  • A receiver is not obligated to reject messages which do not explicitly identify it as receiver (e.g. a tracker will get messages that are destined for some other system)
  • The value set MessageEvent is populated by the authors of the resources declaring the events

2.16.5 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionExpressionIn Common
authorreferenceThe source of the decisionMessageHeader.author
(Practitioner, PractitionerRole)
code Ntokenok | transient-error | fatal-errorMessageHeader.response.code
destination NstringName of systemMessageHeader.destination.name
destination-uri NuriActual destination address or idMessageHeader.destination.endpoint
entererreferenceThe source of the data entryMessageHeader.enterer
(Practitioner, PractitionerRole)
eventtokenCode for the event this message represents or link to event definitionMessageHeader.event
focusreferenceThe actual content of the messageMessageHeader.focus
(Any)
receiverreferenceIntended "real-world" recipient for the dataMessageHeader.destination.receiver
(Practitioner, Organization, PractitionerRole)
response-id NtokenId of original messageMessageHeader.response.identifier
responsiblereferenceFinal responsibility for eventMessageHeader.responsible
(Practitioner, Organization, PractitionerRole)
senderreferenceReal world sender of the messageMessageHeader.sender
(Practitioner, Organization, PractitionerRole)
source NstringName of systemMessageHeader.source.name
source-uri NuriActual message source address or idMessageHeader.source.endpoint
targetreferenceParticular delivery destination within the destinationMessageHeader.destination.target
(Device)