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

Messages

ErrorCodeSystem.versionValues for version differ: '2.0.0' vs '3.0.0'

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 severity of an application error as reported during acknowledgment of messages. Knowing if something is Error, Warning or Information is intrinsic to how an application handles the content and the information flow. Used in HL7 Version 2.x messaging acknowledgment in the ERR segment.
              .experimentalfalse
                .hierarchyMeaningis-a
                  .jurisdiction
                    .nameErrorSeverity
                      .publisherHealth Level Seven International
                        .purposeUnderlying Master Code System for V2 table 0516 (Error Severity)
                          .statusactive
                            .titleerrorSeverity
                              .urlhttp://terminology.hl7.org/CodeSystem/v2-0516
                                .version2.0.03.0.0
                                • Values Differ
                                .versionNeededfalse

                                  Concepts

                                  CodeDisplaystatusv2-table-deprecatedv2-concCommentv2-concCommentAsPubstatusv2-table-deprecatedv2-concCommentv2-concCommentAsPubComments
                                  .WWarningactiveactiveUse this severity when parts of the message may not have been stored.Use this severity when parts of the message may not have been stored.Transaction successful, but there may issuesTransaction successful, but there may issuesactiveactiveUse this severity when parts of the message may not have been stored.Use this severity when parts of the message may not have been stored.Transaction successful, but there may issuesTransaction successful, but there may issues
                                    .IInformationactiveactivee.g., inform patiente.g., inform patientTransaction was successful but includes information e.g., inform patientTransaction was successful but includes information e.g., inform patientactiveactivee.g., inform patiente.g., inform patientTransaction was successful but includes information e.g., inform patientTransaction was successful but includes information e.g., inform patient
                                      .EErroractiveactiveTransaction was unsuccessfulTransaction was unsuccessfulactiveactiveTransaction was unsuccessfulTransaction was unsuccessful
                                        .FFatal ErroractiveactiveMessage not processed due to application or network failure conditionMessage not processed due to application or network failure conditionactiveactiveMessage not processed due to application or network failure conditionMessage not processed due to application or network failure condition