DSTU2 QA Preview

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 . Page versions: R4 R3 R2

V3-AcknowledgementDetailType.xml

Raw XML (canonical form)

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'

Raw XML

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-AcknowledgementDetailType"/>
  <meta>
    <lastUpdated value="2015-07-31T00:00:00.000+10:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>Release Date: 2015-07-31</p>

      <p>OID for code system: 2.16.840.1.113883.5.1082</p>

      <p>OID for value set: 2.16.840.1.113883.1.11.19358 (this is the value set that includes the
           entire code system)</p>

      <h2>Description</h2>

      <p>
                  A code identifying the specific message to be provided.
        <br/>

                  
                     Discussion: A textual value may be specified as the print name, or
           for non-coded messages, as the original text.
        <br/>

                  
                     Examples: 'Required attribute xxx is missing', 'System will be unavailable
           March 19 from 0100 to 0300'
        <br/>

               
      </p>

      <hr/>

      <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>

      </table>

    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.1.11.19358"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/v3-AcknowledgementDetailType"/>
  <version value="2015-07-31"/>
  <name value="v3 Code System AcknowledgementDetailType"/>
  <status value="active"/>
  <experimental value="false"/>
  <publisher value="HL7, Inc"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org"/>
    </telecom>
  </contact>
  <date value="2015-07-31"/>
  <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'"/>
  <codeSystem>
    <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
      <valueUri value="urn:oid:2.16.840.1.113883.5.1082"/>
    </extension>
    <system value="http://hl7.org/fhir/v3/AcknowledgementDetailType"/>
    <caseSensitive value="true"/>
    <concept>
      <code value="E"/>
      <abstract value="false"/>
      <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"/>
      <abstract value="false"/>
      <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"/>
      <abstract value="false"/>
      <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>
  </codeSystem>
</ValueSet>

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.