CodeSystem Comparison between http://terminology.hl7.org/CodeSystem/v2-0357 vs http://terminology.hl7.org/CodeSystem/v2-0357

Messages

Metadata

NameValueComments
.caseSensitivetrue
    .compositionalfalse
      .contentcomplete
        .copyrightThis material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
          .date2019-12-01
            .descriptionHL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging.
              .experimentalfalse
                .hierarchyMeaningis-a
                  .jurisdiction
                    .nameMessageErrorCondition
                      .publisherHealth Level Seven International
                        .purposeUnderlying Master Code System for V2 table 0357 (Message Error Condition Codes)
                          .statusactive
                            .titlemessageErrorCondition
                              .urlhttp://terminology.hl7.org/CodeSystem/v2-0357
                                .version2.0.0
                                  .versionNeededfalse

                                    Concepts

                                    CodeDisplaystatusdeprecatedv2-concCommentv2-concCommentAsPubstatusdeprecatedv2-concCommentv2-concCommentAsPubComments
                                    .0Message acceptedAASuccess. Optional, as the AA conveys success. Used for systems that must always return a status code.Success. Optional, as the AA conveys success. Used for systems that must always return a status code.Success. Optional, as the AA conveys success. Used for systems that must always return a status code.Success. Optional, as the AA conveys success. Used for systems that must always return a status code.AASuccess. Optional, as the AA conveys success. Used for systems that must always return a status code.Success. Optional, as the AA conveys success. Used for systems that must always return a status code.Success. Optional, as the AA conveys success. Used for systems that must always return a status code.Success. Optional, as the AA conveys success. Used for systems that must always return a status code.
                                      .100Segment sequence errorAAError: The message segments were not in the proper order, or required segments are missing.Error: The message segments were not in the proper order, or required segments are missing.Error: The message segments were not in the proper order, or required segments are missing.Error: The message segments were not in the proper order, or required segments are missing.AAError: The message segments were not in the proper order, or required segments are missing.Error: The message segments were not in the proper order, or required segments are missing.Error: The message segments were not in the proper order, or required segments are missing.Error: The message segments were not in the proper order, or required segments are missing.
                                        .101Required field missingAAError: A required field is missing from a segmentError: A required field is missing from a segmentError: A required field is missing from a segmentError: A required field is missing from a segmentAAError: A required field is missing from a segmentError: A required field is missing from a segmentError: A required field is missing from a segmentError: A required field is missing from a segment
                                          .102Data type errorAAError: The field contained data of the wrong data type, e.g., an NM field contained "FOO".Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".AAError: The field contained data of the wrong data type, e.g., an NM field contained "FOO".Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".
                                            .103Table value not foundAAError: A field of data type ID or IS was compared against the corresponding table, and no match was found.Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.AAError: A field of data type ID or IS was compared against the corresponding table, and no match was found.Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.
                                              .104Value too longAAError: a value exceeded the normative length, or the length that the application is able to safely handle.Error: a value exceeded the normative length, or the length that the application is able to safely handle.Error: a value exceeded the normative length, or the length that the application is able to safely handle.Error: a value exceeded the normative length, or the length that the application is able to safely handle.AAError: a value exceeded the normative length, or the length that the application is able to safely handle.Error: a value exceeded the normative length, or the length that the application is able to safely handle.Error: a value exceeded the normative length, or the length that the application is able to safely handle.Error: a value exceeded the normative length, or the length that the application is able to safely handle.
                                                .198Non-Conformant CardinalityNNError: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.NNError: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.
                                                  .199Other HL7 ErrorNNErrorErrorNNErrorError
                                                    .200Unsupported message typeAARejection: The Message Type is not supported.Rejection: The Message Type is not supported.Rejection: The Message Type is not supported.Rejection: The Message Type is not supported.AARejection: The Message Type is not supported.Rejection: The Message Type is not supported.Rejection: The Message Type is not supported.Rejection: The Message Type is not supported.
                                                      .201Unsupported event codeAARejection: The Event Code is not supported.Rejection: The Event Code is not supported.Rejection: The Event Code is not supported.Rejection: The Event Code is not supported.AARejection: The Event Code is not supported.Rejection: The Event Code is not supported.Rejection: The Event Code is not supported.Rejection: The Event Code is not supported.
                                                        .202Unsupported processing idAARejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.AARejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.
                                                          .203Unsupported version idAARejection: The Version ID is not supported.Rejection: The Version ID is not supported.Rejection: The Version ID is not supported.Rejection: The Version ID is not supported.AARejection: The Version ID is not supported.Rejection: The Version ID is not supported.Rejection: The Version ID is not supported.Rejection: The Version ID is not supported.
                                                            .204Unknown key identifierBBERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).ERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).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.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.BBERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).ERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).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.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.
                                                              .205Duplicate key identifierBBERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).ERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).BBERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).ERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).
                                                                .206Application record lockedBBERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).ERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).Rejection: The transaction could not be performed at the application storage level, e.g., database locked.Rejection: The transaction could not be performed at the application storage level, e.g., database locked.BBERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).ERR-3 (HL7 Error Code) should be used to convey errors at the structural level and this is an application level error, which should be reported in ERR-5 (Application Error Code).Rejection: The transaction could not be performed at the application storage level, e.g., database locked.Rejection: The transaction could not be performed at the application storage level, e.g., database locked.
                                                                  .207Application errorAAThis value is used when no other value in this list is applicable and there is an application error reported in ERR-5. It is applicable when ERR-3 is required in an implementation guide.This value is used when no other value in this list is applicable and there is an application error reported in ERR-5. It is applicable when ERR-3 is required in an implementation guide.Rejection: A catchall for internal errors not explicitly covered by other codes.Rejection: A catchall for internal errors not explicitly covered by other codes.AAThis value is used when no other value in this list is applicable and there is an application error reported in ERR-5. It is applicable when ERR-3 is required in an implementation guide.This value is used when no other value in this list is applicable and there is an application error reported in ERR-5. It is applicable when ERR-3 is required in an implementation guide.Rejection: A catchall for internal errors not explicitly covered by other codes.Rejection: A catchall for internal errors not explicitly covered by other codes.