R6 Ballot (2nd Draft)

Publish-box (todo)

Example Specimen/isolate (XML)

Orders and Observations Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Device, Patient, Practitioner

Raw XML (canonical form + also see XML Format Specification)

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

<?xml version="1.0" encoding="UTF-8"?>

<Specimen xmlns="http://hl7.org/fhir">
  <id value="isolate"/> 
  <contained> 
    <Specimen> 
      <id value="stool"/> 
      <accessionIdentifier> 
        <!--   accession identifier - e.g. assigned by the labaratory when it is received.
     This is common, unlike specimen identifier   -->
        <system value="http://lab.acme.org/specimens/2015"/> 
        <value value="X352356"/> 
      </accessionIdentifier> 
      <status value="unavailable"/> 
      <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="119339001"/> 
          <display value="Stool specimen"/> 
        </coding> 
      </type> 
      <subject> 
        <reference value="Patient/example"/> 
      </subject> 
      <receivedTime value="2015-08-16T07:03:00Z"/> 
      <collection> 
        <collector> 
          <!--     in practice, collecter is almost always recorded     -->
          <display value="Patient"/> 
        </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-08-16T06:15:00Z"/> 
        <!--     method is usually implied by type     -->
        <method> 
          <coding> 
            <system value="http://terminology.hl7.org/CodeSystem/v2-0488"/> 
            <code value="LNV"/> 
          </coding> 
        </method> 
      </collection> 
    </Specimen> 
  </contained> 
  <accessionIdentifier> 
    <system value="http://lab.acme.org/specimens/2011"/> 
    <value value="X352356-ISO1"/> 
  </accessionIdentifier> 
  <status value="available"/> 
  <type> 
    <coding> 
      <system value="http://snomed.info/sct"/> 
      <code value="119303007"/> 
      <display value="Microbial isolate specimen"/> 
    </coding> 
    <text value="Bacterial isolate specimen"/> 
  </type> 
  <subject> 
    <reference value="Patient/example"/> 
  </subject> 
  <receivedTime value="2015-08-18T07:03:00Z"/> 
  <parent> 
    <reference value="#stool"/> 
  </parent> 
  <role> 
    <coding> 
      <code value="p"/> 
      <display value="Patient"/> 
    </coding> 
  </role> 
  <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://terminology.hl7.org/CodeSystem/v2-0488"/> 
        <code value="BAP"/> 
      </coding> 
    </method> 
  </collection> 
  <note> 
    <text value="Patient dropped off specimen"/> 
  </note> 
</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.