HL7 Terminology (THO)
5.5.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 5.5.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

: AcknowledgementDetailType - XML Representation

Active as of 2019-03-20

Raw xml | Download



<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-AcknowledgementDetailType"/>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p><b>Properties</b></p><p><b>This code system  defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>Specializes</td><td/><td>Coding</td><td>The child code is a more narrow version of the concept represented by the parent code.  I.e. Every child concept is also a valid parent concept.  Used to allow determination of subsumption.  Must be transitive, irreflexive, antisymmetric.</td></tr><tr><td>Generalizes</td><td/><td>Coding</td><td>Inverse of Specializes.  Only included as a derived relationship.</td></tr><tr><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>code</td><td>The internal identifier for the concept in the HL7 Access database repository.</td></tr><tr><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>code</td><td>Designation of a concept's state.  Normally is not populated unless the state is retired..</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType</code> defines the following codes in a Is-A heirarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>internalId</b></td><td><b>status</b></td></tr><tr><td style="white-space:nowrap">E<a name="v3-AcknowledgementDetailType-E"> </a></td><td>Error</td><td><div><p>**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.</p>
<p>**Example:**Unable to find specified patient.</p>
</div></td><td>19786</td><td>active</td></tr><tr><td style="white-space:nowrap">I<a name="v3-AcknowledgementDetailType-I"> </a></td><td>Information</td><td><div><p><strong>Definition:</strong> 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.</p>
<p><strong>Example:</strong> A Patient's coverage will expire in 5 days.</p>
</div></td><td>19788</td><td>active</td></tr><tr><td style="white-space:nowrap">W<a name="v3-AcknowledgementDetailType-W"> </a></td><td>Warning</td><td><div><p><strong>Definition:</strong> 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.</p>
<p><strong>Example:</strong></p>
<p>Unexpected additional repetitions of phone number have been ignored.</p>
</div></td><td>19787</td><td>active</td></tr><tr style="background-color: #ffeeee"><td style="white-space:nowrap">ERR<a name="v3-AcknowledgementDetailType-ERR"> </a></td><td/><td/><td>20071</td><td>retired</td></tr><tr style="background-color: #ffeeee"><td style="white-space:nowrap">INFO<a name="v3-AcknowledgementDetailType-INFO"> </a></td><td/><td/><td>20073</td><td>retired</td></tr><tr style="background-color: #ffeeee"><td style="white-space:nowrap">WARN<a name="v3-AcknowledgementDetailType-WARN"> </a></td><td/><td/><td>20072</td><td>retired</td></tr></table></div>
  </text>
  <url
       value="http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailType"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.5.1082"/>
  </identifier>
  <version value="3.0.0"/>
  <name value="AcknowledgementDetailType"/>
  <title value="AcknowledgementDetailType"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2019-03-20"/>
  <publisher value="Health Level Seven International"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="hq@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'"/>
  <copyright
             value="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"/>
  <caseSensitive value="true"/>
  <hierarchyMeaning value="is-a"/>
  <content value="complete"/>
  <property>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
      <valueCode value="antisymmetric"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
      <valueCode value="transitive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
      <valueCode value="irreflexive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
      <valueBoolean value="true"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
      <valueCode value="Specializes"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
      <valueString value="Generalizes"/>
    </extension>
    <code value="Specializes"/>
    <description
                 value="The child code is a more narrow version of the concept represented by the parent code.  I.e. Every child concept is also a valid parent concept.  Used to allow determination of subsumption.  Must be transitive, irreflexive, antisymmetric."/>
    <type value="Coding"/>
  </property>
  <property>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
      <valueCode value="antisymmetric"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
      <valueCode value="transitive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
      <valueCode value="irreflexive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
      <valueBoolean value="true"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
      <valueCode value="Generalizes"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
      <valueString value="Specializes"/>
    </extension>
    <code value="Generalizes"/>
    <description
                 value="Inverse of Specializes.  Only included as a derived relationship."/>
    <type value="Coding"/>
  </property>
  <property>
    <code value="internalId"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id"/>
    <description
                 value="The internal identifier for the concept in the HL7 Access database repository."/>
    <type value="code"/>
  </property>
  <property>
    <code value="status"/>
    <uri value="http://hl7.org/fhir/concept-properties#status"/>
    <description
                 value="Designation of a concept's state.  Normally is not populated unless the state is retired.."/>
    <type value="code"/>
  </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."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="19786"/>
    </property>
  </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."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="19788"/>
    </property>
  </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."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="19787"/>
    </property>
  </concept>
  <concept>
    <code value="ERR"/>
    <property>
      <code value="status"/>
      <valueCode value="retired"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="20071"/>
    </property>
  </concept>
  <concept>
    <code value="INFO"/>
    <property>
      <code value="status"/>
      <valueCode value="retired"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="20073"/>
    </property>
  </concept>
  <concept>
    <code value="WARN"/>
    <property>
      <code value="status"/>
      <valueCode value="retired"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="20072"/>
    </property>
  </concept>
</CodeSystem>