This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). 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 Quantitative Observation Profile Example: Capillary Blood Lead (id = "uslab-example1")
<Observation 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><!-- FHIR build is generating the narratives <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <ul> <li> obs-uslab-example1.xml</li> <li> id: uslab-example1</li> <li> Name: USLab Observation Example1</li> <li>Description: USLab Quantitative Observation Profile Canonical Example: Capillary Blood Lead</li> </ul> </div> </text> --><!-- extension for specimen reject goes here - not for this use case <extension url="http://hl7.org/fhir/StructureDefinition/uslabspecimenrejectreason"> <valueCodeableConcept> <coding> <system value="http://hl7.org/fhir/v2/0490"/> <code value="EX"/> <display value="Expired"/> </coding> </valueCodeableConcept> </extension> --><!-- extension for observation kindt goes here --> <extension url="http://hl7.org/fhir/StructureDefinition/uslabobservationkind"> <valueCode value="result"/> </extension><!-- EH : The local and /or LOINC test codes go here --> <code><!-- EH: LOINC code goes here --> <coding> <system value="http://loinc.org"/> <code value="10368-9"/> <display value="Lead [Mass/volume] in Capillary blood"/> </coding><!-- EH: LOINC code goes here --> <coding> <system value="urn:oid:2.16.840.1.113883.3.72.5.24"/> <code value="CAPLD"/> <display value="Blood Lead, Capillary"/> </coding> <text value="Capillary Blood Lead Screen"/> </code><!-- In FHIR, units may be represented twice. Once in the agreed human representation, and once in a coded form. Both is best, since it's not always possible to infer one from the other in code. When a computable unit is provided, UCUM (http://unitsofmeasure.org) is always preferred, but it doesn't provide notional units (such as "tablet"), etc. For these, something else is required (e.g. Snomed-CT) --> <valueQuantity> <value value="65"/> <units value="microgram per deciliter"/> <system value="http://unitsofmeasure.org"/> <code value="ug/dL"/> </valueQuantity><!-- eH dataabsent reason would go here if valueQuantity was empty e.g.: <dataAbsentReason value="error"/> --> <interpretation> <coding> <system value="http://hl7.org/fhir/v2/0078"/> <code value="H"/> </coding> </interpretation> <appliesDateTime value="2014-12-03"/><!-- EH: Showing dateTime to ss with TZO although only needed to Day --> <issued value="2014-12-04T15:42:15-08:00"/> <status value="final"/> <identifier> <use value="official"/> <type> <text value="lab test result ID"/> </type> <system value="http://lis.acmelabs.org/identifiers/labtestresult"/> <value value="1234"/> </identifier> <subject> <reference value="Patient/uslab-example1"/> <display value="Todd Lerr"/> </subject> <specimen> <reference value="Specimen/uslab-example1"/> <display value="Blood sample"/> </specimen> <performer> <reference value="Practitioner/uslab-example1"/> <display value="Dr Leonard T Bloodraw Jr"/> </performer> <referenceRange> <high> <value value="5.0"/> <units value="microgram per deciliter"/> <system value="http://unitsofmeasure.org"/> <code value="ug/dL"/> </high> </referenceRange> </Observation>
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.