Release 4B Snapshot #1

This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4

4.3.14.428 Code System http://terminology.hl7.org/CodeSystem/rejection-criteria

Orders and Observations Work Group Maturity Level: 1Draft Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/rejection-criteria
Version:4.3.0-snapshot1
Name:RejectionCriterion
Title:RejectionCriterion
Definition:

Criterion for rejection of the specimen by laboratory.

Committee:Orders and Observations Work Group
OID:2.16.840.1.113883.4.642.4.1260 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

Criterion for rejection of the specimen by laboratory.

This code system http://terminology.hl7.org/CodeSystem/rejection-criteria defines the following codes:

Code Display Definition
hemolized hemolized specimen blood specimen hemolized.
insufficient insufficient specimen volume insufficient quantity of specimen.
broken broken specimen container specimen container broken.
clotted specimen clotted specimen clotted.
wrong-temperature specimen temperature inappropriate specimen temperature inappropriate.

 

See the full registry of code systems defined as part of FHIR.


Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code