---
type: "example"
title: "Specimen Example: specimen-example"
resource: "Specimen"
example: "specimen-example"
---
# Specimen Example: specimen-example

## Narrative

\[Put rendering here\]

## Example XML



```xml
<?xml version="1.0" encoding="UTF-8"?>
<Specimen xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://hl7.org/fhir ../../schema/plandefinition.xsd"
	xmlns="http://hl7.org/fhir">
	<id value="101"/>
	<!--text>
    <status value="generated" />
    <div xmlns="http://www.w3.org/1999/xhtml">[Put rendering here]</div>
  </text>-->
	<identifier>
		<!-- a specimen identifier - e.g. assigned when the specimen was taken this is often not done -->
		<system value="http://ehr.acme.org/identifiers/collections"/>
		<value value="23234352356"/>
	</identifier>
	<identifier>
	    <type>
					  <coding>
						  <system value="http://terminology.hl7.org/CodeSystem/v2-0203"/>
						  <code value="ACSN"/>
						  <display value="Accession ID"/>
					   </coding>
		</type>
		<system value="http://lab.acme.org/specimens/2011"/>
		<value value="X352356"/>
	</identifier>
	<status value="available"/>
	<type>
		<!--
   Type is a loosely defined field because there is such a lot of variation in how it is used.
   The principal variation is how much information that could be represented elsewhere is also
   represented here. For instance, here's some possible types:
     lithium heparin plasma   (+ .container.additive) (e.g. SNOMED CT 446272009)
     transfusion bag of blood (+ container.type)
     Peritoneal lavage        (+ collection.bodySite)
   If the type includes other fields, it would be normal not to populate the other fields

   Note that this practice is so widespread that it's pointless to try and stop it -->
		<coding>
			<system value="http://snomed.info/sct"/>
			<code value="122555007"/>
			<display value="Venous blood specimen"/>
		</coding>
	</type>
	<subject>
		<reference value="Patient/example"/>
		<display value="Peter Patient"/>
	</subject>
	<receivedTime value="2011-03-04T07:03:00Z"/>
	<request>
		<!-- this points to the order that caused the sample to be drawn -->
		<reference value="ServiceRequest/example"/>
	</request>
	<collection> 
		<collector>
			<!-- in practice, collecter is almost always recorded -->
			<reference value="Practitioner/example"/>
		</collector>
		<!-- the time of collection is usually required. Usually a point in time, but can be a period
      (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine) -->
		<collectedDateTime value="2011-05-30T06:15:00Z"/>
		<quantity>
			<value value="6"/>
			<unit value="mL"/>
			<!-- e.g. full -->
		</quantity>
		<!-- method is usually implied by type -->
		<method>
			<coding>
				<system value="http://terminology.hl7.org/CodeSystem/v2-0488"/>
				<code value="LNV"/>
			</coding>
		</method>
		<!-- bodysite is usually implied by type too its here to demonstrate its usage to indicating the draw site in this case-->
		<bodySite>
		     <concept>
			      <coding>
				          <system value="http://snomed.info/sct"/>
				          <code value="49852007"/>
				          <display value="Structure of median cubital vein (body structure)"/>
			          </coding>
			 </concept>
		</bodySite>
	</collection>
	<!--
      the container identifier is not the same as the specimen identifier
      usually, it is pre-printed/implanted etc.on the container prior to
      use. It might a RFID in the container, or it might be a UDI
      (http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/UniqueDeviceIdentification/)
    -->
    <container>
	<deviceCanonical value="http://hl7.org/fhir/Device/device-example-specimen-container-green-gel-vacutainer"/>

	<!-- if there's only one container, then this value is the same
     as .collection.quantity (usually). This is for when there is more
     than one container -->
	<specimenQuantity>
		<value value="3"/>
		<unit value="mL"/>
	</specimenQuantity>
	</container>
	<note>
		<text value="Specimen is grossly lipemic"/>
	</note>
</Specimen>
```