DK MedCom acknowledgement
2.0.2 - Release Denmark flag

This page is part of the DK MedCom Acknowledgement (v2.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: MedComAcknowledgementMessage

Official URL: http://medcomfhir.dk/ig/acknowledgement/StructureDefinition/medcom-messaging-acknowledgement Version: 2.0.2
Active as of 2024-02-05 Computable Name: MedComAcknowledgementMessage

Base resource for all MedCom Acknowledgement messages.

Scope and usage

This profile is the root profile of MedCom Acknowledgement message. Constraint and rules from MedComMessagingMessage are inherited to this profile. The only change is that the MessageHeader shall be a MedComAcknowledgementMessageHeader.

Note: Be aware that entries in a message in general are unordered. Recipients of a message can therefore not assume any particular sequences of elements.

Below can the structure of a MedCom Acknowledgement message be seen.

MedComAcknowledgementMessage is the root profile. From this is the MedComMessagingProvenance and MedComAcknowledgementMessageHeader referenced. The MedComAcknowledgementMessageHeader includes references to the MedComMessagingOrganization. Additionally, it is possible to include an OperationOutCome profile, referenced from MedComAcknowledgementMessageHeader.

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

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 C0..*MedComMessagingMessageContains a collection of resources
medcom-acknowledgement-2: The message header shall conform to medcom-messaging-acknowledgementHeader profile
medcom-acknowledgement-1: If the response.code is different than 'ok', a reference to an OperationOutcome resource shall be included.
... entry 0..*BackboneElementMessage content (MedComAcknowledgementMessageHeader, MedComMessagingProvenance, MedComMessagingOrganization) - Open

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
medcom-acknowledgement-1errorBundleIf the response.code is different than 'ok', a reference to an OperationOutcome resource shall be included.
: iif(entry.resource.ofType(MessageHeader).response.code = 'ok', true, entry.resource.ofType(MessageHeader).response.code != 'ok' and entry.resource.ofType(OperationOutcome).exists())
medcom-acknowledgement-2errorBundleThe message header shall conform to medcom-messaging-acknowledgementHeader profile
: entry.resource.ofType(MessageHeader).conformsTo('http://medcomfhir.dk/ig/acknowledgement/StructureDefinition/medcom-messaging-acknowledgementHeader')

 

Other representations of profile: CSV, Excel, Schematron