HL7 Terminology (THO)
3.1.5 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 3.1.5). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: AcknowledgementDetailType

Official URL: http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailType Version: 2.0.0
Active as of 2014-03-26 Computable Name: AcknowledgementDetailType
Other Identifiers: : 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)

Logical Definition (CLD)

 

Expansion

This value set contains 6 concepts

Expansion based on AcknowledgementDetailType v2.1.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType

CodeDisplayDefinition
  EError**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.
  IInformation**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.
  WWarning**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
  INFO
  WARN

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

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.