DK MedCom Messaging
2.2.0 - release Denmark flag

This page is part of the DK MedCom Messaging (v2.2.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 - Detailed Descriptions

Active as of 2024-06-28

Definitions for the medcom-messaging-messageHeader resource profile.

Guidance on how to interpret the contents of this table can be found here

0. MessageHeader
2. MessageHeader.id
ShortEach message shall include a globally unique id.
Control1..?
Must Supporttrue
4. MessageHeader.text
ShortA 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.
Must Supporttrue
6. MessageHeader.event[x]
ShortThe event element shall contain a value from MedComMessagingMessageTypes
BindingThe codes SHALL be taken from MedComMessagingMessageTypes
(required to http://medcomfhir.dk/ig/terminology/ValueSet/medcom-messaging-messageTypes)
TypeCoding, uri
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]
Must Supporttrue
8. MessageHeader.event[x].code
Control1..?
10. MessageHeader.destination
Control1..?
SlicingThis element introduces a set of slices on MessageHeader.destination. The slices areUnordered and Closed, and can be differentiated using the following discriminators:
  • value @ $this.extension.value
  • 12. MessageHeader.destination:primary
    Slice Nameprimary
    Control1..1
    14. MessageHeader.destination:primary.extension
    Control1..?
    SlicingThis element introduces a set of slices on MessageHeader.destination.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
    • value @ url
    • 16. MessageHeader.destination:primary.extension:use
      Slice Nameuse
      Control1..1
      TypeExtension(MedComDestinationUseExtension) (Extension Type: Coding)
      Must Supporttrue
      18. MessageHeader.destination:primary.extension:use.value[x]
      [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
      Pattern Value{
        "system" : "http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-destinationUse",
        "code" : "primary"
      }
      20. MessageHeader.destination:primary.endpoint
      Must Supporttrue
      22. MessageHeader.destination:primary.receiver
      ShortThe primary reciever of the message
      Control1..?
      TypeReference(MedComMessagingOrganization)bundled
      Must Supporttrue
      24. MessageHeader.destination:cc
      Slice Namecc
      Control0..*
      26. MessageHeader.destination:cc.extension
      Control1..?
      SlicingThis element introduces a set of slices on MessageHeader.destination.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
      • value @ url
      • 28. MessageHeader.destination:cc.extension:use
        Slice Nameuse
        Control1..1
        TypeExtension(MedComDestinationUseExtension) (Extension Type: Coding)
        Must Supporttrue
        30. MessageHeader.destination:cc.extension:use.value[x]
        [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
        Pattern Value{
          "system" : "http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-destinationUse",
          "code" : "cc"
        }
        32. MessageHeader.destination:cc.endpoint
        Must Supporttrue
        34. MessageHeader.destination:cc.receiver
        ShortThe carbon copy reciever of the message. Is only used when a message has multiple recievers.
        Control1..?
        TypeReference(MedComMessagingOrganization)bundled
        Must Supporttrue
        36. MessageHeader.sender
        ShortThe actual sender of the message
        Control1..?
        TypeReference(MedComMessagingOrganization)bundled
        Must Supporttrue
        38. MessageHeader.source
        ShortContains the information about the target for the Acknowledgement message.
        Must Supporttrue
        40. MessageHeader.source.endpoint
        Must Supporttrue
        42. MessageHeader.definition
        Must Supporttrue