DK MedCom Carecommunication
4.0.2 - release Denmark flag

DK MedCom Carecommunication, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 4.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-medcom-carecommunication/ and changes regularly. See the Directory of published versions

Resource Profile: MedComCareCommunicationProvenance - Examples

Active as of 2025-04-09

Examples for the medcom-careCommunication-provenance Profile.

receive_A-new - Provenance
receive-Tek-J-duplicate - Provenance
Receive_Tek-D - Provenance
receive_Tek-L-dublicate - Provenance
Send-Tek-A-new - Provenance
Send-A-new - Provenance
receive_C-forward - Provenance
Send-E-forward - Provenance
Send-B-new - Provenance
receive-Tek-G - Provenance
4th message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded
2nd message - The Provenance instance is only valid if used in a bundle (message) - reply to new message
receive-Tek-O-invalid - Provenance
CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to OIOXML-message
3rd message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded
CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message
Send-E-forward - Provenance
Send-D-new - Provenance
Send-C-new - Provenance
receive-Tek-M-new-dublicate-inv - Provenance
1st message - The Provenance instance is only valid if used in a bundle (message) - new message
Send-Tek-B-new - Provenance
Receive_Tek-A - Provenance
Receive_Tek-C - Provenance
CareCommunication Flow 1 Provenance
Receive_Tek-B - Provenance