HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
| Official URL: http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailCode | Version: 3.0.0 | |||
| Active as of 2014-03-26 | Responsible: Health Level Seven International | Computable Name: AcknowledgementDetailCode | ||
| Other Identifiers: OID:2.16.840.1.113883.1.11.19638 | ||||
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
||||
A site specific problem code
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet v3-AcknowledgementDetailCode
Language: en
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode| Code | Display | Definition |
| INTERR | Internal system error | An internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message. |
| NOSTORE | No 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. |
| RTEDEST | Message 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. |
| RTUDEST | Error: 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. |
| RTWDEST | Message 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. |
This value set excludes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode| Code | Display | Definition |
| _AcknowledgementDetailNotSupportedCode | AcknowledgementDetailNotSupportedCode | Refelects rejections because elements of the communication are not supported in the current context. |
Generated Narrative: ValueSet
Language: en
Expansion based on:
This value set contains 27 concepts
| Code | System | Display | Definition |
| INTERR | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Internal system error | An internal software component (database, application, queue mechanism, etc.) has failed, leading to inability to process the message. |
| NOSTORE | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | No 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. |
| RTEDEST | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Message 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. |
| RTUDEST | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Error: 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. |
| RTWDEST | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Message 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. |
| SYN | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Syntax error | Reflects errors in the syntax or structure of the communication. |
| SYN102 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Data type error | The attribute contained data of the wrong data type, e.g. a numeric attribute contained "FOO". |
| SYN105 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Required 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. |
| SYN100 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Required association missing | Required 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. |
| SYN101 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Required attribute missing | A required attribute is missing in a class. |
| SYN114 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Insufficient 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. |
| SYN106 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Terminology 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. |
| SYN103 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Value not found in code system | An attribute value was compared against the corresponding code system, and no match was found. |
| SYN104 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Invalid code system in CNE | An attribute value referenced a code system that is not valid for an attribute constrained to CNE. |
| SYN107 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Deprecated code | Description: A coded attribute is referencing a code that has been deprecated by the owning code system. |
| SYN108 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Number 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. |
| SYN110 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Number of association repetitions exceeds limit | The 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. |
| SYN112 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Number of attribute repetitions exceeds limit | The number of repetitions of an attribute exceeds the limits of the standard or of one of the conformance profiles identified in the message. |
| SYN109 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Mandatory 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. |
| SYN111 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Value 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. |
| SYN113 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Formal 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. |
| NS200 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Unsupported interaction | The interaction (or: this version of the interaction) is not supported. |
| NS202 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Unsupported processing id | The Processing ID is not supported. |
| NS203 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Unsupported version id | The Version ID is not supported. |
| NS250 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Unsupported processing Mode | The processing mode is not supported. |
| NS260 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Unknown sender | The Device.id of the sender is unknown. |
| NS261 | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | Unrecognized attentionline | The 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 |
| System | 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
| Date | Action | Custodian | Author | Comment |
| 2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
| 2022-10-18 | revise | TSMG | Marc Duteau | Fixing missing metadata; up-349 |
| 2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |
| 2014-03-26 | revise | 2014T1_2014-03-26_001283 (RIM release ID) | Vocabulary (Woody Beeler) (no record of original request) | Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26 |
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#6.1.0 based on FHIR 5.0.0. Generated 2024-11-19
Links: Table of Contents |
QA Report
| Version History 
|
|
Propose a change