STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 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

V3-AcknowledgementType.cs.xml

Raw XML (canonical form)

This attribute contains an acknowledgement code as described in the HL7 message processing rules. OpenIssue: Description was copied from attribute and needs to be improved to be appropriate for a code system.

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-AcknowledgementType"/>
  <meta>
    <lastUpdated value="2016-03-23T00:00:00.000+11:00"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p>Release Date: 2016-03-23</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>AA
            <a name="AA"> </a>
          </td>
          <td>Application Acknowledgement Accept</td>
          <td>
                        Receiving application successfully processed message.
            <br/>

                     
          </td>
        </tr>
 
        <tr>
          <td>1</td>
          <td>AE
            <a name="AE"> </a>
          </td>
          <td>Application Acknowledgement Error</td>
          <td>
                        Receiving application found error in processing message.  Sending
               error response with additional error detail information.
            <br/>

                     
          </td>
        </tr>
 
        <tr>
          <td>1</td>
          <td>AR
            <a name="AR"> </a>
          </td>
          <td>Application Acknowledgement Reject</td>
          <td>
                        Receiving application failed to process message for reason unrelated
               to content or format.  Original message sender must decide on whether to automatically
               send message again.
            <br/>

                     
          </td>
        </tr>
 
        <tr>
          <td>1</td>
          <td>CA
            <a name="CA"> </a>
          </td>
          <td>Accept Acknowledgement Commit Accept</td>
          <td>
                        Receiving message handling service accepts responsibility for
               passing message onto receiving application.
            <br/>

                     
          </td>
        </tr>
 
        <tr>
          <td>1</td>
          <td>CE
            <a name="CE"> </a>
          </td>
          <td>Accept Acknowledgement Commit Error</td>
          <td>
                        Receiving message handling service cannot accept message for any
               other reason (e.g. message sequence number, etc.).
            <br/>

                     
          </td>
        </tr>
 
        <tr>
          <td>1</td>
          <td>CR
            <a name="CR"> </a>
          </td>
          <td>Accept Acknowledgement Commit Reject</td>
          <td>
                        Receiving message handling service rejects message if interaction
               identifier, version or processing mode is incompatible with known receiving application
               role information.
            <br/>

                     
          </td>
        </tr>

      </table>

    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.5.18"/>
  </extension>
  <url value="http://hl7.org/fhir/v3/AcknowledgementType"/>
  <version value="2016-03-23"/>
  <name value="v3 Code System AcknowledgementType"/>
  <status value="active"/>
  <experimental value="false"/>
  <publisher value="HL7, Inc"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org"/>
    </telecom>
  </contact>
  <date value="2016-03-23T00:00:00+11:00"/>
  <description value=" This attribute contains an acknowledgement code as described in the HL7 message processing
     rules.  OpenIssue: Description was copied from attribute and needs to be improved to be
     appropriate for a code system."/>
  <caseSensitive value="true"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/v3-AcknowledgementType"/>
  <content value="complete"/>
  <concept>
    <code value="AA"/>
    <display value="Application Acknowledgement Accept"/>
    <definition value="Receiving application successfully processed message."/>
  </concept>
  <concept>
    <code value="AE"/>
    <display value="Application Acknowledgement Error"/>
    <definition value="Receiving application found error in processing message.  Sending error response with
       additional error detail information."/>
  </concept>
  <concept>
    <code value="AR"/>
    <display value="Application Acknowledgement Reject"/>
    <definition value="Receiving application failed to process message for reason unrelated to content or format.
        Original message sender must decide on whether to automatically send message again."/>
  </concept>
  <concept>
    <code value="CA"/>
    <display value="Accept Acknowledgement Commit Accept"/>
    <definition value="Receiving message handling service accepts responsibility for passing message onto receiving
       application."/>
  </concept>
  <concept>
    <code value="CE"/>
    <display value="Accept Acknowledgement Commit Error"/>
    <definition value="Receiving message handling service cannot accept message for any other reason (e.g. message
       sequence number, etc.)."/>
  </concept>
  <concept>
    <code value="CR"/>
    <display value="Accept Acknowledgement Commit Reject"/>
    <definition value="Receiving message handling service rejects message if interaction identifier, version
       or processing mode is incompatible with known receiving application role information."/>
  </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.