Current Build

4.4.2.1082 HL7 v3 Code System AcknowledgementDetailType

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This code system (http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType
Version:2018-08-12
Name:v3.AcknowledgementDetailType
Title:v3 Code System AcknowledgementDetailType
Definition:

A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'

OID:2.16.840.1.113883.5.1082 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: v3 Code System AcknowledgementDetailType ( A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300')

Release Date: 2018-08-12

LevelCodeDisplayDefinition
1E 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.
1I 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.
1W 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.
1ERR
1INFO
1WARN