v2+ Vocabulary
0.3.0 - Working Draft to present the concept ideas (FO)

v2+ Vocabulary - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CodeSystem: Message Error Condition Codes (2.9 - 1.2.0) (Experimental)

Official URL: http://terminology.hl7.org/v2plusvocab/CodeSystem/MessageErrorConditionV120 Version: 1.2.0
Active as of 2025-03-06 Computable Name: MessageErrorConditionV120
Other Identifiers: http://hl7.org/oid#urn:oid:2.16.840.1.113883.18.217

Copyright/Legal: HL7 Inc., 2024

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

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

Generated Narrative: CodeSystem MessageErrorConditionV120

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
version introduced versionIntroduced http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionIntroduced string version when was this code introduced
versionDeprecated versionDeprecated http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionDeprecated string version when was this code deprecated
status status http://hl7.org/fhir/concept-properties#status code current status of this code
comment comment http://hl7.org/fhir/concept-properties#comment string further comment on this code
usage usage http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#usage string usage notes for this code
modified modified http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#modified dateTime date of last modification

Concepts

This case-sensitive code system http://terminology.hl7.org/v2plusvocab/CodeSystem/MessageErrorConditionV120 defines the following codes:

CodeDisplayDefinitionversion introducedstatuscommentmodifiedDeutsch (German, de)
0 Message accepted Message accepted 2.3.1 Success. Optional, as the AA conveys success. Used for systems that must always return a status code. 2015-07-13 Nachricht akzeptiert
100 Segment sequence error Segment sequence error 2.3.1 Error: The message segments were not in the proper order, or required segments are missing. 2015-07-13 Fehler in der Segmentreihenfolge
101 Required field missing Required field missing 2.3.1 Error: A required field is missing from a segment 2015-07-13 erforderliches Feld leer
102 Data type error Data type error 2.3.1 Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO". 2015-07-13 Datentypfehler
103 Table value not found Table value not found 2.3.1 Error: A field of data type ID or IS was compared against the corresponding table, and no match was found. 2015-07-13 fehlender Eintrag in der Tabelle
104 Value too long Value too long 2.7 Error: a value exceeded the normative length, or the length that the application is able to safely handle. 2015-07-13
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. 2.9 Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message. 2022-08-25
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. 2.9 Error 2022-08-25
200 Unsupported message type Unsupported message type 2.3.1 Rejection: The Message Type is not supported. 2015-07-13 Nachrichtentyp wird nicht unterstützt
201 Unsupported event code Unsupported event code 2.3.1 Rejection: The Event Code is not supported. 2015-07-13 Ereignis wird nicht unterstützt
202 Unsupported processing id Unsupported processing id 2.3.1 Rejection: The Processing ID is not supported. 2015-07-13 Processing-ID wird nicht unterstützt
203 Unsupported version id Unsupported version id 2.3.1 Rejection: The Version ID is not supported. 2015-07-13 Version wird nicht unterstützt
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. 2.3.1 backward 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). 2017-07-16 Schlüsselwert nicht gefunden
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. 2.3.1 backward 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). 2017-07-16 doppelter Schlüsselwert
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. 2.3.1 backward 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). 2017-07-16 Datensatz durch Applikation gesperrt
207 Application error An application level error has occurred and the detail for that error is identified in ERR-5. 2.3.1 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. 2017-07-25 applikationsinterner Fehler