DK MedCom Messaging
2.0.0 - Build CI Denmark flag

This page is part of the DK MedCom Messaging (v2.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

Resource Profile: MedComMessagingMessage

Official URL: http://medcomfhir.dk/ig/messaging/StructureDefinition/medcom-messaging-message Version: 2.0.0
Active as of 2024-02-15 Computable Name: MedComMessagingMessage

Base resource for all MedCom messages.

Scope and usage

This profile describes the Bundle resource that shall be used in all MedCom FHIR Messages. MedComMessagingMessage is the root in all messages, as shown on the figure below. As this profile is the used in a message, shall the element type in MedComMessagingMessage always be message. This entails that the first resource in the entry element shall be a MedComMessagingMessageHeader.

For each messaging standard e.g., HospitalNotification or CareCommunication is a different set of profiles defined, but common to them both is that all included profiles shall be referenced from the entry element. Due to the different requirements for each standard, it should be expected that the MedComMessagingMessage is inherited in each standard.

Shows the general MedCom messaging model. Each message must contain the following resources: Bundle, MessageHeader, Organization and Provenance.

Please refer to the tab “Snapshot Table(Must support)” below for the definition of the required content of a MedComMessagingMessage.

Usage:

Formal Views of Profile Content

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

This structure is derived from Bundle

NameFlagsCard.TypeDescription & Constraintsdoco
.. Bundle C0..*BundleContains a collection of resources
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-messaging-3: All Provenance resources shall conform to medcom-core-provenance profile
... id S1..1idLogical id of this artifact
... type S1..1codeAlways message
Required Pattern: message
... timestamp S1..1instantWhen the bundle was assembled
.... resource S0..1ResourceEach MedCom message shall contain a MedComMessagingMessageHeader and MedComMessagingProvenance. Please refer to invariant medcom-messaging-1, medcom-messaging-2, and medcom-messaging-3.

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
medcom-messaging-1errorBundleThe MessageHeader resource shall conform to medcom-messaging-messageHeader profile
: entry.ofType(MessageHeader).all(resource.conformsTo('http://medcomfhir.dk/fhir/messaging/StructureDefinition/medcom-messaging-messageHeader'))
medcom-messaging-2errorBundleThere shall be at least one Provenance resource in a MedCom message
: entry.resource.ofType(Provenance).exists()
medcom-messaging-3errorBundleAll Provenance resources shall conform to medcom-core-provenance profile
: entry.ofType(Provenance).all(resource.conformsTo('http://medcomfhir.dk/fhir/messaging/StructureDefinition/medcom-messaging-provenance'))

 

Other representations of profile: CSV, Excel, Schematron