DK MedCom Messaging
2.2.0 - release
DK MedCom Messaging
2.2.0 - release
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
| Official URL: http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-provenance | Version: 2.2.0 | |||
| Active as of 2024-06-28 | Computable Name: MedComMessagingProvenance | |||
Provenance information about the messages preceeding the current message
This profile is used as the Provenance resource for MedCom FHIR messages. The Provenance resource tracks information about the activity what was created, revised, or deleted, while referencing the current message and previous messages if such exist. This is why the Provenance resource is valuable in MedCom messaging.
MedComMessagingProvenance describes the activity and history of a message. The element Provenance.agent.who contains information about the organisation that was involved in the activity, the element Provenance.target references the MessageHeader in the current message, and the element Provenance.what references the event that initiated a message e.g., a previous message.
The figure below illustrates the references from the Provenance resource.
Please refer to the tab “Snapshot Table(Must support)” below for the definition of the required content of a MedComMessagingProvenance.
In MedCom messaging, the Provenance.target shall always be a reference to a MedComMessagingMessageHeader or an inherited of MedComMessagingMessageHeader. The target references the resources on which the activity has occurred. For instances if Provenance.activity is ‘new-message’, it describes that the message referenced from the Messageheader is a new message.
The activitycodes used to describe the activity of the MedCom message may differ between standard e.g. HospitalNotification and CareCommunication. Due to the different requirements of activities in a standard, it should be expected that there will be different invariants pointing at specific ValueSets for the given standard.
Provenance.agent describes the actor who is responsible for the activity that took place, by referencing the organisation responsible for the activity. The referenced organisation shall be an MedComMessagingOrganization.
MedComMessagingProvenance handles the message history in the Provenacne.entity element. This element shall be included if the message is a response to a previous message. In this case the element Provenance.entity.role is used to describe how the entity is used in the message. Provenance.entity.role shall be:
When a message is a response to a previous message, the previous message shall be referenced from the element Provenance.entity.what. The reference depends on the type of the previous message, which can be a MedCom FHIR message or a EDIFACT/OIOXML message. In the latter case, the reference shall be [lokationsnummer]#[brevid].
In MedComMessagingProvenance there are two timestamps, that represents the date and time the message was sent but in two different ways. Provenance.occuredDateTime is a human readable date and time and Provenance.recorded is a machine readable date and time.
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
This structure is derived from Provenance
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
  Provenance |
0..* | Provenance | Who, What, When for a set of resources | |
  text |
S | 0..1 | Narrative | Text summary of the resource, for human interpretation |
 target |
S | 1..1 | Reference(MedComMessagingMessageHeader) | Targets the MedComMessagingMessageHeader from the current message. |
  Slices for occurred[x] |
1..1 | dateTime | When the activity occurred Slice: Unordered, Open by type:$this | |
   occurred[x]:occurredDateTime |
S | 1..1 | dateTime | A human readable date and time for when the message is sent. Shall include a date, a time and timezone. |
| recorded |
S | 1..1 | instant | A system readable date and time for when the message is sent. |
| activity |
S | 1..1 | CodeableConcept | Activity that occurred Binding: MedComMessagingActivityCodes (required) |
 coding |
S | 1..* | Coding | Code defined by a terminology system |
  code |
S | 1..1 | code | Symbol in syntax defined by the system |
| agent |
S | 1..* | BackboneElement | The actors involved in the activity taking place |
| who |
S | 1..1 | Reference(MedComMessagingOrganization) {b} | A reference to the actor of the activity, which shall be a MedComMessagingOrganization. If more actors has been involved, the element must be sliced. |
| entity |
S | 0..* | BackboneElement | An entity used in this activity |
| role |
S | 1..1 | code | When 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'. |
| what |
S | 1..1 | Reference(Resource) | A 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. |
| reference |
S | 0..1 | string | If the previous message is a FHIR message, this element must hold the MessageHeader.id from previous message. |
| identifier |
S | 0..1 | Identifier | If previous message is EDIFACT or OIOXML, this element must be expressed as [lokationsnummer]#[brevid] from the EDIFACT or OIOXML message. |
| Documentation for this format | ||||
| Path | Conformance | ValueSet | URI |
| Provenance.activity | required | MedComMessagingActivityCodeshttp://medcomfhir.dk/ig/terminology/ValueSet/medcom-messaging-activityCodes |
Other representations of profile: CSV, Excel, Schematron
