FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.3.2.1082 HL7 v3 Value Set AcknowledgementDetailType

Vocabulary Work Group Maturity Level: N/AExternalUse Context: Any

This value set (http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailType) is defined as part of HL7 v3.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailType
Name: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.1.11.19358 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:


This value set includes codes from the following code systems:

 

This expansion generated 19 Apr 2017


This value set contains 6 concepts

Expansion based on http://hl7.org/fhir/v3/AcknowledgementDetailType version 2016-11-11

All codes from system http://hl7.org/fhir/v3/AcknowledgementDetailType

CodeDisplayDefinition
EErrorDefinition: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.
IInformationDefinition: 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.
WWarningDefinition: 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