Table of contents
Note: Clinical guidelines for application and use cases are available in both Danish and English. The remaining documentation will solely be in English.
This page presents MedCom’s CareCommunication standard (Danish: Korrespondancemeddelelse). In time, this standard will replace the existing standards DIS91 and XDIS91. The purpose of the standard is to support secure digital communication between social care, the psychiatric area and the somatic sector. CareCommunication standard enable communication of personally identifiable information and is typically used for ad hoc communication. However, the CareCommunication must only be used in areas where no other MedCom standard is available, and it must not be used for cases with an acute nature.
The standard documentation below provides the necessary content to understand the needs for CareCommunication, the role of the CareCommunication, what to implement and how to get a MedCom Certificate. The standard documentation for CareCommunication includes:
The clinical guidelines for application are the foundation for the CareCommunication standard. It describes the clinical needs for the CareCommunication, the requirements for the content of the standard and how the standard supports the business requirements. It is the primary textual part of the documentation for CareCommunication. It is important for both implementers and business specialists to understand the clinical guidelines for application to ensure that the implemented standard supports the requirements.
Below, the clinical guidelines for application can be found (the information is in Danish):
Danish: Sundhedsfaglige retningslinjer for anvendelse
Note: Clinical guidelines for application in English are in preparation. As soon as they are ready, they will be published.
Use cases describe the different scenarios in which a standard support. For a certain real-world scenario, it describes the requirements for the content of a message. The purpose of the use cases is to ensure a coherent implementation and use of CareCommunication. The descriptions are targeted IT system vendors and the people responsible for the implementation in regions and municipalities.
Note: Use cases for CareCommunication in English, are currently in preparation. As soon as they are, ready they will be published.
The technical specifications for the MedCom CareCommunication is composed by profiles from two basis IG’s and from one terminology IG. Links to the IG’s are listed below:
The link below gives an overview of the included profiles, what their purpose is, and which elements the system should support. Furthermore, the structure of the standard is described and supported with examples in different degrees of technical skills.
Mapping from previous OIOXML standards to the FHIR CareCommunication standard can be found below. The document is intended to help translate the previous standard to the new FHIR standard. Please notice that not all elements from XDIS91are transferred to the CareCommunication, as not all elements are represented in the FHIR standard.
Furthermore, not all elements from the FHIR elements are represented in the document; thus, it cannot stand alone for implementation.
Click here to see the mapping from the previous OIOXML standard (XDIS91) to the FHIR CareCommunication standard.
Certification of a system implies both an approved test protocol and a run trough of TouchStone test scripts. TouchStone describes an infrastructure that allows automated test and validation against the IG’s developed by MedCom.
The test protocols in English and test scripts are currently in preparation. As soon as they are ready, they will be published below.
Sending a CareCommunication
Receiving a CareCommunication