FHIR 5.0.0 © HL7.org  |  FHIRsmith 0.8.5  |  Server Home  |  TX Home  |  Capability Statement  |  Terminology Capabilities  |  Operations  |  Problems  |   

TX: CodeSystem v2-0357

Properties

Language en
Defining URL http://terminology.hl7.org/CodeSystem/v2-0357
Version 3.0.0
Name MessageErrorCondition
Title messageErrorCondition
Status active
Definition

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)
Publisher Health Level Seven International
Committee inm
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
Value Set hl7VS-messageErrorConditionCodes

Properties

This code system defines the following properties for its concepts

Code URI Type Description
status http://hl7.org/fhir/concept-properties#status code A code that indicates the status of the concept
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-concComment http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment string V2 Concept Comment
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 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.