HL7 Terminology (THO)
5.1.0 - Publication
This page is part of the HL7 Terminology (v5.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/rejection-criteria | Version: 0.1.0 | |||
Draft as of 2020-02-24 | Maturity Level: 1 | Responsible: HL7 (FHIR Project) | Computable Name: RejectionCriterion | |
Other Identifiers: id: urn:oid:2.16.840.1.113883.4.642.3.856 |
Criterion for rejection of the specimen by laboratory.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/rejection-criteria
This value set contains 5 concepts
Expansion based on RejectionCriterion v0.1.0 (CodeSystem)
Code | System | Display | Definition |
hemolized | http://terminology.hl7.org/CodeSystem/rejection-criteria | hemolized specimen | blood specimen hemolized. |
insufficient | http://terminology.hl7.org/CodeSystem/rejection-criteria | insufficient specimen volume | insufficient quantity of specimen. |
broken | http://terminology.hl7.org/CodeSystem/rejection-criteria | broken specimen container | specimen container broken. |
clotted | http://terminology.hl7.org/CodeSystem/rejection-criteria | specimen clotted | specimen clotted. |
wrong-temperature | http://terminology.hl7.org/CodeSystem/rejection-criteria | specimen temperature inappropriate | specimen temperature inappropriate. |
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
Date | Action | Custodian | Author | Comment |
2020-10-14 | revise | Vocabulary WG | Grahame Grieve | Reset Version after migration to UTG |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |