HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

messageErrorCondition

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v2-0357
Version:2.2.0
Name:MessageErrorCondition
Title:messageErrorCondition
Status:Active
Content:All the concepts defined by the code system are included in the code system resource
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
OID:2.16.840.1.113883.18.217 (for OID based terminology systems)
Content Mode:Complete
Value Set:http://terminology.hl7.org/ValueSet/v2-0357 ( is the value set for all codes in this code system)
Copyright:

Copyright HL7. Licensed under creative commons public domain

Source Resource:XML / JSON / Turtle

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

messageErrorCondition

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

Copyright Statement: Copyright HL7. Licensed under creative commons public domain

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

CodeDisplayDefinitionV2 Table StatusV2 Concept CommentV2 Concept Comment As Published
0 Message acceptedMessage acceptedASuccess. 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 errorSegment sequence errorAError: 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 missingRequired field missingAError: A required field is missing from a segmentError: A required field is missing from a segment
102 Data type errorData type errorAError: 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 foundTable value not foundAError: 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 longValue too longAError: 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.NError: 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.NError
200 Unsupported message typeUnsupported message typeARejection: The Message Type is not supported.Rejection: The Message Type is not supported.
201 Unsupported event codeUnsupported event codeARejection: The Event Code is not supported.Rejection: The Event Code is not supported.
202 Unsupported processing idUnsupported processing idARejection: The Processing ID is not supported.Rejection: The Processing ID is not supported.
203 Unsupported version idUnsupported version idARejection: The Version ID is not supported.Rejection: The Version ID is not supported.
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.BERR-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 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.BERR-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 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.BERR-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 errorAn application level error has occurred and the detail for that error is identified in ERR-5.AThis 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.

Additional Language Displays

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

History

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