CodeSystem Comparison between http://terminology.hl7.org/CodeSystem/v2-0357 vs http://terminology.hl7.org/CodeSystem/v2-0357

Messages

Metadata

Name	Value		Comments
caseSensitive	true
compositional	false
content	complete
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
date	2019-12-01
description	HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging.
experimental	false
hierarchyMeaning	is-a
jurisdiction
name	MessageErrorCondition
publisher	Health Level Seven International
purpose	Underlying Master Code System for V2 table 0357 (Message Error Condition Codes)
status	active
title	messageErrorCondition
url	http://terminology.hl7.org/CodeSystem/v2-0357
version	2.0.0
versionNeeded	false

Concepts

Code	Display		status		deprecated		v2-concComment		v2-concCommentAsPub		status		deprecated		v2-concComment		v2-concCommentAsPub		v2-table-deprecated		Comments
0	Message accepted		A	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.	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.	A	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.	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		A	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.	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.	A	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.	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		A	active			Error: A required field is missing from a segment	Error: A required field is missing from a segment	Error: A required field is missing from a segment	Error: A required field is missing from a segment	A	active			Error: A required field is missing from a segment	Error: A required field is missing from a segment	Error: A required field is missing from a segment	Error: A required field is missing from a segment
102	Data type error		A	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".	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".	A	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".	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		A	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.	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.	A	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.	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		A	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.	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.	A	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.	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		N	N			Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.	Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.			N	N			Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.	Error: Cardinality is listed as [0..3] and more than 3 of the identified element are present in the message.
199	Other HL7 Error		N	N			Error	Error			N	N			Error	Error
200	Unsupported message type		A	active			Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.	A	active			Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.	Rejection: The Message Type is not supported.
201	Unsupported event code		A	active			Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.	A	active			Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.	Rejection: The Event Code is not supported.
202	Unsupported processing id		A	active			Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.	A	active			Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.	Rejection: The Processing ID is not supported.
203	Unsupported version id		A	active			Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.	A	active			Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.	Rejection: The Version ID is not supported.
204	Unknown key identifier		B	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).	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.	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.	B	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).	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.	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		B	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).	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.).	Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).	B	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).	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.).	Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).
206	Application record locked		B	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).	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.	Rejection: The transaction could not be performed at the application storage level, e.g., database locked.	B	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).	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.	Rejection: The transaction could not be performed at the application storage level, e.g., database locked.
207	Application error		A	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.	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.	Rejection: A catchall for internal errors not explicitly covered by other codes.	A	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.	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.	Rejection: A catchall for internal errors not explicitly covered by other codes.