Specimen-example.xml

General Specimen Example (id = "101")

Raw XML

<Specimen xmlns="http://hl7.org/fhir">
  <id value="101"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <contained>
    <Substance><!--   text&gt;
    &lt;status value=&quot;generated&quot; /&gt;
    &lt;div xmlns=&quot;http://www.w3.org/1999/xhtml&quot;&gt;[Put rendering here]&lt;/div&gt;
  &lt;/text&gt;   -->
      <id value="hep"/>
      <type>
        <coding>
          <system value="http://hl7.org/fhir/v3/EntityCode"/>
          <code value="HEPL"/>
        </coding>
      </type>
    </Substance>
  </contained><!--    a specimen identifier - e.g. assigned when the specimen was taken
     this is often not done    -->
  <identifier>
    <system value="http://ehr.acme.org/identifiers/collections"/>
    <value value="23234352356"/>
  </identifier><!--   
   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    -->
  <type>
    <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><!--    accession identifier - e.g. assigned by the labaratory when it is received.
     This is common, unlike specimen identifier    -->
  <accessionIdentifier>
    <system value="http://lab.acme.org/specimens/2011"/>
    <value value="X352356"/>
  </accessionIdentifier>
  <receivedTime value="2011-03-04T07:03:00Z"/>
  <collection>
    <collector><!--    in practice, collecter is almost always recorded    -->
      <reference value="Practitioner/example"/>
    </collector><!--    the time of collection is 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"/>
      <units value="mL"/>
    </quantity><!--    e.g. full    --><!--    method is usually implied by type    -->
    <method>
      <coding>
        <system value="http://hl7.org/fhir/v2/0488"/>
        <code value="LNV"/>
      </coding>
    </method>
  </collection>
  <container><!--    
      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/)
     
       -->
    <identifier><!--    this is a serial number off the tube - there's no context such as a system    -->
      <value value="48736-15394-75465"/>
    </identifier>
    <description value="Green Gel tube"/>
    <type><!--    again, this might easily be used to cover additives and capacity as well    -->
      <text value="Vacutainer"/>
    </type>
    <capacity>
      <value value="10"/>
      <units value="mL"/>
    </capacity><!--    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="6"/>
      <units value="mL"/>
    </specimenQuantity>
    <additiveReference>
      <reference value="#hep"/>
    </additiveReference>
  </container>
</Specimen>