R4 Draft for Comment

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

V2-0357.vs.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form)

FHIR Value set/code system definition for HL7 v2 table 0357 ( Message Error Condition Codes)

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v2-0357"/> 
  <meta> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="additional"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Message Error Condition Codes</p> 

      <table class="grid">
        <tr> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Description</b> 
          </td> 
          <td> 
            <b> Comment</b> 
          </td> 
          <td> 
            <b> Version</b> 
          </td> 
        </tr> 
        <tr> 
          <td> 0
            <a name="0"> </a> 
          </td> 
          <td> Message accepted</td> 
          <td> Success. Optional, as the AA conveys success. Used for systems that must always return
               a status code.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 100
            <a name="100"> </a> 
          </td> 
          <td> Segment sequence error</td> 
          <td> Error: The message segments were not in the proper order, or required segments are missing.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 101
            <a name="101"> </a> 
          </td> 
          <td> Required field missing</td> 
          <td> Error: A required field is missing from a segment</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 102
            <a name="102"> </a> 
          </td> 
          <td> Data type error</td> 
          <td> Error: The field contained data of the wrong data type, e.g. an NM field contained &quot;FOO&quot;.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 103
            <a name="103"> </a> 
          </td> 
          <td> Table value not found</td> 
          <td> Error: A field of data type ID or IS was compared against the corresponding table, and
               no match was found.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 104
            <a name="104"> </a> 
          </td> 
          <td> Value too long</td> 
          <td> Error: a value exceeded the normative length, or the length that the application is able
               to safely handle.</td> 
          <td> added v2.7</td> 
        </tr> 
        <tr> 
          <td> 200
            <a name="200"> </a> 
          </td> 
          <td> Unsupported message type</td> 
          <td> Rejection: The Message Type is not supported.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 201
            <a name="201"> </a> 
          </td> 
          <td> Unsupported event code</td> 
          <td> Rejection: The Event Code is not supported.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 202
            <a name="202"> </a> 
          </td> 
          <td> Unsupported processing id</td> 
          <td> Rejection: The Processing ID is not supported.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 203
            <a name="203"> </a> 
          </td> 
          <td> Unsupported version id</td> 
          <td> Rejection:  The Version ID is not supported.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 204
            <a name="204"> </a> 
          </td> 
          <td> Unknown key identifier</td> 
          <td> Rejection: The ID of the patient, order, etc., was not found. Used for transactions other
               than additions, e.g. transfer of a non-existent patient.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 205
            <a name="205"> </a> 
          </td> 
          <td> Duplicate key identifier</td> 
          <td> Rejection: The ID of the patient, order, etc., already exists. Used in response to addition
               transactions (Admit, New Order, etc.).</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 206
            <a name="206"> </a> 
          </td> 
          <td> Application record locked</td> 
          <td> Rejection: The transaction could not be performed at the application storage level, e.g.
               database locked.</td> 
          <td> added v2.3.1</td> 
        </tr> 
        <tr> 
          <td> 207
            <a name="207"> </a> 
          </td> 
          <td> Application internal error</td> 
          <td> Rejection: A catchall for internal errors not explicitly covered by other codes.</td> 
          <td> added v2.3.1</td> 
        </tr> 
      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="External"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/v2-0357"/> 
  <version value="2.8.2"/> 
  <name value="v2 Message Error Condition Codes"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="FHIR Value set/code system definition for HL7 v2 table 0357 ( Message Error Condition
     Codes)"/> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://hl7.org/fhir/v2/0357"/> 
    </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.