This page is part of the FHIR Specification (v0.4.0: DSTU 2 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
USLab Specimen Profile Canonical Example: Blood (id = "uslab-example1")
<Specimen xmlns="http://hl7.org/fhir"> <id value="uslab-example1"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div> </text><!-- 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 --> <identifier> <use value="official"/> <label value="Placer Specimen ID"/> <system value="http://ehr.goodhealthclinic.org/identifiers/specimen"/> <value value="SID123"/> </identifier><!-- 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> --><!-- 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... --> <type> <coding> <system value="http://snomed.info/sct"/><!-- EH: Note to balloters - lots of choices for whole blood I chose this. --> <code value="122555007"/> <display value="Venous blood specimen"/> </coding><!-- and or local code --> <coding> <system value="http://ehr.goodhealthclinic.org"/> <code value="BLD"/> <display value="Blood"/> </coding> <text value="Blood sample"/> </type><!-- Patient is required from core --> <subject> <reference value="Patient/uslab-example1"/> <display value="Todd Lerr"/> </subject><!-- accession identifier - e.g. assigned by the labaratory when it is received. This is common, unlike specimen identifier --> <accessionIdentifier> <use value="official"/> <system value="http://lis.acmelabs.org/identifiers/accession"/> <value value="21041205000001"/> </accessionIdentifier> <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"/> <bodySiteCodeableConcept><!-- choice of SNOMED CT concept code... --> <coding> <system value="http://snomed.info/sct"/><!-- EH: Note to balloters - this is to demonstrate use of source for body site not really needed for blood draw. --> <code value=" 53120007"/> <display value="Arm"/> </coding><!-- and or local code --> <coding> <system value="http://ehr.goodhealthclinic.org"/> <code value="ARM"/> <display value="Arm"/> </coding> <text value="Drawn from Arm"/> </bodySiteCodeableConcept> </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.