HL7.TERMINOLOGY\errorSeverity

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. 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

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:

Hl7VSErrorSeverity

Properties

Code

URL

Description

Type

status

http://terminology.hl7.org/CodeSystem/utg-concept-properties#status

Status of the concept

code

deprecated

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated

Version of HL7 in which the code was deprecated

code

v2-concComment

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment

V2 Concept Comment

string

v2-concCommentAsPub

http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub

V2 Concept Comment As Published

string

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

Code	Display	Definition	V2 Concept Comment	V2 Concept Comment As Published
W	Warning	Transaction successful, but there may be issues	Use this severity when parts of the message may not have been stored.	Transaction successful, but there may issues
I	Information	Transaction was successful but includes information	e.g., inform patient	Transaction was successful but includes information e.g., inform patient
E	Error	Transaction was unsuccessful		Transaction was unsuccessful
F	Fatal Error	Message not processed due to application or network failure condition		Message not processed due to application or network failure condition

Additional Language Displays

Code	Deutsch (German, de)
W	Warnung
I	Information
E	Fehler
F

History

Date

Action

Custodian

Author

Comment

2020-05-06

revise

Vocabulary WG

Ted Klein

Migrated to the UTG maintenance environment and publishing tooling.