HL7 Terminology (THO)
7.0.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 7.0.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)
Language: en
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode version 📦3.0.0| 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 version 📦3.0.0| Code | Display | Definition |
| _AcknowledgementDetailNotSupportedCode | AcknowledgementDetailNotSupportedCode | Refelects rejections because elements of the communication are not supported in the current context. |
Expansion performed internally based on:
This value set contains 27 concepts
| System | Code | Display (en) - English (English, en) | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | INTERR | Internal system error | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NOSTORE | No storage space for message. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | RTEDEST | Message routing error, destination unreachable. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | RTUDEST | Error: Message routing error, unknown destination. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | RTWDEST | Message routing warning, destination unreachable. | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN | Syntax error | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN102 | Data type error | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN105 | Required element missing | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN100 | Required association missing | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN101 | Required attribute missing | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN114 | Insufficient repetitions | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN106 | Terminology error | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN103 | Value not found in code system | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN104 | Invalid code system in CNE | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN107 | Deprecated code | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN108 | Number of repetitions exceeds limit | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN110 | Number of association repetitions exceeds limit | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN112 | Number of attribute repetitions exceeds limit | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN109 | Mandatory element with null value | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN111 | Value does not match fixed value | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | SYN113 | Formal constraint violation | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NS200 | Unsupported interaction | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NS202 | Unsupported processing id | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NS203 | Unsupported version id | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NS250 | Unsupported processing Mode | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NS260 | Unknown sender | ||
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode | NS261 | Unrecognized attentionline |
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 | Author | Custodian | Comment |
| 2023-11-14 | revise | Marc Duteau | TSMG | Add standard copyright and contact to internal content; up-476 |
| 2022-10-18 | revise | Marc Duteau | TSMG | Fixing missing metadata; up-349 |
| 2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |
| 2014-03-26 | revise | Vocabulary (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 |