DK MedCom Carecommunication
4.0.1 - release Denmark flag

This page is part of the DK MedCom CareCommunication (v4.0.1: 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

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

MedComCareCommunication

Care related communication between two or more parties in Danish healthcare

MedComCareCommunicationMessage

The CareCommunication is used to ensure secure electronic communication of personally identifiable information and is most often used for ad hoc communication between parties in Danish Healthcare. However, the CareCommunication shall only be used in areas where no other MedCom standard is available, and it must not be used for cases with an acute nature.

MedComCareCommunicationMessageDefinition

The MessageDefinition for a CareCommunication messsage.

MedComCareCommunicationMessageHeader

Message header for care communication message

MedComCareCommunicationProvenance

Provenance information about the current and preceeding message.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

1st message - Bruno Test Elmer

1st message - Patient described with minimal information. Valid only if used in a Bundle.

1st message - Example of a reciever organization with a SOR and an EAN identifier.

1st message - Example of an organization with a SOR and an EAN identifier.

1st message - Example of a sender organization with a SOR and an EAN identifier.

1st message - Example of an organization with a SOR and an EAN identifier.

1st message - Instance of Communication resource used in a new message.

1st message - Content of care communication message. Valid only if used in a bundle (message) - new message

1st message - Instance of a MessageHeader resource used in a new message.

1st message - Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message).

1st message - New CareCommunication message.

1st message - Example of a CareCommunication new message.

1st message - The Provenance instance is only valid if used in a bundle (message) - new message

1st message - The Provenance instance is only valid if used in a bundle (message) - new message

2nd message - Instance of Communication resource used in a reply message.

2nd message - Content of care communication message. Valid only if used in a bundle (message) - reply message

2nd message - Instance of a MessageHeader resource used in a reply message.

2nd message - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message).

2nd message - Reply CareCommunication message

2nd message - Example of a reply to a CareCommunication message.

2nd message - The Provenance instance is only valid if used in a bundle (message) - reply to new message

2nd message - The Provenance instance is only valid if used in a bundle (message) - reply to new message

3rd message - Bruno Test Elmer

3rd message - Patient described with minimal information. Valid only if used in a Bundle.

3rd message - Example of a reciever organization with a SOR and an EAN identifier.

3rd message - Example of an organization with a SOR and an EAN identifier.

3rd message - Example of a sender organization with a SOR and an EAN identifier.

3rd message - Example of an organization with a SOR and an EAN identifier.

3rd message - Instance of Communication resource used in a reply message.

3rd message - Content of care communication message. Valid only if used in a bundle (message) - reply message

3rd message - Instance of a MessageHeader resource used in a reply message.

3rd message - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message).

3rd message - Reply CareCommunication message

3rd message - Example of a reply to a CareCommunication message.

3rd message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded

3rd message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded

4th message - Forward CareCommunication message

4th message - Example of a forward CareCommunication message.

4th message - Instance of Communication resource used in a forward message.

4th message - Content of care communication message. Valid only if used in a bundle (message) - forward message

4th message - Instance of a MessageHeader resource used in a forward message.

4th message - Example of a MessageHeader in a forward CareCommunication message. Valid only if used in a bundle (message).

4th message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded

4th message - The Provenance instance is only valid if used in a bundle (message) - new message being forwarded

5th message - Instance of Communication resource used in a reply message.

5th message - Content of CareCommunication message. Valid only if used in a bundle (message) - reply message

5th message - Instance of a MessageHeader resource used in a reply message.

5th message - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message).

5th message - Reply CareCommunication message

5th message - Example of a reply CareCommunication message.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

Bruno Test Elmer

Patient described with minimal information. Valid only if used in a Bundle.

CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message

CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - new message

CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to OIOXML-message

CareCommunication example. The Provenance instance is only valid if used in a bundle (message) - reply to OIOXML-message

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a reciever organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a recipient in terms of a careteam.

Example of a recipient in terms of a careteam.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Example of a sender organization with a SOR and an EAN identifier.

Example of an organization with a SOR and an EAN identifier.

Instance of Communication resource used in a new message.

Content of care communication message. Valid only if used in a bundle (message) - new message

Instance of Communication resource used in a new message. The message includes a journal note and author information in the messagetext.

Content of care communication message. Valid only if used in a bundle (message) - new message with attachment

Instance of Communication resource used in a reply message. A reply to an OIOXML message

Content of care communication message. Valid only if used in a bundle (message).

Instance of a MessageHeader resource used in a new message with journal note in message text.

Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message).

Instance of a MessageHeader resource used in a new message.

Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message).

Instance of a MessageHeader resource used in a reply to an OIOXML message.

MessageHeader for CareCommunication reply to an OIOXML message. Valid only if used in a bundle (message).

MedCom Core Encounter

Example of a simple MedCom Core Encounter

MedCom Core Encounter

Example of a simple MedCom Core Encounter

New CareCommunication message.

Example of a CareCommunication new message.

New CareCommunication message. Including journal note in the message text.

Example of a CareCommunication new message with journal note in the message text.

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

Reply CareCommunication message. Reply to OIOXML Message

Example of a reply to an OIOXML message.

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name