HL7.TERMINOLOGY\AcknowledgementDetailType

HL7 Terminology (THO)
3.0.0 - Publication

This page is part of the HL7 Terminology (v3.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: AcknowledgementDetailType

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailType

Version:

2.0.0

Name:

AcknowledgementDetailType

Status:

Active as of 3/26/14

Definition:

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:

OID:

2.16.840.1.113883.1.11.19358 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

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)

Include all codes defined in http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType

Expansion

This value set contains 6 concepts

Expansion based on AcknowledgementDetailType v2.0.0 (CodeSystem)

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

Code	Display	Definition
E	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	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	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
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

Source

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

2020-05-06

revise