R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). 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

V3-AcknowledgementDetailType.cs.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form + also see XML Format Specification)

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'

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-AcknowledgementDetailType"/> 
  <meta> 
    <lastUpdated value="2018-08-12T00:00:00.000+10:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Release Date: 2018-08-12</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="v3-AcknowledgementDetailType-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="v3-AcknowledgementDetailType-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="v3-AcknowledgementDetailType-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="v3-AcknowledgementDetailType-ERR"> </a> 
          </td> 
          <td/>  
          <td/>  
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> INFO
            <a name="v3-AcknowledgementDetailType-INFO"> </a> 
          </td> 
          <td/>  
          <td/>  
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> WARN
            <a name="v3-AcknowledgementDetailType-WARN"> </a> 
          </td> 
          <td/>  
          <td/>  
        </tr> 

      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueString value="External"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <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="2018-08-12"/> 
  <name value="v3.AcknowledgementDetailType"/> 
  <title value="v3 Code System AcknowledgementDetailType"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2018-08-12T00:00:00+10: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://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailType"/> 
  <hierarchyMeaning value="is-a"/> 
  <content value="complete"/> 
  <property> 
    <code value="status"/> 
    <uri value="http://hl7.org/fhir/concept-properties#status"/> 
    <description value="A property that indicates the status of the concept. One of active, experimental, deprecated,
       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."/> 
  </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="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="INFO"/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </property> 
  </concept> 
  <concept> 
    <code value="WARN"/> 
    <property> 
      <code value="status"/> 
      <valueCode value="retired"/> 
    </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.