STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.3.2.1100 HL7 v3 Value Set AcknowledgementDetailCode

This value set (http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailCode) is defined as part of HL7 v3.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailCode
Name:v3 Code System AcknowledgementDetailCode
Definition: OpenIssue: Missing description.
OID: (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


This value set includes codes from the following code systems:

 

This expansion generated 06 Dec 2016


This value set contains 27 concepts

Expansion based on http://hl7.org/fhir/v3/AcknowledgementDetailCode version 2016-11-11

All codes from system http://hl7.org/fhir/v3/AcknowledgementDetailCode

CodeDisplayDefinition
_AcknowledgementDetailNotSupportedCodeAcknowledgementDetailNotSupportedCodeRefelects rejections because elements of the communication are not supported in the current context.
  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.
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 missingDescription: 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 repetitionsDescription: 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 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.
    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 codeDescription: A coded attribute is referencing a code that has been deprecated by the owning code system.
  SYN108Number of repetitions exceeds limitDescription: 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 valueDescription: 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 valueDescription: 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 violationDescription: A formal constraint asserted in the standard or one of the conformance profiles or templates declared in the message has been violated.