FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example Specimen/vma-urine (XML)

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

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

VMA, Random Urine Sample (id = "vma-urine")

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

<Specimen xmlns="http://hl7.org/fhir">
  <id value="vma-urine"/> 
  <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="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://terminology.hl7.org/CodeSystem/v2-0487"/> 
      <code value="RANDU"/> 
      <display value="Urine, Random"/> 
    </coding> 
  </type> 
  <subject> 
    <reference value="Patient/example"/> 
  </subject> 
  <receivedTime value="2015-08-18T07:03:00Z"/> 
  <!--   method is usually implied by type   -->
  <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-18T07:03:00Z"/> 
  </collection> 
  <processing> 
    <description value="Acidify to pH &lt; 3.0 with 6 N HCl."/> 
    <method> 
      <coding> 
        <system value="http://terminology.hl7.org/CodeSystem/v2-0373"/> 
        <code value="ACID"/> 
      </coding> 
    </method> 
    <additive> 
      <display value="6 N HCl"/> 
    </additive> 
    <timeDateTime value="2015-08-18T08:10:00Z"/> 
  </processing> 
  <container> 
    <device> 
      <reference value="Device/device-example-specimen-container-polycup"/> 
    </device> 
    <specimenQuantity> 
      <value value="10"/> 
      <unit value="mls"/> 
    </specimenQuantity> 
  </container> 
</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.