HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

AcknowledgementDetailCode

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailCode
Version:2.0.0
Name:AcknowledgementDetailCode
Status:Active
Title:AcknowledgementDetailCode
Definition:

A site specific problem code

OID:2.16.840.1.113883.1.11.19638 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode
    CodeDisplay
    INTERRInternal system errorAn internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message.
    NOSTORENo storage space for message.**Rejection:** The message can't be stored by the receiver due to an unspecified internal application issue. The message was neither processed nor stored by the receiving application.
    RTEDESTMessage routing error, destination unreachable.**Error:** The destination of this message is known to the receiving application. Messages have been successfully routed to that destination in the past. The link to the destination application or an intermediate application is unavailable.
    RTUDESTError: Message routing error, unknown destination.The destination of this message is unknown to the receiving application. The receiving application in the message does not match the application which received the message. The message was neither routed, processed nor stored by the receiving application.
    RTWDESTMessage routing warning, destination unreachable.**Warning:** The destination of this message is known to the receiving application. Messages have been successfully routed to that destination in the past. The link to the destination application or an intermediate application is (temporarily) unavailable. The receiving application will forward the message as soon as the destination can be reached again.
  • Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailSyntaxErrorCode
  • Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailNotSupportedCode
  • Exclude these codes as defined in http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode
    CodeDisplay
    _AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeRefelects rejections because elements of the communication are not supported in the current context.

 

Expansion

This value set contains 27 concepts

All codes from system http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode

CodeDisplayDefinition
INTERRInternal system errorAn internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message.
NOSTORENo storage space for message.**Rejection:** The message can't be stored by the receiver due to an unspecified internal application issue. The message was neither processed nor stored by the receiving application.
RTEDESTMessage routing error, destination unreachable.**Error:** The destination of this message is known to the receiving application. Messages have been successfully routed to that destination in the past. The link to the destination application or an intermediate application is unavailable.
RTUDESTError: Message routing error, unknown destination.The destination of this message is unknown to the receiving application. The receiving application in the message does not match the application which received the message. The message was neither routed, processed nor stored by the receiving application.
RTWDESTMessage routing warning, destination unreachable.**Warning:** The destination of this message is known to the receiving application. Messages have been successfully routed to that destination in the past. The link to the destination application or an intermediate application is (temporarily) unavailable. The receiving application will forward the message as soon as the destination can be reached again.
SYNSyntax errorReflects errors in the syntax or structure of the communication.
SYN102Data type errorThe attribute contained data of the wrong data type, e.g. a numeric attribute contained "FOO".
SYN105Required element missing**Description:** Required association or attribute missing in message; or the sequence of the classes is different than required by the standard or one of the conformance profiles identified in the message.
SYN100Required association missingRequired association missing in message; or the sequence of the classes is different than required by the standard or one of the conformance profiles identified in the message.
SYN101Required attribute missingA required attribute is missing in a class.
SYN114Insufficient repetitions**Description:** The number of repetitions of a group of association or attributes is less than the required minimum for the standard or of one of the conformance profiles or templates identified in the message.
SYN106Terminology error**Description:** A coded attribute or datatype property violates one of the terminology constraints specified in the standard or one of the conformance profiles or templates declared by the instance.
SYN103Value not found in code systemAn attribute value was compared against the corresponding code system, and no match was found.
SYN104Invalid code system in CNEAn attribute value referenced a code system that is not valid for an attribute constrained to CNE.
SYN107Deprecated code**Description:** A coded attribute is referencing a code that has been deprecated by the owning code system.
SYN108Number of repetitions exceeds limit**Description:** The number of repetitions of a (group of) association(s) or attribute(s) exceeds the limits of the standard or of one of the conformance profiles or templates identified in the message.
SYN110Number of association repetitions exceeds limitThe number of repetitions of a (group of) association(s) exceeds the limits of the standard or of one of the conformance profiles identified in the message.
SYN112Number of attribute repetitions exceeds limitThe number of repetitions of an attribute exceeds the limits of the standard or of one of the conformance profiles identified in the message.
SYN109Mandatory element with null value**Description:** An attribute or association identified as mandatory in a specification or declared conformance profile or template has been specified with a null flavor.
SYN111Value does not match fixed value**Description:** The value of an attribute or property differs from the fixed value asserted in the standard or one of the conformance profiles or templates declared in the message.
SYN113Formal constraint violation**Description:** A formal constraint asserted in the standard or one of the conformance profiles or templates declared in the message has been violated.
NS200Unsupported interactionThe interaction (or: this version of the interaction) is not supported.
NS202Unsupported processing idThe Processing ID is not supported.
NS203Unsupported version idThe Version ID is not supported.
NS250Unsupported processing ModeThe processing mode is not supported.
NS260Unknown senderThe Device.id of the sender is unknown.
NS261Unrecognized attentionlineThe receiver requires information in the attentionLine classes for routing purposes.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26