HL7 Terminology (THO)
5.3.0 - Publication
This page is part of the HL7 Terminology (v5.3.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailType | Version: 2.0.0 | |||
Active as of 2014-03-26 | Computable Name: AcknowledgementDetailType | |||
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.19358 |
A code identifying the specific message to be provided.
A textual value may be specified as the print name, or for non-coded messages, as the original text.Discussion:
‘Required attribute xxx is missing’, ‘System will be unavailable March 19 from 0100 to 0300’Examples:
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType
This value set contains 6 concepts
Expansion based on codesystem AcknowledgementDetailType v2.1.0 (CodeSystem)
Code | System | Display | Inactive | Definition |
E | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType | Error | **Definition:**An issue which has prevented, or will prevent (unless a management is provided for the issue by the sender), the successful processing of an interaction. Response interactions which include an issue which is an Error are a 'rejection', indicating that the request was not successfully processed. **Example:**Unable to find specified patient. | |
I | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType | Information | Definition: The message relates to an issue which has no bearing on the successful processing of the request. Information issues cannot be overridden by specifying a management. Example: A Patient's coverage will expire in 5 days. | |
W | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType | Warning | Definition: The message relates to an issue which cannot prevent the successful processing of a request, but which could result in the processing not having the ideal or intended effect. Managing a warning issue is not required for successful processing, but will suppress the warning from being raised. Example: Unexpected additional repetitions of phone number have been ignored. | |
ERR | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType | inactive | ||
INFO | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType | inactive | ||
WARN | http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType | inactive |
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 |
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 |