|
Type
|
Reference
|
Content
|
|
web
|
tel:+4538683868
|
ContactExtension
: +4538683868
|
|
web
|
tel:+4523232323
|
ContactExtension
: +4523232323
|
|
web
|
tel:+4512345789
|
ContactExtension
: +4512345789
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=953741000016009
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=265161000016000
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=330461000016004
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=441211000016000
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=1042981000016003
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=1017421000016003
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=1053231000016001
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=328081000016004
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=328051000016008
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=359001000016000
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=1385391000016002
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=953751000016007
|
|
web
|
www.medcom.dk
|
|
|
web
|
github.com
|
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
|
|
web
|
www.medcom.dk
|
IG © 2021+ MedCom
. Package medcom.fhir.dk.carecommunication#4.0.2 based on FHIR 4.0.1
. Generated 2025-04-09
Links: Table of Contents |
QA Report
| Accessibility statement (Tilgængelighedserklæring)
|
|
web
|
www.was.digst.dk
|
Links: Table of Contents
|
QA Report
| Accessibility statement (Tilgængelighedserklæring)
|
|
web
|
medcomfhir.dk
|
This profile is used as the Communication resource for the MedCom CareCommunication message. The MedComCareCommunication
profile contains the main content of a message, which includes a communication identifier, at least one message segment with a message text (Danish: Meddelelsestekst) and a signature. The message may include zero or more message segments with an attachment and a signature. All message segments are found under the element Communication.payload. A more detailed description of the content of the MedComCareCommunication profile can be seen below.
|
|
web
|
medcomfhir.dk
|
The figure below shows the possible references from MedComCareCommunication profile, and thereby which resources that may be included in a CareCommunication message. A subject, in terms of a MedComCorePatient
, shall always be included since a CareCommunication message always concerns a patient or citizen's matter. A MedComCorePractitionerRole
and MedComCorePractitioner
shall be included since these reference includes information about the author of the message text. A MedComCoreEncounter
may be referenced if an episodeOfCare-identifier (Danish: forløbs-id) is relevant to include. Further, the MedComCorePractitionerRole
or MedComCoreCareTeam
may be included if a recipient or sender is added. Both profiles includes a reference to the MedComCoreOrganization
the CareTeam or Practitioner is a part of.
|
|
web
|
medcomfhir.dk
|
The figure below shows the possible references from MedComCareCommunication profile, and thereby which resources that may be included in a CareCommunication message. A subject, in terms of a MedComCorePatient
, shall always be included since a CareCommunication message always concerns a patient or citizen's matter. A MedComCorePractitionerRole
and MedComCorePractitioner
shall be included since these reference includes information about the author of the message text. A MedComCoreEncounter
may be referenced if an episodeOfCare-identifier (Danish: forløbs-id) is relevant to include. Further, the MedComCorePractitionerRole
or MedComCoreCareTeam
may be included if a recipient or sender is added. Both profiles includes a reference to the MedComCoreOrganization
the CareTeam or Practitioner is a part of.
|
|
web
|
medcomfhir.dk
|
The figure below shows the possible references from MedComCareCommunication profile, and thereby which resources that may be included in a CareCommunication message. A subject, in terms of a MedComCorePatient
, shall always be included since a CareCommunication message always concerns a patient or citizen's matter. A MedComCorePractitionerRole
and MedComCorePractitioner
shall be included since these reference includes information about the author of the message text. A MedComCoreEncounter
may be referenced if an episodeOfCare-identifier (Danish: forløbs-id) is relevant to include. Further, the MedComCorePractitionerRole
or MedComCoreCareTeam
may be included if a recipient or sender is added. Both profiles includes a reference to the MedComCoreOrganization
the CareTeam or Practitioner is a part of.
|
|
web
|
medcomfhir.dk
|
The figure below shows the possible references from MedComCareCommunication profile, and thereby which resources that may be included in a CareCommunication message. A subject, in terms of a MedComCorePatient
, shall always be included since a CareCommunication message always concerns a patient or citizen's matter. A MedComCorePractitionerRole
and MedComCorePractitioner
shall be included since these reference includes information about the author of the message text. A MedComCoreEncounter
may be referenced if an episodeOfCare-identifier (Danish: forløbs-id) is relevant to include. Further, the MedComCorePractitionerRole
or MedComCoreCareTeam
may be included if a recipient or sender is added. Both profiles includes a reference to the MedComCoreOrganization
the CareTeam or Practitioner is a part of.
|
|
web
|
medcomfhir.dk
|
The figure below shows the possible references from MedComCareCommunication profile, and thereby which resources that may be included in a CareCommunication message. A subject, in terms of a MedComCorePatient
, shall always be included since a CareCommunication message always concerns a patient or citizen's matter. A MedComCorePractitionerRole
and MedComCorePractitioner
shall be included since these reference includes information about the author of the message text. A MedComCoreEncounter
may be referenced if an episodeOfCare-identifier (Danish: forløbs-id) is relevant to include. Further, the MedComCorePractitionerRole
or MedComCoreCareTeam
may be included if a recipient or sender is added. Both profiles includes a reference to the MedComCoreOrganization
the CareTeam or Practitioner is a part of.
|
|
web
|
medcomfhir.dk
|
The figure below shows the possible references from MedComCareCommunication profile, and thereby which resources that may be included in a CareCommunication message. A subject, in terms of a MedComCorePatient
, shall always be included since a CareCommunication message always concerns a patient or citizen's matter. A MedComCorePractitionerRole
and MedComCorePractitioner
shall be included since these reference includes information about the author of the message text. A MedComCoreEncounter
may be referenced if an episodeOfCare-identifier (Danish: forløbs-id) is relevant to include. Further, the MedComCorePractitionerRole
or MedComCoreCareTeam
may be included if a recipient or sender is added. Both profiles includes a reference to the MedComCoreOrganization
the CareTeam or Practitioner is a part of.
|
|
web
|
medcomdk.github.io
|
The purpose of the communication identifier, in the element Communication.identifier.value, is to ensure a common identifier for a communication. This will help systems to connect incoming and outgoing CareCommuncations. This identifier must be a UUID v4 and it must remain the same when replying to a CareCommunication. The identifier must be updated when a CareCommunication is forwarded. This is elaborated in the Governance for CareCommunication
.
|
|
web
|
medcomfhir.dk
|
A CareCommunication shall have a category (Danish: Kategori), in the element Communication.category. The category describes the overall content of the communication and shall be selected from a nationally agreed list of categories defined in the ValueSet of category codes
. Exactly one category code must be included in a CareCommunication. In time, new category codes may be relevant to include or existing codes may be irrelevant, why it should be expected that the ValueSet will change. Changes will be made in agreement with the business and will be warned.
|
|
web
|
medcomdk.github.io
|
In addition to the category, it is allowed to add a topic (Danish: Emne) in the element Communication.topic, to support and elaborate the category. This can either be inserted as free text or as regionally agreed codes, which is describes further in the clinical guidelines for application
.
|
|
web
|
medcomdk.github.io
|
Priority, found in the element Communication.priority, is used to support the referral flow. It is only allowed to add a priority to a CareCommunication when the category of the message is regarding referral
. In this case, priority can either be routine
or asap
. To ensure this, the invariant medcom-careCommunication-5 is created, which states that in no other case than when the category is regarding referral
, a priority must be added. As described on clinical guidelines for application
, the use of priority must follow the development in collective agreements and on basis of national requirements.
|
|
web
|
medcomfhir.dk
|
Message text:
The written content of the message is of the datatype string
defined by HL7. The signature for the message text consists of author name, author role, relevant phone number, and sent timestamp. The identifier is included for technical purposes. See the table below for an overview of the requirements.
Attachment:
The allowed types of attachments can be found in the ValueSet of allowed mimetypes
. Further, it is allowed to include a link to a website. In a message segment with an attachment, the title, identifier and timestamp must be included, whereas it is optional to include information about the author, relevant phone number and creation date as structured data. See the table below for an overview of the requirements.
|
|
web
|
medcomfhir.dk
|
A description of the above mentioned information can be found here:
Author name:
The name of the person responsible for writing the message text. The author shall be described using a MedComCorePractitioner
profile.
Author role:
The role (Danish: stillingsbetegnelse) of the person responsible for writing the message text. The author role shall be described using a MedComCorePractitionerRole
profile. It is recommended to use a role from the defined list of roles in the element PractitionerRole.code.coding.code. Alternatively, a it is allowed to add a role in the element PractitionerRole.code.text.
Relevant phone number:
A relevant phone number e.g. to the department from which the CareCommunication is sent. The phone number should be applied automatically. In case it is not possible to apply the phone number automatically, it shall be applied by the author.
Timestamp:
Represents the real world event, where the user presses "send" to send the CareCommunication.
Identifier:
An UUID version 4 with a reference to the organisation who assigned the identifier, which will be the same as the sender organisation of the message segment.
Title:
The title of the attached file. This should be applied by the system.
Creation:
The date and time for when the attachment is created.
|
|
web
|
medcomfhir.dk
|
A description of the above mentioned information can be found here:
Author name:
The name of the person responsible for writing the message text. The author shall be described using a MedComCorePractitioner
profile.
Author role:
The role (Danish: stillingsbetegnelse) of the person responsible for writing the message text. The author role shall be described using a MedComCorePractitionerRole
profile. It is recommended to use a role from the defined list of roles in the element PractitionerRole.code.coding.code. Alternatively, a it is allowed to add a role in the element PractitionerRole.code.text.
Relevant phone number:
A relevant phone number e.g. to the department from which the CareCommunication is sent. The phone number should be applied automatically. In case it is not possible to apply the phone number automatically, it shall be applied by the author.
Timestamp:
Represents the real world event, where the user presses "send" to send the CareCommunication.
Identifier:
An UUID version 4 with a reference to the organisation who assigned the identifier, which will be the same as the sender organisation of the message segment.
Title:
The title of the attached file. This should be applied by the system.
Creation:
The date and time for when the attachment is created.
|
|
web
|
medcomfhir.dk
|
In the element Communication.encounter it is possible to reference a MedComCoreEncounter
. An encounter describes the meeting between a patient and one or more healthcare providers or actors involved in the patient care. The Encounter resource contains an episodeOfCare-identifier. When receiving a message, either CareCommunication or EDIFACT/OIOXML message, there will in many cases be an episodeOfCare-identifier, as it described the id of the contact. If this is the case, the episodeOfCare-identifier shall always be included in the response. Altenatively, when a user at a hospital is in the context of e.g. an admission, the episodeOfCare-identifier should be coupled to a CareCommunication.
Click here to get more information about the episodeOfCare-identifier
|
|
web
|
medcomdk.github.io
|
In the element Communication.encounter it is possible to reference a MedComCoreEncounter
. An encounter describes the meeting between a patient and one or more healthcare providers or actors involved in the patient care. The Encounter resource contains an episodeOfCare-identifier. When receiving a message, either CareCommunication or EDIFACT/OIOXML message, there will in many cases be an episodeOfCare-identifier, as it described the id of the contact. If this is the case, the episodeOfCare-identifier shall always be included in the response. Altenatively, when a user at a hospital is in the context of e.g. an admission, the episodeOfCare-identifier should be coupled to a CareCommunication.
Click here to get more information about the episodeOfCare-identifier
|
|
web
|
medcomfhir.dk
|
In the MedComCareCommunicationMessageHeader
profile it is required to include information about a sender and receiver in terms of a reference to a MedComMessagingOrganization
. This information is primarily used for transportation matters and will always include an EAN-number and SOR-identifier for each organisation.
|
|
web
|
medcomfhir.dk
|
In the MedComCareCommunicationMessageHeader
profile it is required to include information about a sender and receiver in terms of a reference to a MedComMessagingOrganization
. This information is primarily used for transportation matters and will always include an EAN-number and SOR-identifier for each organisation.
|
|
web
|
medcomfhir.dk
|
When sending a CareCommunication message it is possible to add a more specific receiver of the message, called a recipient, and a more specific sender, which can be found in the elements Communication.recipient and Communication.extension.sender, respectively. It is allowed to reference a MedComCoreCareTeam
, which is people or an organization participating a coordination or delivery of patientcare, or MedComCorePractitionerRole
, which references a MedComCorePractitioner to address a healthcare professional involved in patient care. Common for both MedComCoreCareTeam and MedComCorePractitionerRole/MedComCorePractitioner is that a name of the careteam or practitioner should be included as well as a reference to a MedComCoreOrganization which represents the sender or receiver defined in MedComCareCommunicationMessageHeader
.
|
|
web
|
medcomfhir.dk
|
When sending a CareCommunication message it is possible to add a more specific receiver of the message, called a recipient, and a more specific sender, which can be found in the elements Communication.recipient and Communication.extension.sender, respectively. It is allowed to reference a MedComCoreCareTeam
, which is people or an organization participating a coordination or delivery of patientcare, or MedComCorePractitionerRole
, which references a MedComCorePractitioner to address a healthcare professional involved in patient care. Common for both MedComCoreCareTeam and MedComCorePractitionerRole/MedComCorePractitioner is that a name of the careteam or practitioner should be included as well as a reference to a MedComCoreOrganization which represents the sender or receiver defined in MedComCareCommunicationMessageHeader
.
|
|
web
|
medcomfhir.dk
|
When sending a CareCommunication message it is possible to add a more specific receiver of the message, called a recipient, and a more specific sender, which can be found in the elements Communication.recipient and Communication.extension.sender, respectively. It is allowed to reference a MedComCoreCareTeam
, which is people or an organization participating a coordination or delivery of patientcare, or MedComCorePractitionerRole
, which references a MedComCorePractitioner to address a healthcare professional involved in patient care. Common for both MedComCoreCareTeam and MedComCorePractitionerRole/MedComCorePractitioner is that a name of the careteam or practitioner should be included as well as a reference to a MedComCoreOrganization which represents the sender or receiver defined in MedComCareCommunicationMessageHeader
.
|
|
web
|
en.wikipedia.org
|
Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS
).
|
|
web
|
medcomdk.github.io
|
More information about the clinical guidelines for applications
can be found here.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessage
is a constraint of MedComMessagingMessage
further to use the MedComCareCommunicationMessageHeader
and to require exactly one MedComCorePatient
resource in the message. Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComCareCommunicationMessageActivities ValueSet
, which contains the activities new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessage
is a constraint of MedComMessagingMessage
further to use the MedComCareCommunicationMessageHeader
and to require exactly one MedComCorePatient
resource in the message. Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComCareCommunicationMessageActivities ValueSet
, which contains the activities new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessage
is a constraint of MedComMessagingMessage
further to use the MedComCareCommunicationMessageHeader
and to require exactly one MedComCorePatient
resource in the message. Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComCareCommunicationMessageActivities ValueSet
, which contains the activities new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessage
is a constraint of MedComMessagingMessage
further to use the MedComCareCommunicationMessageHeader
and to require exactly one MedComCorePatient
resource in the message. Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComCareCommunicationMessageActivities ValueSet
, which contains the activities new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessage
is a constraint of MedComMessagingMessage
further to use the MedComCareCommunicationMessageHeader
and to require exactly one MedComCorePatient
resource in the message. Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComCareCommunicationMessageActivities ValueSet
, which contains the activities new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessageHeader
constrains the MedComMessagingMessageHeader
further to specify the fixed coding for this message and require a focus reference to a MedComCareCommunication profile.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationMessageHeader
constrains the MedComMessagingMessageHeader
further to specify the fixed coding for this message and require a focus reference to a MedComCareCommunication profile.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunication
profile contains the main content of the message. It based on the Communication resource. MedComCareCommunication profile shall include a category code as defined in the MedComCareCommunicationCategories ValueSet
and it is allowed to add a topic of the message which may be in free text or from a regionally agreed list of topics that supports and elaborates the category.
|
|
web
|
medcomfhir.dk
|
The MedComCorePatient
profile is used in a CareCommunication. It is preferred that a CareCommunication is being sent for a patient with an official Danish civil registration number (CPR)-number. In cases where a CPR-number is not known, a replacement CPR-number (Danish: Erstatnings-CPR) shall be included.
|
|
web
|
medcomfhir.dk
|
The MedComCorePractitionerRole
and MedComCorePractitioner
profiles are used to describe the author in the signature of a message text by name and role (Danish: Stillingsbetegnelse). The MedComCorePractitionerRole is referenced from the MedComCareCommunication profile and MedComCorePractitionerRole includes a reference to the MedComCorePractitioner, why both profiles are shown on Figure 1
.
|
|
web
|
medcomfhir.dk
|
The MedComCorePractitionerRole
and MedComCorePractitioner
profiles are used to describe the author in the signature of a message text by name and role (Danish: Stillingsbetegnelse). The MedComCorePractitionerRole is referenced from the MedComCareCommunication profile and MedComCorePractitionerRole includes a reference to the MedComCorePractitioner, why both profiles are shown on Figure 1
.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationProvenance
profile is used to track information about the activity of the communication, e.g. if the message describes a 'new-message' or 'reply-message'. Activity codes can be found in MedComCareCommunicationMessageActivityCodes ValueSet
on the Terminology IG. Note that all not activity codes are allowed for a CareCommunication. The allowed activity codes are: new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
The MedComCareCommunicationProvenance
profile is used to track information about the activity of the communication, e.g. if the message describes a 'new-message' or 'reply-message'. Activity codes can be found in MedComCareCommunicationMessageActivityCodes ValueSet
on the Terminology IG. Note that all not activity codes are allowed for a CareCommunication. The allowed activity codes are: new-message, reply-message and forward-message.
|
|
web
|
medcomfhir.dk
|
A CareCommunication includes several timestamps. These timestamps are present in the profiles MedComCareCommunication
, MedComCareCommunicationMessage
, and MedComMessagingProvenance
and have different purposes:
|
|
web
|
medcomfhir.dk
|
A CareCommunication includes several timestamps. These timestamps are present in the profiles MedComCareCommunication
, MedComCareCommunicationMessage
, and MedComMessagingProvenance
and have different purposes:
|
|
web
|
medcomdk.github.io
|
All instances of a profile shall have a global unique id by using an UUID. Read more about the use of ids here
.
|
|
web
|
hl7.dk
|
This IG has a dependency to the MedCom Core IG
, MedCom Messaging IG
and DK-core v. 2.0.0
, where the latter is defined by HL7 Denmark
. These dependencies are currently reflected in MedComCareCommunicationMessage, and MedComCareCommunicationMessageHeader which both inherits from profiles defined MedComMessaging IG. Further, it is reflected in references to MedComCorePatient, MedComCoreEncounter, MedComCoreOrganization and MedComMessagingOrganization.
|
|
web
|
hl7.dk
|
This IG has a dependency to the MedCom Core IG
, MedCom Messaging IG
and DK-core v. 2.0.0
, where the latter is defined by HL7 Denmark
. These dependencies are currently reflected in MedComCareCommunicationMessage, and MedComCareCommunicationMessageHeader which both inherits from profiles defined MedComMessaging IG. Further, it is reflected in references to MedComCorePatient, MedComCoreEncounter, MedComCoreOrganization and MedComMessagingOrganization.
|
|
web
|
medcomfhir.dk
|
Content in this IG can be downloaded in npm format under Download
. This can be used to validate locale FHIR profiles against.
|
|
web
|
medcomdk.github.io
|
On the introduction page for CareCommunication
the following documentation can be found:
|
|
web
|
github.com
|
MedComs FHIR profiles and extension are managed in GitHub under MedCom: Source code
|
|
web
|
medcomdk.github.io
|
A description of governance concerning change management and versioning
of MedComs FHIR artefacts, can be found on the link.
|
|
web
|
www.medcom.dk
|
MedCom
is responsible for this IG.
|
