DK MedCom Messaging
2.0.0 - Build CI Denmark flag

This page is part of the DK MedCom Messaging (v2.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

Resource Profile: MedComMessagingMessageHeader

Official URL: http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-messageHeader Version: 2.0.0
Active as of 2024-02-15 Computable Name: MedComMessagingMessageHeader

MessageHeader for MedCom messages

Scope and usage

This profile describes the MessageHeader resource that shall be used in all MedCom FHIR Messages. A MedComMessagingMessageHeader shall include a sender and receiver and it may include a carbon-copy receiver, however this is depended on type of standard. Each MedComMessagingMessageHeader shall include a globally unique id, which is used to describe the message history from the MedComMessagingProvenance profile.

The element event shall be defined in accordance with the type of standard the message concerns e.g., HospitalNotification and CareCommunication. Due to the different requirements for each standard, it should be expected that the MedComMessagingMessageHeader is inherited in each standard.

Shows the MedComMessageHeader, which references the MedComMessagingOrganization as a sender, reciever and carbon-copy.

Please refer to the tab “Snapshot Table(Must support)” below for the definition of the required content of a MedComMessagingMessageHeader.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from MessageHeader

NameFlagsCard.TypeDescription & Constraintsdoco
.. MessageHeader 0..*MessageHeaderA resource that describes a message that is exchanged between systems
... id S1..1idEach message shall include a globally unique id.
... text S0..1NarrativeA summary of the resource content. The narrative text shall always be included when exchanging a MedCom message. All MustSupport elements and extensions shall be included.
... event[x] S1..1CodingThe event element shall contain a value from MedComMessagingMessageTypes
Binding: http://medcomfhir.dk/fhir/dk-medcom-terminology/ValueSet/medcom-messaging-messageTypes (required)
.... code 1..1codeSymbol in syntax defined by the system
.... destination:All Slices Content/Rules for all slices
..... Slices for extension 1..*ExtensionExtension
Slice: Unordered, Open by value:url
..... use S1..1CodingMedComDestinationUseExtension
URL: http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-destinationUseExtension
.... destination:primary S1..1BackboneElementMessage destination application(s)
..... use S1..1CodingMedComDestinationUseExtension
URL: http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-destinationUseExtension
...... value[x] 1..1CodingValue of extension
Required Pattern: At least the following
....... system1..1uriIdentity of the terminology system
Fixed Value: http://medcomfhir.dk/fhir/dk-medcom-terminology/CodeSystem/medcom-messaging-destinationUse
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: primary
..... endpoint S1..1urlActual destination address or id
..... receiver S1..1Reference(MedComMessagingOrganization) {b}The primary reciever of the message
.... destination:cc 0..*BackboneElementMessage destination application(s)
..... use S1..1CodingMedComDestinationUseExtension
URL: http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-destinationUseExtension
...... value[x] 1..1CodingValue of extension
Required Pattern: At least the following
....... system1..1uriIdentity of the terminology system
Fixed Value: http://medcomfhir.dk/fhir/dk-medcom-terminology/CodeSystem/medcom-messaging-destinationUse
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: cc
..... endpoint S1..1urlActual destination address or id
..... receiver S1..1Reference(MedComMessagingOrganization) {b}The carbon copy reciever of the message. Is only used when a message has multiple recievers.
... sender S1..1Reference(MedComMessagingOrganization) {b}The actual sender of the message
... source S1..1BackboneElementContains the information about the target for the Acknowledgement message.
.... endpoint S1..1urlActual message source address or id

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
MessageHeader.event[x]requiredhttp://medcomfhir.dk/fhir/dk-medcom-terminology/ValueSet/medcom-messaging-messageTypes
http://medcomfhir.dk/fhir/dk-medcom-terminology/ValueSet/medcom-messaging-messageTypes

 

Other representations of profile: CSV, Excel, Schematron