03572 in FHIR
Message Error Condition Codes
Introduced in v2.3.1· hl7· Steward: InM· universal· 14 values· 16 in FHIR
HL7-defined code system of concepts specifying the HL7 (communications) error code. Used in the ERR segment in HL7 Version 2.x messaging.
No description available in the specification.
OID & Vocabulary Information
- THO Canonical URL (v2.0.0)
- http://terminology.hl7.org/CodeSystem/v2-0357
- Table OID
- 2.16.840.1.113883.12.357
- Codesystem OID (v2)
- 2.16.840.1.113883.18.217
- Value Set OID
- 2.16.840.1.113883.21.233
- Binding
- universal
- Expansion
- All codes from codesystem
- Where Used
- ERR-4,
- UTG Code Table
- prev version
Used In Data Elements
14
0 | Message accepted Usage: Success. Optional, as the AA conveys success. Used for systems that must always return a status code. |
100 | Segment sequence error Usage: Error: The message segments were not in the proper order, or required segments are missing. |
101 | Required field missing Usage: Error: A required field is missing from a segment |
102 | Data type error Usage: Error: The field contained data of the wrong data type, e.g., an NM field contained "FOO". |
103 | Table value not found Usage: Error: A field of data type ID or IS was compared against the corresponding table, and no match was found. |
104 | Value too long Usage: Error: a value exceeded the normative length, or the length that the application is able to safely handle. |
200 | Unsupported message type Usage: Rejection: The Message Type is not supported. |
201 | Unsupported event code Usage: Rejection: The Event Code is not supported. |
202 | Unsupported processing id Usage: Rejection: The Processing ID is not supported. |
203 | Unsupported version id Usage: Rejection: The Version ID is not supported. |
204 | Unknown key identifier Usage: 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. THO: 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). 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. |
205 | Duplicate key identifier Usage: Rejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.). THO: 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). 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. |
206 | Application record locked Usage: Rejection: The transaction could not be performed at the application storage level, e.g., database locked. THO: 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). 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. |
207 | Application internal error Usage: Rejection: A catchall for internal errors not explicitly covered by other codes. THO: 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. Definition: An application level error has occurred and the detail for that error is identified in ERR-5. |
16 codes+2 new