HL7 Terminology (THO)
5.3.0 - Publication International flag

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

CodeSystem: messageErrorCondition

Official URL: http://terminology.hl7.org/CodeSystem/v2-0357 Version: 2.2.0
Active as of 2019-12-01 Responsible: HL7, Inc Computable Name: MessageErrorCondition
Other Identifiers: id: urn:oid:2.16.840.1.113883.18.217

Copyright/Legal: Copyright HL7. Licensed under creative commons public domain

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

Underlying Master Code System for V2 table 0357 (Message Error Condition Codes)

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

Properties

This code system defines the following properties for its concepts

CodeURITypeDescription
statushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statuscodeStatus of the concept
deprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedcodeVersion of HL7 in which the code was deprecated
v2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentstringV2 Concept Comment
v2-concCommentAsPubhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPubstringV2 Concept Comment As Published

Concepts

This case-sensitive code system http://terminology.hl7.org/CodeSystem/v2-0357 defines the following codes in a Is-A heirarchy:

CodeDisplayDefinitionV2 Concept CommentV2 Concept Comment As PublishedDeutsch (German, de)
0 Message acceptedMessage acceptedSuccess. 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.Nachricht akzeptiert
100 Segment sequence errorSegment sequence errorError: 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.Fehler in der Segmentreihenfolge
101 Required field missingRequired field missingError: A required field is missing from a segmentError: A required field is missing from a segmenterforderliches Feld leer
102 Data type errorData type errorError: 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".Datentypfehler
103 Table value not foundTable value not foundError: 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.fehlender Eintrag in der Tabelle
104 Value too longValue too longError: 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 CardinalityAn 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 ErrorAny other error with the HL7 syntax that is not captured in any of the other error codes in this set.Error
200 Unsupported message typeUnsupported message typeRejection: The Message Type is not supported.Rejection: The Message Type is not supported.Nachrichtentyp wird nicht unterstützt
201 Unsupported event codeUnsupported event codeRejection: The Event Code is not supported.Rejection: The Event Code is not supported.Ereignis wird nicht unterstützt
202 Unsupported processing idUnsupported processing idRejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.Processing-ID wird nicht unterstützt
203 Unsupported version idUnsupported version idRejection: The Version ID is not supported.Rejection: The Version ID is not supported.Version wird nicht unterstützt
204 Unknown key identifierRetained 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.Schlüsselwert nicht gefunden
205 Duplicate key identifierRetained 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.).doppelter Schlüsselwert
206 Application record lockedRetained 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.Datensatz durch Applikation gesperrt
207 Application errorAn 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.applikationsinterner Fehler

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.