FHIRPath Specification, published by Implementable Technology Specifications WG. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/FHIRPath/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: Example Observation - XML Representation

Raw xml | Download

<Observation xmlns="http://hl7.org/fhir">
  <id value="example"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Observation example</b></p><a name="example"> </a><a name="hcexample"> </a><a name="example-en-US"> </a><p><b>status</b>: Final</p><p><b>category</b>: <span title="Codes:{http://terminology.hl7.org/CodeSystem/observation-category vital-signs}">Vital Signs</span></p><p><b>code</b>: <span title="Codes:{http://loinc.org 29463-7}, {http://loinc.org 3141-9}, {http://snomed.info/sct 27113001}, {http://acme.org/devices/clinical-codes body-weight}">Body Weight</span></p><p><b>subject</b>: <a href="Patient-example.html">Jim  Male, DoB: 1974-12-25 ( Medical record number (use: usual, period: 2001-05-06 --&gt; (ongoing)))</a></p><p><b>effective</b>: 2016-03-28</p><p><b>value</b>: 185 lbs<span style="background: LightGoldenRodYellow"> (Details: UCUM  code[lb_av] = '[lb_av]')</span></p></div>
  </text>
  <!--     the mandatory quality flags:     -->
  <status value="final"/>
  <!--    category code is A code that classifies the general type of observation being made. This is used for searching, sorting and display purposes.   -->
  <category>
    <coding>
      <system
              value="http://terminology.hl7.org/CodeSystem/observation-category"/>
      <code value="vital-signs"/>
      <display value="Vital Signs"/>
    </coding>
  </category>
  <!--    
    Observations are often coded in multiple code systems.
      - LOINC provides codes of varying granularity (though not usefully more specific in this particular case) and more generic LOINCs  can be mapped to more specific codes as shown here
      - snomed provides a clinically relevant code that is usually less granular than LOINC
      - the source system provides its own code, which may be less or more granular than LOINC
      -->
  <code>
    <!--     LOINC - always recommended to have a LOINC code     -->
    <coding>
      <system value="http://loinc.org"/>
      <code value="29463-7"/>
      <!--   more generic methodless LOINC   -->
      <display value="Body Weight"/>
    </coding>
    <coding>
      <system value="http://loinc.org"/>
      <code value="3141-9"/>
      <!--   translation is more specific method = measured LOINC   -->
      <display value="Body weight Measured"/>
    </coding>
    <!--     SNOMED CT Codes - becoming more common     -->
    <coding>
      <system value="http://snomed.info/sct"/>
      <code value="27113001"/>
      <display value="Body weight"/>
    </coding>
    <!--     Also, a local code specific to the source system     -->
    <coding>
      <system value="http://acme.org/devices/clinical-codes"/>
      <code value="body-weight"/>
      <display value="Body Weight"/>
    </coding>
  </code>
  <subject>🔗 
    <reference value="Patient/example"/>
  </subject>
  <!-- encounter>
		<reference value="Encounter/example"/>
	</encounter -->
  <effectiveDateTime value="2016-03-28"/>
  <!--     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="185"/>
    <unit value="lbs"/>
    <system value="http://unitsofmeasure.org"/>
    <code value="[lb_av]"/>
  </valueQuantity>
</Observation>