DK MedCom Carecommunication
4.0.0 - release Denmark flag

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

Resource Profile: MedComCareCommunicationProvenance

Official URL: http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-provenance Version: 4.0.0
Active as of 2024-06-28 Computable Name: MedComCareCommunicationProvenance

Provenance information about the current and preceeding message.

Scope and usage

This profile is used as the Provenance in a CareCommunication message. This profile inherits from MedComMessagingProvenance and must be used as Provenance instance in the CareCommuncation message. The Provenance resource tracks information about the activity what was created, while referencing the current message and previous messages if such exist. Further, does the profile include the identifier of the message segment (also referred to as payload).

Entities

The element Provenance.entity is sliced. One slice is called payload, and contains the identifier for the payloads added in the current CareCommunication. The second slice is called previousMessage is used when the message is a reply or forwarding. In these cases, the Provenance.entity must refer to the previous message.

Please refer to the tab “Snapshot Table” below for the definition of the required content of a MedComCareCommunicationMessageHeader.

Usage:

Formal Views of Profile Content

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

This structure is derived from MedComMessagingProvenance

NameFlagsCard.TypeDescription & Constraintsdoco
.. Provenance 0..* MedComMessagingProvenance Who, What, When for a set of resources
... target 1..1 Reference(MedComCareCommunicationMessageHeader) Targets the MedComMessagingMessageHeader from the current message.
... activity 1..1 CodeableConcept Activity that occurred
Binding: MedComCareCommunicationMessageActivityCodes (required)
... Slices for entity 1..* BackboneElement An entity used in this activity
Slice: Unordered, Closed by value:role
.... entity:preceedingMessage S 0..1 BackboneElement Shall be included when the current message is a response to a previous FHIR message.
..... role 1..1 code When a message is a response or a forwarding message the role shall be 'revision'.
Required Pattern: revision
..... what 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 0..1 string If the previous message is a FHIR message, this element must contain the MessageHeader.id from previous message.
...... identifier 0..1 Identifier If the previous message is EDIFACT or OIOXML, this element must be expressed as [lokationsnummer]#[brevid] from the EDIFACT or OIOXML message.
.... entity:payload S 1..* BackboneElement An identifier for the payload included during this revision. If more payloads are added, each payload must be represented with an individual entity.
..... role 1..1 code The role shall be 'source' or 'revision'.
Required Pattern: source
..... what 1..1 Reference(Resource) A reference to the payload included in this message.
...... identifier 1..1 Identifier The identifier of the newly included Communication.payload.extension.valueIdentifier must be included here.

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Provenance.activityrequiredMedComCareCommunicationMessageActivities
http://medcomfhir.dk/ig/terminology/ValueSet/medcom-careCommunication-messagingActivities

 

Other representations of profile: CSV, Excel, Schematron