HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.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

hl7VS-specimenRejectReason

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v2-0490
Version:2.0.0
Name:Hl7VSSpecimenRejectReason
Status:Active
Title:hl7VS-specimenRejectReason
Definition:

Reasons a specimen may be rejected for a specified observation/result/analysis. Used in Version 2 messaging in the SPM segment.

Publisher:HL7, Inc
OID:2.16.840.1.113883.21.330 (for OID based terminology systems)
Copyright:

Copyright HL7. Licensed under creative commons public domain

Source Resource:XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

 

Expansion

This value set contains 14 concepts

Expansion based on specimenRejectReason v2.1.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v2-0490

CodeDisplayDefinition
EXExpiredExpired
QSQuantity not sufficientQuantity not sufficient
RBBroken containerBroken container
RCClottingClotting
RDMissing collection dateMissing collection date
RAMissing patient ID numberMissing patient ID number
REMissing patient nameMissing patient name
RHHemolysisHemolysis
RIIdentification problemIdentification problem
RMLabelingLabeling
RNContaminationContamination
RPMissing phlebotomist IDMissing phlebotomist ID
RRImproper storageImproper storage
RSName misspellingName misspelling

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
Source 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

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.