HL7 Terminology (THO)
6.3.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO) - Local Development build (v6.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: hl7VS-messageErrorConditionCodes

Official URL: http://terminology.hl7.org/ValueSet/v2-0357 Version: 2.0.0
Active as of 2019-12-01 Responsible: Health Level Seven International Computable Name: Hl7VSMessageErrorConditionCodes
Other Identifiers: OID:2.16.840.1.113883.21.233

Copyright/Legal: 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

HL7 (communications) error codes, as transmitted in a message acknowledgement.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

Expansion performed internally based on codesystem messageErrorCondition v2.0.0 (CodeSystem)

This value set contains 16 concepts

CodeSystemDisplay (en-US)Definition
  0http://terminology.hl7.org/CodeSystem/v2-0357Message acceptedMessage accepted
  100http://terminology.hl7.org/CodeSystem/v2-0357Segment sequence errorSegment sequence error
  101http://terminology.hl7.org/CodeSystem/v2-0357Required field missingRequired field missing
  102http://terminology.hl7.org/CodeSystem/v2-0357Data type errorData type error
  103http://terminology.hl7.org/CodeSystem/v2-0357Table value not foundTable value not found
  104http://terminology.hl7.org/CodeSystem/v2-0357Value too longValue too long
  198http://terminology.hl7.org/CodeSystem/v2-0357Non-Conformant CardinalityAn 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.
  199http://terminology.hl7.org/CodeSystem/v2-0357Other HL7 ErrorAny other error with the HL7 syntax that is not captured in any of the other error codes in this set.
  200http://terminology.hl7.org/CodeSystem/v2-0357Unsupported message typeUnsupported message type
  201http://terminology.hl7.org/CodeSystem/v2-0357Unsupported event codeUnsupported event code
  202http://terminology.hl7.org/CodeSystem/v2-0357Unsupported processing idUnsupported processing id
  203http://terminology.hl7.org/CodeSystem/v2-0357Unsupported version idUnsupported version id
  204http://terminology.hl7.org/CodeSystem/v2-0357Unknown key identifierRetained 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.
  205http://terminology.hl7.org/CodeSystem/v2-0357Duplicate key identifierRetained 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.
  206http://terminology.hl7.org/CodeSystem/v2-0357Application record lockedRetained 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.
  207http://terminology.hl7.org/CodeSystem/v2-0357Application errorAn application level error has occurred and the detail for that error is identified in ERR-5.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.