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: MedComMessagingProvenance - Detailed Descriptions

Active as of 2024-06-28

Definitions for the medcom-messaging-provenance resource profile.

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

0. Provenance
2. Provenance.text
Must Supporttrue
4. Provenance.target
ShortTargets the MedComMessagingMessageHeader from the current message.
Control0..1
TypeReference(MedComMessagingMessageHeader)
Must Supporttrue
6. Provenance.occurred[x]
Control1..?
[x] NoteSeeChoice of Data Typesfor further information about how to use [x]
SlicingThis element introduces a set of slices on Provenance.occurred[x]. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • type @ $this
  • 8. Provenance.occurred[x]:occurredDateTime
    Slice NameoccurredDateTime
    ShortA human readable date and time for when the message is sent. Shall include a date, a time and timezone.
    Control1..1
    TypedateTime
    [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    Must Supporttrue
    10. Provenance.recorded
    ShortA system readable date and time for when the message is sent.
    Must Supporttrue
    12. Provenance.activity
    Definition

    Activity that occurred and triggered the current or a previous message

    Control1..?
    BindingThe codes SHALL be taken from MedComMessagingActivityCodes
    (required to http://medcomfhir.dk/ig/terminology/ValueSet/medcom-messaging-activityCodes)
    Must Supporttrue
    14. Provenance.activity.coding
    Control1..?
    Must Supporttrue
    16. Provenance.activity.coding.code
    Definition

    The activity defined by the system

    Control1..?
    Must Supporttrue
    18. Provenance.agent
    ShortThe actors involved in the activity taking place
    Must Supporttrue
    20. Provenance.agent.who
    Definition

    Shall contain the messaging organization performing the activity. This also apply to an internal transmission to another messaging organization within a given system.

    ShortA reference to the actor of the activity, which shall be a MedComMessagingOrganization. If more actors has been involved, the element must be sliced.
    TypeReference(MedComMessagingOrganization)bundled
    Must Supporttrue
    22. Provenance.entity
    Definition

    Shall only be included if the current message is a response to a previous message.

    Must Supporttrue
    24. Provenance.entity.role
    ShortWhen a message is a response, a correction or a forwarding message the role shall be 'revision' and when the message is a cancellation the role shall be 'removal'.
    Must Supporttrue
    26. Provenance.entity.what
    ShortA reference to the previous message. If the previous message is a FHIR message, the reference element must be used and if the previous message is an EDIFACT or OIOXML, the identifier element must be used.
    Must Supporttrue
    28. Provenance.entity.what.reference
    Definition

    Shall contain the message header id of messages given as input to the activity

    ShortIf the previous message is a FHIR message, this element must hold the MessageHeader.id from previous message.
    Must Supporttrue
    30. Provenance.entity.what.identifier
    Definition

    Shall contain the message header id of messages given as input to the activity if the previous message is not a fhir message

    ShortIf previous message is EDIFACT or OIOXML, this element must be expressed as [lokationsnummer]#[brevid] from the EDIFACT or OIOXML message.
    NoteThis is a business identifier, not a resource identifier (see discussion)
    Must Supporttrue