GAO Ballot Package

This page is part of the FHIR Specification (v1.1.0: STU 3 Ballot 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3 R2

This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.

1.25.3.1.357 HL7 Version 2 Table 0357

This is a table defined as part of HL7 v2 . Related FHIR content: v2 Message Error Condition Codes.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/v2-0357
Name:v2 Message Error Condition Codes
Definition:FHIR Value set/code system definition for HL7 v2 table 0357 ( Message Error Condition Codes)
OID:??
System URL:http://hl7.org/fhir/v2/0357
System OID:2.16.840.1.133883.18.217
Source ResourceXML / JSON

This value set is not currently used

1.25.3.1.357.1 Content Logical Definition

Message Error Condition Codes

CodeDescriptionDeutsch (German)CommentVersion
0 Message acceptedNachricht akzeptiertSuccess. Optional, as the AA conveys success. Used for systems that must always return a status code.added v2.3.1
100 Segment sequence errorFehler in der SegmentreihenfolgeError: The message segments were not in the proper order, or required segments are missing.added v2.3.1
101 Required field missingerforderliches Feld leerError: A required field is missing from a segmentadded v2.3.1
102 Data type errorDatentypfehlerError: The field contained data of the wrong data type, e.g. an NM field contained "FOO".added v2.3.1
103 Table value not foundfehlender Eintrag in der TabelleError: A field of data type ID or IS was compared against the corresponding table, and no match was found.added v2.3.1
104 Value too longError: a value exceeded the normative length, or the length that the application is able to safely handle.added v2.7
200 Unsupported message typeNachrichtentyp wird nicht unterstütztRejection: The Message Type is not supported.added v2.3.1
201 Unsupported event codeEreignis wird nicht unterstütztRejection: The Event Code is not supported.added v2.3.1
202 Unsupported processing idProcessing-ID wird nicht unterstütztRejection: The Processing ID is not supported.added v2.3.1
203 Unsupported version idVersion wird nicht unterstütztRejection: The Version ID is not supported.added v2.3.1
204 Unknown key identifierSchlüsselwert nicht gefundenRejection: The ID of the patient, order, etc., was not found. Used for transactions other than additions, e.g. transfer of a non-existent patient.added v2.3.1
205 Duplicate key identifierdoppelter SchlüsselwertRejection: The ID of the patient, order, etc., already exists. Used in response to addition transactions (Admit, New Order, etc.).added v2.3.1
206 Application record lockedDatensatz durch Applikation gesperrtRejection: The transaction could not be performed at the application storage level, e.g. database locked.added v2.3.1
207 Application internal errorapplikationsinterner FehlerRejection: A catchall for internal errors not explicitly covered by other codes.added v2.3.1