FHIR 5.0.0 © HL7.org  |  FHIRsmith 0.8.5  |  Server Home  |  TX Home  |  Capability Statement  |  Terminology Capabilities  |  Operations  |  Problems  |   

TX: CodeSystem v3-AcknowledgementDetailType

Properties

Language en
Defining URL http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType
Version 4.0.0
Name AcknowledgementDetailType
Title AcknowledgementDetailType
Status active
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'

Publisher Health Level Seven International
Copyright This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

Properties

This code system defines the following properties for its concepts

Code URI Type Description
status http://hl7.org/fhir/concept-properties#status code Designation of a concept's state. Normally is not populated unless the state is retired..

Concepts

This case-sensitive code system http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType defines the following codes in a is-a hierarchy:

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