STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Spec-uslab-example2.xml

Raw XML (canonical form)

USLab Specimen Profile Example: Urine- first catch (id = "spec-uslab-example2")

<Specimen xmlns="http://hl7.org/fhir">
  <id value="spec-uslab-example2"/>
  <text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: spec-uslab-example2</p><p><b>identifier</b>: SID456 (OFFICIAL)</p><p><b>accessionIdentifier</b>: 21041205000001 (OFFICIAL)</p><p><b>type</b>: Urine, First Void <span>(Details : {SNOMED CT code '698276005' = 'First stream urine sample (specimen)', given
           as 'First stream urine sample'}; {http://ehr.goodhealthclinic.org code 'UFV' = '??', given
           as 'Urine, First Void'})</span></p><p><b>subject</b>: <a>Todd Lerr</a></p><h3>Collections</h3><table><tr><td>-</td><td><b>Collected[x]</b></td></tr><tr><td>*</td><td>05/12/2014</td></tr></table></div></text><identifier>
    <!--    a specimen identifier - e.g. assigned when the specimen was taken by the orderer/placer
      use the accession number for the filling lab    -->
    <!--   Placer ID   -->
    <use value="official"/>
    <system value="http://ehr.goodhealthclinic.org/identifiers/specimen"/>
    <value value="SID456"/>
    <!--   Filler ID moved to accsession number
  <identifier>
    <use value="official"></use>
    <label  value="Filler Specimen ID"></label>
    <system value="http://lis.acmelabs.org/identifiers/specimen"/>
    <value value="SID456"/>
  </identifier>
   -->
  </identifier>
  <accessionIdentifier>
    <use value="official"/>
    <system value="http://lis.acmelabs.org/identifiers/accession"/>
    <value value="21041205000001"/>
  </accessionIdentifier>
  <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  :(
        -->
    <!--   choice of SNOMED CT concept code...   -->
    <coding>
      <system value="http://snomed.info/sct"/>
      <!--   EH: Note to balloters  - lots of choices for uriine but this is best for Aptima 2 GC-CT
         -->
      <code value="698276005"/>
      <display value="First stream urine sample"/>
    </coding>
    <!--    and or local code   -->
    <coding>
      <system value="http://ehr.goodhealthclinic.org"/>
      <code value="UFV"/>
      <display value="Urine, First Void"/>
    </coding>
    <text value="Urine, First Void"/>
  </type>
  <subject>
    <reference value="Patient/patient-uslab-example1"/>
    <display value="Todd Lerr"/>
  </subject>
  <collection>
    <!--    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="2014-12-05"/>
  </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.