This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 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
1.25.4.1.1082 v3 Code System AcknowledgementDetailType
This code system (http://hl7.org/fhir/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) |
System URL: | http://hl7.org/fhir/v3/AcknowledgementDetailType |
System OID: | 2.16.840.1.113883.5.1082 |
Source Resource | XML / JSON |
This value set is not currently used
1.25.4.1.1082.1 Content Logical Definition
This value set has an inline code system http://hl7.org/fhir/v3/AcknowledgementDetailType, which defines the following codes:
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. |