HL7 Terminology
2.1.0 - Publication

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

CodeSystem: errorSeverity

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v2-0516
Version:2.2.0
Name:ErrorSeverity
Status:Active as of 2019-12-01
Definition:

HL7-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.

Publisher:HL7, Inc
Committee:Infrastructure And Messaging
Copyright:

Copyright HL7. Licensed under creative commons public domain

Content:Complete: All the concepts defined by the code system are included in the code system resource
OID:2.16.840.1.113883.18.337 (for OID based terminology systems)
Value Set:http://terminology.hl7.org/ValueSet/v2-0516 ( is the value set for all codes in this code system)
Source Resource:XML / JSON / Turtle

This Code system is referenced in the content logical definition of the following value sets:

Properties

CodeURLDescriptionType
statushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statusStatus of the conceptcode
deprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedVersion of HL7 in which the code was deprecatedcode
v2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentV2 Concept Commentstring
v2-concCommentAsPubhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPubV2 Concept Comment As Publishedstring

This code system http://terminology.hl7.org/CodeSystem/v2-0516 defines the following codes:

CodeDisplayDefinitionV2 Concept CommentV2 Concept Comment As Published
W WarningTransaction successful, but there may be issuesUse this severity when parts of the message may not have been stored.Transaction successful, but there may issues
I InformationTransaction was successful but includes informatione.g., inform patientTransaction was successful but includes information e.g., inform patient
E ErrorTransaction was unsuccessfulTransaction was unsuccessful
F Fatal ErrorMessage not processed due to application or network failure conditionMessage not processed due to application or network failure condition

Additional Language Displays

CodeDeutsch (German, de)
WWarnung
IInformation
EFehler
F

History

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.