This code system http://terminology.hl7.org/CodeSystem/v2-0357 defines the following codes:
| Code | Display | Definition | V2 Table Status | V2 Concept Comment | V2 Concept Comment As Published |
| 0 | Message accepted | Message accepted | A | 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 | A | 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 | A | 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 | A | 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 | A | 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 | A | 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 | A | Rejection: The Message Type is not supported. | Rejection: The Message Type is not supported. |
| 201 | Unsupported event code | Unsupported event code | A | Rejection: The Event Code is not supported. | Rejection: The Event Code is not supported. |
| 202 | Unsupported processing id | Unsupported processing id | A | Rejection: The Processing ID is not supported. | Rejection: The Processing ID is not supported. |
| 203 | Unsupported version id | Unsupported version id | A | 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. | 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. |
| 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.). |
| 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. |
| 207 | Application error | An application level error has occurred and the detail for that error is identified in ERR-5. | A | 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. |