v3 Vocabulary

AcknowledgementDetailCode

AcknowledgementDetailCode2.16.840.1.113883.5.1100

Details

NameAcknowledgementDetailCode
Title
OID2.16.840.1.113883.5.1100
Concepts29
In the unified registry

Concepts29

CodeDisplayStatus
_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeRefelects rejections because elements of the communication are not supported in the current context.active
_AcknowledgementDetailSyntaxErrorCodeAcknowledgementDetailSyntaxErrorCodeReflects errors in the syntax or structure of the communication.retired
INTERRInternal system errorAn internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message.active
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.active
NS200Unsupported interaction_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeThe interaction (or: this version of the interaction) is not supported.active
NS202Unsupported processing id_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeThe Processing ID is not supported.active
NS203Unsupported version id_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeThe Version ID is not supported.active
NS250Unsupported processing Mode_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeThe processing mode is not supported.active
NS260Unknown sender_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeThe Device.id of the sender is unknown.active
NS261Unrecognized attentionline_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeThe receiver requires information in the attentionLine classes for routing purposes.active
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.active
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.active
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.active
SYNSyntax errorReflects errors in the syntax or structure of the communication.active
SYN100Required association missingSYN105Required element 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.active
SYN101Required attribute missingSYN105Required element missingA required attribute is missing in a class.active
SYN102Data type errorSYNSyntax errorThe attribute contained data of the wrong data type, e.g. a numeric attribute contained "FOO".active
SYN103Value not found in code systemSYN106Terminology errorAn attribute value was compared against the corresponding code system, and no match was found.active
SYN104Invalid code system in CNESYN106Terminology errorAn attribute value referenced a code system that is not valid for an attribute constrained to CNE.active
SYN105Required element missingSYNSyntax errorDescription: 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.active
SYN106Terminology errorSYNSyntax errorDescription: 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.active
SYN107Deprecated codeSYN106Terminology errorDescription: A coded attribute is referencing a code that has been deprecated by the owning code system.active
SYN108Number of repetitions exceeds limitSYNSyntax errorDescription: 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.active
SYN109Mandatory element with null valueSYNSyntax errorDescription: An attribute or association identified as mandatory in a specification or declared conformance profile or template has been specified with a null flavor.active
SYN110Number of association repetitions exceeds limitSYN108Number of 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.active
SYN111Value does not match fixed valueSYNSyntax errorDescription: 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.active
SYN112Number of attribute repetitions exceeds limitSYN108Number of 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.active
SYN113Formal constraint violationSYNSyntax errorDescription: A formal constraint asserted in the standard or one of the conformance profiles or templates declared in the message has been violated.active
SYN114Insufficient repetitionsSYN105Required element missingDescription: 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.active