Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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-AcknowledgementDetailCode.cs.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

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

OpenIssue: Missing description.

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

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-AcknowledgementDetailCode"/> 
  <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> 
            <span style="color: grey">
              <i> (_AcknowledgementDetailNotSupportedCode)</i> 
            </span>  
            <b> 
              <i> Abstract</i> 
            </b> 
          </td> 
          <td> 
            <a name="v3-AcknowledgementDetailCode-_AcknowledgementDetailNotSupportedCode"> </a> 
          </td> 
          <td> 
                        Refelects rejections because elements of the communication are
               not supported in the current context.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   NS200
            <a name="v3-AcknowledgementDetailCode-NS200"> </a> 
          </td> 
          <td> Unsupported interaction</td> 
          <td> 
                        The interaction (or: this version of the interaction) is not supported.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   NS202
            <a name="v3-AcknowledgementDetailCode-NS202"> </a> 
          </td> 
          <td> Unsupported processing id</td> 
          <td> 
                        The Processing ID is not supported.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   NS203
            <a name="v3-AcknowledgementDetailCode-NS203"> </a> 
          </td> 
          <td> Unsupported version id</td> 
          <td> 
                        The Version ID is not supported.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   NS250
            <a name="v3-AcknowledgementDetailCode-NS250"> </a> 
          </td> 
          <td> Unsupported processing Mode</td> 
          <td> 
                        The processing mode is not supported.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   NS260
            <a name="v3-AcknowledgementDetailCode-NS260"> </a> 
          </td> 
          <td> Unknown sender</td> 
          <td> 
                        The Device.id of the sender is unknown.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   NS261
            <a name="v3-AcknowledgementDetailCode-NS261"> </a> 
          </td> 
          <td> Unrecognized attentionline</td> 
          <td> 
                        The receiver requires information in the attentionLine classes
               for routing purposes.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> INTERR
            <a name="v3-AcknowledgementDetailCode-INTERR"> </a> 
          </td> 
          <td> Internal system error</td> 
          <td> 
                        An internal software component (database, application, queue mechanism,
               etc.) has failed, leading to inability to process the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> NOSTORE
            <a name="v3-AcknowledgementDetailCode-NOSTORE"> </a> 
          </td> 
          <td> No storage space for message.</td> 
          <td> 
                        
                           Rejection: The message can't be stored by the receiver due
               to an unspecified internal application issue. The message was neither processed nor stored
               by the receiving application.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> RTEDEST
            <a name="v3-AcknowledgementDetailCode-RTEDEST"> </a> 
          </td> 
          <td> Message routing error, destination unreachable.</td> 
          <td> 
                        
                           Error: The destination of this message is known to the receiving
               application. Messages have been successfully routed to that destination in the past. The
               link to the destination application or an intermediate application is unavailable.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> RTUDEST
            <a name="v3-AcknowledgementDetailCode-RTUDEST"> </a> 
          </td> 
          <td> Error: Message routing error, unknown destination.</td> 
          <td> 
                        The destination of this message is unknown to the receiving application.
               The receiving application in the message does not match the application which received
               the message. The message was neither routed, processed nor stored by the receiving application.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> RTWDEST
            <a name="v3-AcknowledgementDetailCode-RTWDEST"> </a> 
          </td> 
          <td> Message routing warning, destination unreachable.</td> 
          <td> 
                        
                           Warning: The destination of this message is known to the receiving
               application. Messages have been successfully routed to that destination in the past. The
               link to the destination application or an intermediate application is (temporarily) unavailable.
               The receiving application will forward the message as soon as the destination can be reached
               again.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> SYN
            <a name="v3-AcknowledgementDetailCode-SYN"> </a> 
          </td> 
          <td> Syntax error</td> 
          <td> 
                        Reflects errors in the syntax or structure of the communication.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN102
            <a name="v3-AcknowledgementDetailCode-SYN102"> </a> 
          </td> 
          <td> Data type error</td> 
          <td> 
                        The attribute contained data of the wrong data type, e.g. a numeric
               attribute contained &quot;FOO&quot;.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN105
            <a name="v3-AcknowledgementDetailCode-SYN105"> </a> 
          </td> 
          <td> Required element missing</td> 
          <td> 
                        
                           Description: Required association or attribute missing in message;
               or the sequence of the classes is different than required by the standard or one of the
               conformance profiles identified in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN100
            <a name="v3-AcknowledgementDetailCode-SYN100"> </a> 
          </td> 
          <td> Required association missing</td> 
          <td> 
                        Required association missing in message; or the sequence of the
               classes is different than required by the standard or one of the conformance profiles
               identified in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN101
            <a name="v3-AcknowledgementDetailCode-SYN101"> </a> 
          </td> 
          <td> Required attribute missing</td> 
          <td> 
                        A required attribute is missing in a class.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN114
            <a name="v3-AcknowledgementDetailCode-SYN114"> </a> 
          </td> 
          <td> Insufficient repetitions</td> 
          <td> 
                        
                           Description: The number of repetitions of a group of association
               or attributes is less than the required minimum for the standard or of one of the conformance
               profiles or templates identified in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN106
            <a name="v3-AcknowledgementDetailCode-SYN106"> </a> 
          </td> 
          <td> Terminology error</td> 
          <td> 
                        
                           Description: A coded attribute or datatype property violates
               one of the terminology constraints specified in the standard or one of the conformance
               profiles or templates declared by the instance.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN103
            <a name="v3-AcknowledgementDetailCode-SYN103"> </a> 
          </td> 
          <td> Value not found in code system</td> 
          <td> 
                        An attribute value was compared against the corresponding code
               system, and no match was found.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN104
            <a name="v3-AcknowledgementDetailCode-SYN104"> </a> 
          </td> 
          <td> Invalid code system in CNE</td> 
          <td> 
                        An attribute value referenced a code system that is not valid
               for an attribute constrained to CNE.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN107
            <a name="v3-AcknowledgementDetailCode-SYN107"> </a> 
          </td> 
          <td> Deprecated code</td> 
          <td> 
                        
                           Description: A coded attribute is referencing a code that has
               been deprecated by the owning code system.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN108
            <a name="v3-AcknowledgementDetailCode-SYN108"> </a> 
          </td> 
          <td> Number of repetitions exceeds limit</td> 
          <td> 
                        
                           Description: The number of repetitions of a (group of) association(s)
               or attribute(s) exceeds the limits of the standard or of one of the conformance profiles
               or templates identified in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN110
            <a name="v3-AcknowledgementDetailCode-SYN110"> </a> 
          </td> 
          <td> Number of association repetitions exceeds limit</td> 
          <td> 
                        The number of repetitions of a (group of) association(s) exceeds
               the limits of the standard or of one of the conformance profiles identified in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 3</td> 
          <td>     SYN112
            <a name="v3-AcknowledgementDetailCode-SYN112"> </a> 
          </td> 
          <td> Number of attribute repetitions exceeds limit</td> 
          <td> 
                        The number of repetitions of an attribute exceeds the limits of
               the standard or of one of the conformance profiles identified in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN109
            <a name="v3-AcknowledgementDetailCode-SYN109"> </a> 
          </td> 
          <td> Mandatory element with null value</td> 
          <td> 
                        
                           Description: An attribute or association identified as mandatory
               in a specification or declared conformance profile or template has been specified with
               a null flavor.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN111
            <a name="v3-AcknowledgementDetailCode-SYN111"> </a> 
          </td> 
          <td> Value does not match fixed value</td> 
          <td> 
                        
                           Description: The value of an attribute or property differs
               from the fixed value asserted in the standard or one of the conformance profiles or templates
               declared in the message.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   SYN113
            <a name="v3-AcknowledgementDetailCode-SYN113"> </a> 
          </td> 
          <td> Formal constraint violation</td> 
          <td> 
                        
                           Description: A formal constraint asserted in the standard or
               one of the conformance profiles or templates declared in the message has been violated.
            <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> 
  <url value="http://terminology.hl7.org/CodeSystem/v3-AcknowledgementDetailCode"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.5.1100"/> 
  </identifier> 
  <version value="2018-08-12"/> 
  <name value="v3.AcknowledgementDetailCode"/> 
  <title value="v3 Code System AcknowledgementDetailCode"/> 
  <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="  OpenIssue:
Missing description."/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://terminology.hl7.org/ValueSet/v3-AcknowledgementDetailCode"/> 
  <hierarchyMeaning value="is-a"/> 
  <content value="complete"/> 
  <property> 
    <code value="notSelectable"/> 
    <uri value="http://hl7.org/fhir/concept-properties#notSelectable"/> 
    <description value="Indicates that the code is abstract - only intended to be used as a selector for other
       concepts"/> 
    <type value="boolean"/> 
  </property> 
  <concept> 
    <code value="_AcknowledgementDetailNotSupportedCode"/> 
    <display value="AcknowledgementDetailNotSupportedCode"/> 
    <definition value="Refelects rejections because elements of the communication are not supported in the current
       context."/> 
    <property> 
      <code value="notSelectable"/> 
      <valueBoolean value="true"/> 
    </property> 
    <concept> 
      <code value="NS200"/> 
      <display value="Unsupported interaction"/> 
      <definition value="The interaction (or: this version of the interaction) is not supported."/> 
    </concept> 
    <concept> 
      <code value="NS202"/> 
      <display value="Unsupported processing id"/> 
      <definition value="The Processing ID is not supported."/> 
    </concept> 
    <concept> 
      <code value="NS203"/> 
      <display value="Unsupported version id"/> 
      <definition value="The Version ID is not supported."/> 
    </concept> 
    <concept> 
      <code value="NS250"/> 
      <display value="Unsupported processing Mode"/> 
      <definition value="The processing mode is not supported."/> 
    </concept> 
    <concept> 
      <code value="NS260"/> 
      <display value="Unknown sender"/> 
      <definition value="The Device.id of the sender is unknown."/> 
    </concept> 
    <concept> 
      <code value="NS261"/> 
      <display value="Unrecognized attentionline"/> 
      <definition value="The receiver requires information in the attentionLine classes for routing purposes."/> 
    </concept> 
  </concept> 
  <concept> 
    <code value="INTERR"/> 
    <display value="Internal system error"/> 
    <definition value="An internal software component (database, application, queue mechanism, etc.) has failed,
       leading to inability to process the message."/> 
  </concept> 
  <concept> 
    <code value="NOSTORE"/> 
    <display value="No storage space for message."/> 
    <definition value="Rejection: The message can't be stored by the receiver due to an unspecified internal
       application issue. The message was neither processed nor stored by the receiving application."/> 
  </concept> 
  <concept> 
    <code value="RTEDEST"/> 
    <display value="Message routing error, destination unreachable."/> 
    <definition value="Error: The destination of this message is known to the receiving application. Messages
       have been successfully routed to that destination in the past. The link to the destination
       application or an intermediate application is unavailable."/> 
  </concept> 
  <concept> 
    <code value="RTUDEST"/> 
    <display value="Error: Message routing error, unknown destination."/> 
    <definition value="The destination of this message is unknown to the receiving application. The receiving
       application in the message does not match the application which received the message.
       The message was neither routed, processed nor stored by the receiving application."/> 
  </concept> 
  <concept> 
    <code value="RTWDEST"/> 
    <display value="Message routing warning, destination unreachable."/> 
    <definition value="Warning: The destination of this message is known to the receiving application. Messages
       have been successfully routed to that destination in the past. The link to the destination
       application or an intermediate application is (temporarily) unavailable. The receiving
       application will forward the message as soon as the destination can be reached again."/> 
  </concept> 
  <concept> 
    <code value="SYN"/> 
    <display value="Syntax error"/> 
    <definition value="Reflects errors in the syntax or structure of the communication."/> 
    <concept> 
      <code value="SYN102"/> 
      <display value="Data type error"/> 
      <definition value="The attribute contained data of the wrong data type, e.g. a numeric attribute contained
         &quot;FOO&quot;."/> 
    </concept> 
    <concept> 
      <code value="SYN105"/> 
      <display value="Required element missing"/> 
      <definition value="Description: Required association or attribute missing in message; or the sequence of
         the classes is different than required by the standard or one of the conformance profiles
         identified in the message."/> 
      <concept> 
        <code value="SYN100"/> 
        <display value="Required association missing"/> 
        <definition value="Required association missing in message; or the sequence of the classes is different than
           required by the standard or one of the conformance profiles identified in the message."/> 
      </concept> 
      <concept> 
        <code value="SYN101"/> 
        <display value="Required attribute missing"/> 
        <definition value="A required attribute is missing in a class."/> 
      </concept> 
      <concept> 
        <code value="SYN114"/> 
        <display value="Insufficient repetitions"/> 
        <definition value="Description: The number of repetitions of a group of association or attributes is less
           than the required minimum for the standard or of one of the conformance profiles or templates
           identified in the message."/> 
      </concept> 
    </concept> 
    <concept> 
      <code value="SYN106"/> 
      <display value="Terminology error"/> 
      <definition value="Description: A coded attribute or datatype property violates one of the terminology constraints
         specified in the standard or one of the conformance profiles or templates declared by
         the instance."/> 
      <concept> 
        <code value="SYN103"/> 
        <display value="Value not found in code system"/> 
        <definition value="An attribute value was compared against the corresponding code system, and no match was
           found."/> 
      </concept> 
      <concept> 
        <code value="SYN104"/> 
        <display value="Invalid code system in CNE"/> 
        <definition value="An attribute value referenced a code system that is not valid for an attribute constrained
           to CNE."/> 
      </concept> 
      <concept> 
        <code value="SYN107"/> 
        <display value="Deprecated code"/> 
        <definition value="Description: A coded attribute is referencing a code that has been deprecated by the owning
           code system."/> 
      </concept> 
    </concept> 
    <concept> 
      <code value="SYN108"/> 
      <display value="Number of repetitions exceeds limit"/> 
      <definition value="Description: The number of repetitions of a (group of) association(s) or attribute(s)
         exceeds the limits of the standard or of one of the conformance profiles or templates
         identified in the message."/> 
      <concept> 
        <code value="SYN110"/> 
        <display value="Number of association repetitions exceeds limit"/> 
        <definition value="The number of repetitions of a (group of) association(s) exceeds the limits of the standard
           or of one of the conformance profiles identified in the message."/> 
      </concept> 
      <concept> 
        <code value="SYN112"/> 
        <display value="Number of attribute repetitions exceeds limit"/> 
        <definition value="The number of repetitions of an attribute exceeds the limits of the standard or of one
           of the conformance profiles identified in the message."/> 
      </concept> 
    </concept> 
    <concept> 
      <code value="SYN109"/> 
      <display value="Mandatory element with null value"/> 
      <definition value="Description: An attribute or association identified as mandatory in a specification or
         declared conformance profile or template has been specified with a null flavor."/> 
    </concept> 
    <concept> 
      <code value="SYN111"/> 
      <display value="Value does not match fixed value"/> 
      <definition value="Description: The value of an attribute or property differs from the fixed value asserted
         in the standard or one of the conformance profiles or templates declared in the message."/> 
    </concept> 
    <concept> 
      <code value="SYN113"/> 
      <display value="Formal constraint violation"/> 
      <definition value="Description: A formal constraint asserted in the standard or one of the conformance profiles
         or templates declared in the message has been violated."/> 
    </concept> 
  </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.