Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Specimen-example-isolate.xml

Raw XML (canonical form)

Bacterial Isolate from Stool sample (id = "isolate")

<Specimen xmlns="http://hl7.org/fhir">
  <id value="isolate"/>
  <!--   text>
    <status value="generated" />
    <div xmlns="http://www.w3.org/1999/xhtml">[Put rendering here]</div>
  </text>   -->
  <text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: isolate</p><p><b>contained</b>: </p><p><b>status</b>: available</p><p><b>type</b>: Bacterial isolate specimen <span>(Details : {SNOMED CT code '429951000124103' = '429951000124103', given as 'Bacterial
           isolate specimen'})</span></p><p><b>parent</b>: id: stool; status: unavailable; Stool specimen <span>(Details : {SNOMED CT code '119339001' = '119339001', given as 'Stool specimen'})</span>; Patient/example; X352356; receivedTime: 16/08/2015 5:03:00 PM</p><p><b>subject</b>: <a>Patient/example</a></p><p><b>accessionIdentifier</b>: X352356-ISO1</p><p><b>receivedTime</b>: 18/08/2015 5:03:00 PM</p><h3>Collections</h3><table><tr><td>-</td><td><b>Collector</b></td><td><b>Collected[x]</b></td><td><b>Method</b></td></tr><tr><td>*</td><td><a>Practitioner/f202</a></td><td>16/08/2015 5:03:00 PM</td><td>Plates, Blood Agar <span>(Details : {http://hl7.org/fhir/v2/0488 code 'BAP' = 'Plates, Blood Agar)</span></td></tr></table></div></text><contained>
    <Specimen>
      <id value="stool"/>
      <status value="unavailable"/>
      <type>
        <coding>
          <system value="http://snomed.info/sct"/>
          <code value="119339001"/>
          <display value="Stool specimen"/>
        </coding>
      </type>
      <subject>
        <reference value="Patient/example"/>
      </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/2015"/>
        <value value="X352356"/>
      </accessionIdentifier>
      <receivedTime value="2015-08-16T07:03:00Z"/>
      <collection>
        <collector>
          <!--    in practice, collecter is almost always recorded    -->
          <display value="Patient"/>
        </collector>
        <comment value="Patient dropped off specimen"/>
        <!--    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-08-16T06:15:00Z"/>
        <!--    method is usually implied by type    -->
        <method>
          <coding>
            <system value="http://hl7.org/fhir/v2/0488"/>
            <code value="LNV"/>
          </coding>
        </method>
      </collection>
    </Specimen>
  </contained>
  <!--   
   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    -->
   <status value="available"/>
  <type>
    <coding>
      <system value="http://snomed.info/sct"/>
      <code value="429951000124103"/>
      <display value="Bacterial isolate specimen"/>
    </coding>
  </type><parent><reference value="#stool"/></parent>
  <subject>
    <reference value="Patient/example"/>
  </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-ISO1"/>
  </accessionIdentifier>
  <receivedTime value="2015-08-18T07:03:00Z"/>
  <collection>
    <collector>
      <!--    in practice, collecter is almost always recorded    -->
      <reference value="Practitioner/f202"/>
    </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="2015-08-16T07:03:00Z"/>
    <!--    method is usually implied by type    -->
    <method>
      <coding>
        <system value="http://hl7.org/fhir/v2/0488"/>
        <code value="BAP"/>
      </coding>
    </method>
  </collection>
</Specimen>

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.