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
Vocabulary Work Group | Maturity Level: N/A | Ballot Status: Informative |
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'
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="v3-AcknowledgementDetailType"/> <meta> <lastUpdated value="2016-11-11T00:00:00.000+11:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Release Date: 2016-11-11</p> <table class="grid"> <tr> <td> <b> Level</b> </td> <td> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> 1</td> <td> E <a name="E"> </a> </td> <td> Error</td> <td> 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. <br/> Example:Unable to find specified patient. <br/> </td> </tr> <tr> <td> 1</td> <td> I <a name="I"> </a> </td> <td> Information</td> <td> 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. <br/> Example: A Patient's coverage will expire in 5 days. <br/> </td> </tr> <tr> <td> 1</td> <td> W <a name="W"> </a> </td> <td> Warning</td> <td> 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. <br/> Example: <br/> Unexpected additional repetitions of phone number have been ignored. <br/> </td> </tr> <tr> <td> 1</td> <td> ERR <a name="ERR"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> INFO <a name="INFO"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> WARN <a name="WARN"> </a> </td> <td/> <td/> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status"> <valueString value="External"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="0"/> </extension> <url value="http://hl7.org/fhir/v3/AcknowledgementDetailType"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.5.1082"/> </identifier> <version value="2016-11-11"/> <name value="v3 Code System AcknowledgementDetailType"/> <status value="active"/> <experimental value="false"/> <date value="2016-11-11T00:00:00+11:00"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> </contact> <description value=" 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'"/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailType"/> <hierarchyMeaning value="is-a"/> <content value="complete"/> <property> <code value="inactive"/> <uri value="http://hl7.org/fhir/concept-properties#inactive"/> <description value="True if the concept is not considered active - e.g. not a valid concept any more"/> <type value="boolean"/> </property> <concept> <code value="E"/> <display value="Error"/> <definition value="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."/> </concept> <concept> <code value="I"/> <display value="Information"/> <definition value="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."/> </concept> <concept> <code value="W"/> <display value="Warning"/> <definition value="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."/> </concept> <concept> <code value="ERR"/> <property> <code value="inactive"/> <valueBoolean value="true"/> </property> </concept> <concept> <code value="INFO"/> <property> <code value="inactive"/> <valueBoolean value="true"/> </property> </concept> <concept> <code value="WARN"/> <property> <code value="inactive"/> <valueBoolean value="true"/> </property> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.