FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4B from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions

CodeSystem: v3 Code System AcknowledgementDetailType

Official URL: http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType Version: 2018-08-12
Standards status: External Maturity Level: 0 Computable Name: v3.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’

This Code system is referenced in the content logical definition of the following value sets:

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
status status http://hl7.org/fhir/concept-properties#status code A property that indicates the status of the concept. One of active, experimental, deprecated, retired

Concepts

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

CodeDisplayDefinitionstatus
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 retired
INFO retired
WARN retired