# text.div
Generated Narrative: CodeSystem v2-0357

Language: en

Properties

This code system defines the following properties for its concepts

Name | Code | URI | Type | Description
Status | status | http://hl7.org/fhir/concept-properties#status | code | A code that indicates the status of the concept
deprecated | v2-table-deprecated | http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated | code | Version of HL7 in which the code was deprecated
V2 Concept Comment | v2-concComment | http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment | string | V2 Concept Comment
V2 Concept Comment As Published | v2-concCommentAsPub | http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub | string | V2 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 hierarchy:

Code | Display | Definition | Status | V2 Concept Comment | V2 Concept Comment As Published | Deutsch (German, de)
0 | Message accepted | Message accepted | active | 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. | Nachricht akzeptiert
100 | Segment sequence error | Segment sequence error | active | 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. | Fehler in der Segmentreihenfolge
101 | Required field missing | Required field missing | active | Error: A required field is missing from a segment | Error: A required field is missing from a segment | erforderliches Feld leer
102 | Data type error | Data type error | active | 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". | Datentypfehler
103 | Table value not found | Table value not found | active | 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. | fehlender Eintrag in der Tabelle
104 | Value too long | Value too long | active | 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. | N | 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. | N | Error | |
200 | Unsupported message type | Unsupported message type | active | Rejection: The Message Type is not supported. | Rejection: The Message Type is not supported. | Nachrichtentyp wird nicht unterstützt
201 | Unsupported event code | Unsupported event code | active | Rejection: The Event Code is not supported. | Rejection: The Event Code is not supported. | Ereignis wird nicht unterstützt
202 | Unsupported processing id | Unsupported processing id | active | Rejection: The Processing ID is not supported. | Rejection: The Processing ID is not supported. | Processing-ID wird nicht unterstützt
203 | Unsupported version id | Unsupported version id | active | Rejection: The Version ID is not supported. | Rejection: The Version ID is not supported. | 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. | B | 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 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. | B | 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 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. | B | 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 error | An application level error has occurred and the detail for that error is identified in ERR-5. | active | 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

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

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

# copyright
This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

# property[].description
A code that indicates the status of the concept

# property[].description
Version of HL7 in which the code was deprecated

# concept[].property[].valueString
Success. Optional, as the AA conveys success. Used for systems that must always return a status code.

# concept[].property[].valueString
Success. Optional, as the AA conveys success. Used for systems that must always return a status code.

# concept[].property[].valueString
Error: The message segments were not in the proper order, or required segments are missing.

# concept[].property[].valueString
Error: The message segments were not in the proper order, or required segments are missing.

# concept[].property[].valueString
Error: A required field is missing from a segment

# concept[].property[].valueString
Error: A required field is missing from a segment

# concept[].property[].valueString
Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".

# concept[].property[].valueString
Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO".

# concept[].property[].valueString
Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.

# concept[].property[].valueString
Error: A field of data type ID or IS was compared against the corresponding table, and no match was found.

# concept[].property[].valueString
Error: a value exceeded the normative length, or the length that the application is able to safely handle.

# concept[].property[].valueString
Error: a value exceeded the normative length, or the length that the application is able to safely handle.

# concept[].definition
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.

# concept[].property[].valueString
Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.

# concept[].definition
Any other error with the HL7 syntax that is not captured in any of the other error codes in this set.

# concept[].property[].valueString
Rejection: The Message Type is not supported.

# concept[].property[].valueString
Rejection: The Message Type is not supported.

# concept[].property[].valueString
Rejection: The Event Code is not supported.

# concept[].property[].valueString
Rejection: The Event Code is not supported.

# concept[].property[].valueString
Rejection: The Processing ID is not supported.

# concept[].property[].valueString
Rejection: The Processing ID is not supported.

# concept[].property[].valueString
Rejection:  The Version ID is not supported.

# concept[].property[].valueString
Rejection:  The Version ID is not supported.

# concept[].definition
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.

# concept[].property[].valueString
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).

# concept[].property[].valueString
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.

# concept[].definition
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.

# concept[].property[].valueString
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).

# concept[].property[].valueString
Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).

# concept[].definition
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.

# concept[].property[].valueString
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).

# concept[].property[].valueString
Rejection: The transaction could not be performed at the application storage level, e.g., database locked.

# concept[].definition
An application level error has occurred and the detail for that error is identified in ERR-5.

# concept[].property[].valueString
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.

# concept[].property[].valueString
Rejection: A catchall for internal errors not explicitly covered by other codes.