DK MedCom Carecommunication
4.0.3 - release
DK MedCom Carecommunication
4.0.3 - release
This page is part of the DK MedCom CareCommunication (v4.0.3: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-message | Version: 4.0.3 | |||
| Active as of 2025-05-23 | 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.
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..*.
Please refer to the tab "Snapshot Table(Must support)" below for the definition of the required content of a MedComCareCommunicationMessage.
Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
  Bundle |
C | 0..* | MedComMessagingMessage | Contains a collection of resources bdl-1: total only when a search or history bdl-2: entry.search only when a search bdl-3: entry.request mandatory for batch/transaction/history, otherwise prohibited bdl-4: entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited bdl-7: FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) bdl-9: A document must have an identifier with a system and a value bdl-10: A document must have a date bdl-11: A document must have a Composition as the first resource bdl-12: A message must have a MessageHeader as the first resource medcom-messaging-1: The MessageHeader resource shall conform to medcom-messaging-messageHeader profile medcom-messaging-2: There shall be at least one Provenance resource in a MedCom message 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. |
  id |
SΣ | 1..1 | id | Logical id of this artifact |
| implicitRules |
?!Σ | 0..1 | uri | A set of rules under which this content was created |
| type |
SΣ | 1..1 | code | Always message Binding: BundleType (required): Indicates the purpose of a bundle - how it is intended to be used. Required Pattern: message |
| timestamp |
SΣ | 1..1 | instant | When the bundle was assembled |
  entry |
SΣC | 0..* | BackboneElement | Message content (MedComCareCommunicationMessageHeader, MedComMessagingOrganization, MedComMessagingProvenance, MedComCareCommunication, MedComCorePatient, MedComCoreEncounter, MedComCorePractitioner, MedComCorePractitionerRole, MedComCoreCareTeam) - Open bdl-5: must be a resource unless there's a request or response bdl-8: fullUrl cannot be a version specific reference This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type |
  modifierExtension |
?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
 resource |
SΣ | 0..1 | Resource | Each MedCom message shall contain a MedComMessagingMessageHeader and MedComMessagingProvenance. Please refer to invariant medcom-messaging-1, medcom-messaging-2, and medcom-messaging-3. |
| Documentation for this format | ||||
| Path | Conformance | ValueSet / Code | URI |
| Bundle.type | required | Pattern: messagehttp://hl7.org/fhir/ValueSet/bundle-type|4.0.1from the FHIR Standard |
| Id | Grade | Path(s) | Details | Requirements |
| bdl-1 | error | Bundle | total only when a search or history : total.empty() or (type = 'searchset') or (type = 'history') | |
| bdl-2 | error | Bundle | entry.search only when a search : entry.search.empty() or (type = 'searchset') | |
| bdl-3 | error | Bundle | entry.request mandatory for batch/transaction/history, otherwise prohibited : entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history')) | |
| bdl-4 | error | Bundle | entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited : entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history')) | |
| bdl-5 | error | Bundle.entry | must be a resource unless there's a request or response : resource.exists() or request.exists() or response.exists() | |
| bdl-7 | error | Bundle | FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) : (type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct() | |
| bdl-8 | error | Bundle.entry | fullUrl cannot be a version specific reference : fullUrl.contains('/_history/').not() | |
| bdl-9 | error | Bundle | A document must have an identifier with a system and a value : type = 'document' implies (identifier.system.exists() and identifier.value.exists()) | |
| bdl-10 | error | Bundle | A document must have a date : type = 'document' implies (timestamp.hasValue()) | |
| bdl-11 | error | Bundle | A document must have a Composition as the first resource : type = 'document' implies entry.first().resource.is(Composition) | |
| bdl-12 | error | Bundle | A message must have a MessageHeader as the first resource : type = 'message' implies entry.first().resource.is(MessageHeader) | |
| ele-1 | error | **ALL** elements | All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count()) | |
| ext-1 | error | **ALL** extensions | Must have either extensions or value[x], not both : extension.exists() != value.exists() | |
| medcom-careCommunication-1 | error | Bundle | The MessageHeader shall conform to medcom-careCommunication-messageHeader profile : entry[0].resource.conformsTo('http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-messageHeader') | |
| medcom-careCommunication-2 | error | Bundle | Entry shall contain exactly one Patient resource : entry.where(resource.is(Patient)).count() = 1 | |
| medcom-careCommunication-3 | error | Bundle | All 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-4 | error | Bundle | There shall exist a practitioner given and family name when using a PractitionerRole. : entry.resource.ofType(Practitioner).name.exists() | |
| medcom-careCommunication-11 | error | Bundle | 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. : 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-12 | error | Bundle | 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. : 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-13 | error | Bundle | All PractitionerRole resources shall have a reference to an instance of a Practitioner resource. : Bundle.entry.resource.ofType(PractitionerRole).practitioner.reference.exists() | |
| medcom-messaging-1 | error | Bundle | The MessageHeader resource shall conform to medcom-messaging-messageHeader profile : entry[0].resource.conformsTo('http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-messageHeader') | |
| medcom-messaging-2 | error | Bundle | There shall be at least one Provenance resource in a MedCom message : entry.resource.ofType(Provenance).exists() |
Other representations of profile: CSV, Excel, Schematron
