DK MedCom acknowledgement
2.0.1 - Release Denmark flag

This page is part of the DK MedCom Acknowledgement (v2.0.1: Release) based on FHIR R4. The current version which supercedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions

Resource Profile: MedComAcknowledgementOperationOutcome

Official URL: http://medcomfhir.dk/ig/acknowledgement/StructureDefinition/medcom-acknowledgement-operationoutcome Version: 2.0.1
Active as of 2023-03-10 Computable Name: MedComAcknowledgementOperationOutcome

This profile provides detailed information about the outcome of an attempted system operation, such as delivering a message. It shall only be used when the attempt fails.

Scope and usage

This profile is called MedComAcknowledgementOperationOutcome and is used to give a detailed describtion of errors occuring when exchanging FHIR messages. Succes or fail in message exchange can be found in the element MessageHeader.response.code. MedComAcknowledgementOperationOutcome can be seen as a help for IT-vendors to identify potential errors in their systems, as it least shall contain a description of the issue, including a severity and an error or warning code. It may include several issues.

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

When to include an OperationOutcome

MedComAcknowledgementOperationOutcome should not be included when the message exchange goes well, corresponding to the value ‘ok’ in MessageHeader.response.code. However, may be included when the MessageHeader.response.code is ‘ok’, e.g. in cases where the received message is valid, but it is a dublet of a previous sent message. In this case an OperationOutcome with a value of OperationOutcome.issue.severity ‘information’ and a relevant code could be included. An OperationOutcome resource shall be included when the element MessageHeader.response.code is different from ‘ok’.

OperationOutCome.issue.details.coding

The CodeSystem MedComAcknowledgementIssueDetailsand ValueSetMedComAcknowledgementIssueDetailValues used in the element OperationOutCome.issue.details.coding are used to describe the issue of receiving a message more detailed. Currently, the two terminologies are fairly empty, as MedCom wants input from IT-vendors on which issue codes provide value in IT-systems. Across sectors there must be an agreed list of codes. Therefore, the ValueSet has a status as ‘draft’ and vendors should expect the CodeSystem and ValueSet to be extended. For relevant input regarding the issue codes, please contact MedCom.

Usage:

Formal Views of Profile Content

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

This structure is derived from OperationOutcome

NameFlagsCard.TypeDescription & Constraintsdoco
.. OperationOutcome 0..*OperationOutcomeInformation about the success/failure of an action
... issue S1..*BackboneElementA single issue associated with the action
.... severity S1..1codefatal | error | warning | information
.... code S1..1codeError or warning code
.... details S0..1CodeableConceptAdditional details about the error
..... coding S0..*CodingCode defined by a terminology system
Binding: MedComAcknowledgementIssueDetailValues (required)
..... text S0..1stringPlain text representation of the concept

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
OperationOutcome.issue.details.codingrequiredMedComAcknowledgementIssueDetailValues

 

Other representations of profile: CSV, Excel, Schematron