HL7.TERMINOLOGY\messageErrorCondition

This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 7.0.0. For a full list of available versions, see the Directory of published versions

CodeSystem: messageErrorCondition

Summary

Defining URL:

http://terminology.hl7.org/CodeSystem/v2-0357

Version:

2.2.0

Name:

MessageErrorCondition

Status:

Active as of 2019-12-01

Definition:

HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging.

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.217 (for OID based terminology systems)

Value Set:

http://terminology.hl7.org/ValueSet/v2-0357 ( 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:

Hl7VSMessageErrorConditionCodes

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-0357 defines the following codes:

Additional Language Displays

Code	Deutsch (German, de)
0	Nachricht akzeptiert
100	Fehler in der Segmentreihenfolge
101	erforderliches Feld leer
102	Datentypfehler
103	fehlender Eintrag in der Tabelle
104
198
199
200	Nachrichtentyp wird nicht unterstützt
201	Ereignis wird nicht unterstützt
202	Processing-ID wird nicht unterstützt
203	Version wird nicht unterstützt
204	Schlüsselwert nicht gefunden
205	doppelter Schlüsselwert
206	Datensatz durch Applikation gesperrt
207	applikationsinterner Fehler

History

Date

Action

Custodian

Author

Comment

2020-05-06

revise

Vocabulary WG

Ted Klein

Migrated to the UTG maintenance environment and publishing tooling.

Code	Display	Definition	V2 Concept Comment	V2 Concept Comment As Published
0	Message accepted	Message accepted	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.
100	Segment sequence error	Segment sequence error	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.
101	Required field missing	Required field missing	Error: A required field is missing from a segment	Error: A required field is missing from a segment
102	Data type error	Data type error	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".
103	Table value not found	Table value not 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.
104	Value too long	Value too long	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.
198	Non-Conformant Cardinality	An error has been encountered related to HL7 message content. Message is not -conformant with the applicable specification’s (base standard, conformance profile or implementation profile) cardinality.	Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.
199	Other HL7 Error	Any other error with the HL7 syntax that is not captured in any of the other error codes in this set.	Error
200	Unsupported message type	Unsupported message type	Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.
201	Unsupported event code	Unsupported event code	Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.
202	Unsupported processing id	Unsupported processing id	Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.
203	Unsupported version id	Unsupported version id	Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.
204	Unknown key identifier	Retained for backwards compatibility only: This situation should be reported in ERR-5 (Application Error Code) using code 101 (Unknown Key Identifier) from code system HL70533.	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.
205	Duplicate key identifier	Retained for backwards compatibility only: This situation should be reported in ERR-5 (Application Error Code) using code 102 (Duplicate Key Identifier) from code system HL70533.	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.).
206	Application record locked	Retained for backwards compatibility only: This situation should be reported in ERR-5 (Application Error Code) using code 103 (Application record locked) from code system HL70533.	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.
207	Application error	An application level error has occurred and the detail for that error is identified in ERR-5.	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.