DK MedCom Carecommunication
4.0.2 - release Denmark flag

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

Resource Profile: MedComCareCommunicationMessage

Official URL: http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-message Version: 4.0.2
Active as of 2024-11-07 Computable Name: 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.

Scope and usage

This profile is the root profile of MedCom FHIR CareCommunication message. This profile is inherited from the MedComMessagingMessage. The following figure represent the profiles that should be included in a MedCom FHIR CareCommunication message.

The Bundle containing the CareCommunication message is selfcontained, why it shall contain one instance of the MedComCareCommunicationMessageHeader. By convention the cardinality is shown as 0..*.

Shows the structure of a CareCommunication message. The MedComCareCommunicationMessage includes a MedComCareCommunicationMessageHeader and a MedComMessagingProvenance. MedComCareCommunicationMessageHeader references a sender and receiver organization, the MedComMessagingOrganization and a focus which is a reference to a MedComCareCommunication. From the MedComCareCommunication is a MedComCorePatient, MedComCoreEncounter, Organization, MedComCorePractitioner and MedComCorePractitionerRole referenced.

Please refer to the tab "Snapshot Table(Must support)" below for the definition of the required content of a MedComCareCommunicationMessage.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from MedComMessagingMessage

NameFlagsCard.TypeDescription & Constraintsdoco
.. Bundle C 0..* MedComMessagingMessage Contains a collection of resources
medcom-careCommunication-1: The MessageHeader shall conform to medcom-careCommunication-messageHeader profile
medcom-careCommunication-2: Entry shall contain exactly one Patient resource
medcom-careCommunication-4: There shall exist a practitioner given and family name when using a PractitionerRole.
medcom-careCommunication-3: All Provenance resources shall be of the type medcom-careCommunication-provenance profile
medcom-careCommunication-12: If a specific recipient exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the receiver organisation in the MessageHeader resource.
medcom-careCommunication-11: If a specific sender exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the sender organisation in the MessageHeader resource.
medcom-careCommunication-13: All PractitionerRole resources shall have a reference to an instance of a Practitioner resource.
... entry 0..* BackboneElement Message content (MedComCareCommunicationMessageHeader, MedComMessagingOrganization, MedComMessagingProvenance, MedComCareCommunication, MedComCorePatient, MedComCoreEncounter, MedComCorePractitioner, MedComCorePractitionerRole, MedComCoreCareTeam) - Open

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
medcom-careCommunication-1errorBundleThe MessageHeader shall conform to medcom-careCommunication-messageHeader profile
: entry[0].resource.conformsTo('http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-messageHeader')
medcom-careCommunication-2errorBundleEntry shall contain exactly one Patient resource
: entry.where(resource.is(Patient)).count() = 1
medcom-careCommunication-3errorBundleAll Provenance resources shall be of the type medcom-careCommunication-provenance profile
: entry.resource.ofType(Provenance).where(meta.profile = 'http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-provenance').exists()
medcom-careCommunication-4errorBundleThere shall exist a practitioner given and family name when using a PractitionerRole.
: entry.resource.ofType(Practitioner).name.exists()
medcom-careCommunication-11errorBundleIf a specific sender exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the sender organisation in the MessageHeader resource.
: Bundle.entry.resource.ofType(Communication).extension.value.reference.resolve().managingOrganization.reference = %resource.entry.resource.ofType(MessageHeader).sender.reference or Bundle.entry.resource.ofType(Communication).extension.value.reference.resolve().organization.reference = %resource.entry.resource.ofType(MessageHeader).sender.reference or Bundle.entry.resource.ofType(Communication).extension.exists().not()
medcom-careCommunication-12errorBundleIf a specific recipient exists, the organisation which the CareTeam or Practitioner is a part of shall be the same as the receiver organisation in the MessageHeader resource.
: Bundle.entry.resource.ofType(Communication).recipient.reference.resolve().managingOrganization.reference = %resource.entry.resource.ofType(MessageHeader).destination.receiver.reference or Bundle.entry.resource.ofType(Communication).recipient.reference.resolve().organization.reference = %resource.entry.resource.ofType(MessageHeader).destination.receiver.reference or Bundle.entry.resource.ofType(Communication).recipient.exists().not()
medcom-careCommunication-13errorBundleAll PractitionerRole resources shall have a reference to an instance of a Practitioner resource.
: Bundle.entry.resource.ofType(PractitionerRole).practitioner.reference.exists()

 

Other representations of profile: CSV, Excel, Schematron