DK MedCom Carecommunication
4.0.2 - release
DK MedCom Carecommunication
4.0.2 - release
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
This section describes five subsequent CareCommunications sent between three healthcare departments concerning the same citizen with test-CPR-nr. 250947-9989. The flow that the examples support is:
A sends a new message to B
B replies to A
A replies to B
B forwards to C
C replies to B
The initial message sent from Hjerteafdelingen på Herlev og Gentofte hospital to Plejecenter Herlev.
The message includes one message segment and a new communication identifier. As it is a new message, the activity is in the Provenance instance 'new-message'. The sender and receiver organizations are both referenced from the MessageHeader.
The CareCommunication contains a topic at Communication.topic.
A reply to the 1st message. Since it is a reply to the latest CareCommunication, the Communication.identifier remains the same. Two Communication.payload is added which includes the reply to the new message, since a message text and an attachment are included. The activity is in the Provenance instance 'reply-message'.
The author of the second CareCommunication has included an attachment without structured author information.
This is a reply to the 2nd message. Therefore, the Communication.identifier remains the same. One Communication.payload has been added with the reply. The base64-encoded content from the attachment in the 2nd message is not included, only the identifier and author information. The unique ids of the instances are updated, however the referenced MessageHeader in the Provenance instances from the previous messages remain the same.
This is a forwarding of the 3rd message. Therefore is the Communication.identifier updated and the base64-encoded content from the attachment in the 2nd message is included. Additionally, is a Communciation.payload added with a reason for the forwarding. The user decides not to forward the topic, why it is not included in the CareCommunication. The activity in the Provenance instance is 'forward-message'. A new receiver organization is included. The sender organization does not include a name in Organization.name.
Is a reply to the 4th message. The Communication.identifier remains the same and the base64-encoded content from the attachment in the 2nd message is not included. The user has included a new attachment, which is a link to a webpage. The author role is not from the list of roles, but is included as at PractitionerRole.code.text.
The examples below demonstrates how different information is included in a CareCommunication.
CareCommunication with all optional content
This includes
CareCommunication where the patient has a replacement-CPR.
It is allowed to send a CareCommunication for a patient with a replacement-CPR (Danish: erstatnings-CPR or ecpr). In the example, the replacement-CPR is from the national eCPR service, defined by the Patient.identifier.system = "urn:oid:1.2.208.176.1.6.1.1". Further, an EpisodeOfCare-identifier (Danish: forløbsid) is included in the Encounter instance.
It is allowed to answer a received MedCom EDIFACT or OIOXML message with a MedCom CareCommunication. The Provenance.entity.what.identifier shall contain a reference to the received OIOXML. The reference shall contain the locationnumber and letter identifier, divided by #. If the message being replied contains an episodOfCareIdentifier, this shall be included in the CareCommunication message.