- This is an Implementation Guide for UK Core FHIR Assets in Development.
- There will be disruption as the content will be updated on an ad-hoc basis and with links not working.
- Therefore this Implementation Guide must not be implemented.
- Please follow the guidance on the "Contact Us" page if you need any assistance.
StructureDefinition-UKCore-MessageHeader
Canonical_URL | Status | Current_Version | Last_Updated | Description |
---|---|---|---|---|
https://fhir.hl7.org.uk/StructureDefinition/UKCore-MessageHeader | draft | 2.4.0 | 2024-07-11 | This profile defines the UK constraints and extensions on the International FHIR resource MessageHeader. |
Profile_Purpose |
---|
This profile carries the header data for a message exchange that is either requesting or responding to an action. |
Detailed Descriptions
MessageHeader | |
Definition | 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. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
MessageHeader.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
MessageHeader.meta | |
Definition | 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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
MessageHeader.implicitRules | |
Definition | 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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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 it's narrative along with other profiles, value sets, etc. |
Invariants |
|
Mappings |
|
MessageHeader.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
Mappings |
|
MessageHeader.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | Contained resources do not have 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. |
Invariants |
|
Mappings |
|
MessageHeader.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
MessageHeader.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MessageHeader.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MessageHeader.event[x] | |
Definition | 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 uri to the EventDefinition. |
Cardinality | 1...1 |
Type | Coding |
Binding | One of the message events defined as part of this version of FHIR. |
Must Support | True |
Summary | True |
Requirements | Drives the behavior associated with this message. |
Comments | The time of the event will be found in the focus resource. The time of the message will be found in Bundle.timestamp. |
Invariants |
|
Mappings |
|
MessageHeader.destination | |
Definition | The destination application which the message is intended for. |
Cardinality | 0...* |
Type | BackboneElement |
Must Support | True |
Summary | True |
Requirements | Indicates where message is to be sent for routing purposes. Allows verification of "am I the intended recipient". |
Comments | There SHOULD be at least one destination, but in some circumstances, the source system is unaware of any particular destination system. |
Invariants |
|
Mappings |
|
MessageHeader.destination.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
MessageHeader.destination.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MessageHeader.destination.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | 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. |
Invariants |
|
Mappings |
|
MessageHeader.destination.name | |
Definition | Human-readable name for the target system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | May be used for routing of response and/or to support audit. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MessageHeader.destination.target | |
Definition | Identifies the target end system in situations where the initial message transmission is to an intermediary system. |
Cardinality | 0...1 |
Type | Reference(Device) |
Summary | True |
Requirements | Supports multi-hop routing. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MessageHeader.destination.endpoint | |
Definition | Indicates where the message should be routed to. |
Cardinality | 1...1 |
Type | url |
Summary | True |
Requirements | Identifies where to route the message. |
Comments | The id may be a non-resolvable URI for systems that do not use standard network-based addresses. |
Invariants |
|
Mappings |
|
MessageHeader.destination.receiver | |
Definition | Allows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | Organization) |
Summary | True |
Requirements | Allows routing beyond just the application level. |
Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. |
Invariants |
|
Mappings |
|
MessageHeader.sender | |
Definition | Identifies the sending system to allow the use of a trust relationship. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | Organization) |
Must Support | True |
Summary | True |
Requirements | Allows routing beyond just the application level. |
Comments | Use case is for where a (trusted) sending system is responsible for multiple organizations, and therefore cannot differentiate based on source endpoint / authentication alone. |
Invariants |
|
Mappings |
|
MessageHeader.enterer | |
Definition | 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 extensions. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole) |
Summary | True |
Requirements | Need to know for audit/traceback requirements and possibly for authorization. |
Comments | Usually only for the request but can be used in a response. |
Invariants |
|
Mappings |
|
MessageHeader.author | |
Definition | The logical author of the message - the person or 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. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole) |
Summary | True |
Requirements | Need to know for audit/traceback requirements and possibly for authorization. |
Comments | Usually only for the request but can be used in a response. |
Invariants |
|
Mappings |
|
MessageHeader.source | |
Definition | The source application from which this message originated. |
Cardinality | 1...1 |
Type | BackboneElement |
Must Support | True |
Summary | True |
Requirements | Allows replies, supports audit. |
Invariants |
|
Mappings |
|
MessageHeader.source.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
MessageHeader.source.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MessageHeader.source.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | 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. |
Invariants |
|
Mappings |
|
MessageHeader.source.name | |
Definition | Human-readable name for the source system. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | May be used to support audit. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MessageHeader.source.software | |
Definition | May include configuration or other information useful in debugging. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Supports audit and possibly interface engine behavior. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MessageHeader.source.version | |
Definition | Can convey versions of multiple systems in situations where a message passes through multiple hands. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Supports audit and possibly interface engine behavior. |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
MessageHeader.source.contact | |
Definition | An e-mail, phone, website or other contact point to use to resolve issues with message communications. |
Cardinality | 0...1 |
Type | ContactPoint |
Summary | True |
Requirements | Allows escalation of technical issues. |
Invariants |
|
Mappings |
|
MessageHeader.source.endpoint | |
Definition | Identifies the routing target to send acknowledgements to. |
Cardinality | 1...1 |
Type | url |
Summary | True |
Requirements | Identifies where to send responses, may influence security permissions. |
Comments | The id may be a non-resolvable URI for systems that do not use standard network-based addresses. |
Invariants |
|
Mappings |
|
MessageHeader.responsible | |
Definition | 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. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole | Organization) |
Summary | True |
Requirements | Need to know for audit/traceback requirements and possibly for authorization. |
Comments | Usually only for the request but can be used in a response. |
Invariants |
|
Mappings |
|
MessageHeader.reason | |
Definition | Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this message. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Reason for event occurrence. |
Summary | True |
Requirements | Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. |
Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. |
Invariants |
|
Mappings |
|
MessageHeader.response | |
Definition | Information about the message that this message is a response to. Only present if this message is a response. |
Cardinality | 0...1 |
Type | BackboneElement |
Summary | True |
Invariants |
|
Mappings |
|
MessageHeader.response.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
MessageHeader.response.extension | |
Definition | 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 manageable, 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
MessageHeader.response.modifierExtension | |
Definition | 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 manageable, 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Comments | 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. |
Invariants |
|
Mappings |
|
MessageHeader.response.identifier | |
Definition | The MessageHeader.id of the message to which this message is a response. |
Cardinality | 1...1 |
Type | id |
Summary | True |
Requirements | Allows receiver to know what message is being responded to. |
Comments | RFC 4122 |
Invariants |
|
Mappings |
|
MessageHeader.response.code | |
Definition | Code that identifies the type of response to the message - whether it was successful or not, and whether it should be resent or not. |
Cardinality | 1...1 |
Type | code |
Binding | The kind of response to a message. |
Summary | True |
Requirements | Allows the sender of the acknowledge message to know if the request was successful or if action is needed. |
Comments | This is a generic response to the request message. Specific data for the response will be found in MessageHeader.focus. |
Invariants |
|
Mappings |
|
MessageHeader.response.details | |
Definition | Full details of any issues found in the message. |
Cardinality | 0...1 |
Type | Reference(OperationOutcome) |
Summary | True |
Requirements | Allows the sender of the message to determine what the specific issues are. |
Comments | This SHALL be contained in the bundle. If any of the issues are errors, the response code SHALL be an error. |
Invariants |
|
Mappings |
|
MessageHeader.focus | |
Definition | The actual data of the message - a reference to the root/focus class of the event. |
Cardinality | 0...* |
Type | Reference(Resource) |
Must Support | True |
Summary | True |
Requirements | Every message event is about actual data, a single resource, that is identified in the definition of the event, and perhaps some or all linked resources. |
Comments | 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. |
Invariants |
|
Mappings |
|
MessageHeader.definition | |
Definition | Permanent link to the MessageDefinition for this message. |
Cardinality | 0...1 |
Type | canonical(MessageDefinition) |
Summary | True |
Requirements | Allows sender to define the expected contents of the message. |
Comments | |
Invariants |
|
Mappings |
|
Table View
MessageHeader | .. | |
MessageHeader.event[x] | .. | |
MessageHeader.destination | .. | |
MessageHeader.sender | .. | |
MessageHeader.source | .. | |
MessageHeader.focus | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="UKCore-MessageHeader" /> <url value="https://fhir.hl7.org.uk/StructureDefinition/UKCore-MessageHeader" /> <version value="2.4.0" /> <name value="UKCoreMessageHeader" /> <title value="UK Core Message Header" /> <status value="draft" /> <date value="2024-07-11" /> <publisher value="HL7 UK" /> <contact> <name value="HL7 UK" /> <telecom> <system value="email" /> <value value="ukcore@hl7.org.uk" /> <use value="work" /> <rank value="1" /> </telecom> </contact> <description value="This profile defines the UK constraints and extensions on the International FHIR resource [MessageHeader](https://hl7.org/fhir/R4/MessageHeader.html)." /> <purpose value="This profile carries the header data for a message exchange that is either requesting or responding to an action." /> <copyright value="Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="MessageHeader" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/MessageHeader" /> <derivation value="constraint" /> <differential> <element id="MessageHeader.event[x]"> <path value="MessageHeader.event[x]" /> <mustSupport value="true" /> </element> <element id="MessageHeader.destination"> <path value="MessageHeader.destination" /> <mustSupport value="true" /> </element> <element id="MessageHeader.sender"> <path value="MessageHeader.sender" /> <mustSupport value="true" /> </element> <element id="MessageHeader.source"> <path value="MessageHeader.source" /> <mustSupport value="true" /> </element> <element id="MessageHeader.focus"> <path value="MessageHeader.focus" /> <mustSupport value="true" /> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "UKCore-MessageHeader", "url": "https://fhir.hl7.org.uk/StructureDefinition/UKCore-MessageHeader", "version": "2.4.0", "name": "UKCoreMessageHeader", "title": "UK Core Message Header", "status": "draft", "date": "2024-07-11", "publisher": "HL7 UK", "contact": [ { "name": "HL7 UK", "telecom": [ { "system": "email", "value": "ukcore@hl7.org.uk", "use": "work", "rank": 1 } ] } ], "description": "This profile defines the UK constraints and extensions on the International FHIR resource [MessageHeader](https://hl7.org/fhir/R4/MessageHeader.html).", "purpose": "This profile carries the header data for a message exchange that is either requesting or responding to an action.", "copyright": "Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "MessageHeader", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/MessageHeader", "derivation": "constraint", "differential": { "element": [ { "id": "MessageHeader.event[x]", "path": "MessageHeader.event[x]", "mustSupport": true }, { "id": "MessageHeader.destination", "path": "MessageHeader.destination", "mustSupport": true }, { "id": "MessageHeader.sender", "path": "MessageHeader.sender", "mustSupport": true }, { "id": "MessageHeader.source", "path": "MessageHeader.source", "mustSupport": true }, { "id": "MessageHeader.focus", "path": "MessageHeader.focus", "mustSupport": true } ] } }
Usage
This Profile has the following derived profiles:This Profile is referenced in the following Extensions:
This Profile is referenced in the following Profiles:
Feedback
Click here to:Report issue for UKCore-MessageHeader, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Examples
Discharge Summary - An example to illustrate a message header for a discharge summaryExample UKCore-MessageHeader-Discharge
Example Usage Scenarios
The following are feasible use cases for the UK Core OperationOutcome profile:
- Query for
- Exchange of
Profile Specific Implementation Guidance:
Minimum Viable Content
A minimum viable content that all provider and consumer systems SHALL support are the following elements.
Element | Reason |
---|---|
MessageHeader.event[x] |
Code for the event this message represents or link to event definition |
MessageHeader.destination |
The destination application which the message is intended for. |
MessageHeader.sender |
Real world sender of the message |
MessageHeader.source |
The source application from which this message originated. |
MessageHeader.focus |
The actual content of the message |
Extensions
More information about the extensions can be found using the links below.
Important note regarding the extension messageheader-response-request
.
This extension is defined in the FHIR R4 specification as having a root conformance of 1..1 which mandates the use of the extension if added to any profile. This is an error and has been amended in R5 but will not be updated in R4. Therefore this extension is not hardcoded in the profile as this is not the desired behaviour.
Extension | Context | Link | Comment |
---|---|---|---|
messageheader-response-request | MessageHeader | Core-defined Extension messageheader-response-request | This is a HL7 Core-defined extension that is used to indicate the response required to a message. |
Bindings (differential)
More information about the bindings to UK Core ValueSets can be found below.
Context | Strength | Link |
---|---|---|
MessageHeader.event | Example | ValueSet UKCore-MessageEvent |
destination
The resource referenced in MessageHeader.destination.target
SHOULD conform to the Profile UKCore-Device.
The resource referenced in MessageHeader.destination.receiver
SHOULD conform to one of the following:
sender
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
enterer
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
responsible
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
response
The resource referenced in MessageHeader.response.details
SHOULD conform to the Profile UKCore-OperationOutcome
focus
Where a UK Core profile exists the resource being referenced SHOULD conform to the profile.