Release 4

V3-AcknowledgementCondition.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

The codes identify the conditions under which accept acknowledgements are required to be returned in response to this message. Note that accept acknowledgement address two different issues at the same time: reliable transport as well as syntactical correctness

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

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-AcknowledgementCondition"/> 
  <meta> 
    <lastUpdated value="2018-08-12T00:00:00.000+00:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </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> AL
            <a name="v3-AcknowledgementCondition-AL"> </a> 
          </td> 
          <td> Always</td> 
          <td> 
                        Always send an acknowledgement.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> ER
            <a name="v3-AcknowledgementCondition-ER"> </a> 
          </td> 
          <td> Error/reject only</td> 
          <td> 
                        Send an acknowledgement for error/reject conditions only.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> NE
            <a name="v3-AcknowledgementCondition-NE"> </a> 
          </td> 
          <td> Never</td> 
          <td> 
                        Never send an acknowledgement.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> SU
            <a name="v3-AcknowledgementCondition-SU"> </a> 
          </td> 
          <td> Successful only</td> 
          <td> 
                        Send an acknowledgement for successful completions only.
            <br/>  

                     
          </td> 
        </tr> 

      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="external"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="vocab"/> 
  </extension> 
  <url value="http://terminology.hl7.org/ValueSet/v3-AcknowledgementCondition"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.1.11.155"/> 
  </identifier> 
  <version value="2018-08-12"/> 
  <name value="v3.AcknowledgementCondition"/> 
  <title value="v3 Code System AcknowledgementCondition"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2018-08-12"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value=" The codes identify the conditions under which accept acknowledgements are required to
     be returned in response to this message. Note that accept acknowledgement address two
     different issues at the same time: reliable transport as well as syntactical correctness"/> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://terminology.hl7.org/CodeSystem/v3-AcknowledgementCondition"/> 
    </include> 
  </compose> 
</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.