Release 5 R6 Ballot (1st Full Ballot)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot4: Release 6 Ballot (1st Full Ballot) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2 for published versions

Example Observation/example (XML)

Maturity Level : N/A
Responsible Owner: Orders and Observations Work Group Standards Status : Informative Compartments : Device , Encounter , Group , Patient , Practitioner , RelatedPerson

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

Jump past Narrative

Simple Weight Example (id = "example")

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

  
      
  display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border:
       1px solid #8da1b4; border-radius: 5px; line-height: 60%  category code is A code that classifies the general type of observation being
         made. This is used for searching, sorting and display purposes.   
    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
       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
    &quot;tablet&quot;), etc. For these, something else is required (e.g. SNOMED
         CT)
     
      <!--    category code is A code that classifies the general type of observation being
   made. This is used for searching, sorting and display purposes.   -->
  
    
      
      
      
    
  
      <!--    
    Observations are often coded in multiple code systems.

<!--   
 This is an example of a simple weight measurement.
   --><Observation xmlns="http://hl7.org/fhir">
  <id value="example"/> 
  <!--    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> 
  <category> 
    <coding> 
      <system value="http://loinc.org"/> 
      <code value="29463-7"/> 
      <!--   methodless LOINC "interoperability category" code   -->
      <display value="Body Weight"/> 
    </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

   codes as shown here

      - snomed provides a clinically relevant code that is usually less granular
   than LOINC

   than LOINC

      - the source system provides its own code, which may be less or more granular
   than LOINC
      -->
  
        
    
      
      
      
    
    
      
      
      
    
        
    
      
      
      
    
        
    
      
      
      
    
  
  
    
  
  
    
  
  
      <!--     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)
       -->
  
    
    
    
    
  

   than LOINC
     -->
  <code> 
    <!--    LOINC - always recommended to have a LOINC code    -->
    <coding> 
      <system value="http://loinc.org"/> 
      <code value="29463-7"/> 
      <display value="Body weight"/> 
    </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> 
  <component> 
    <code> 
      <coding> 
        <system value="http://loinc.org"/> 
        <code value="8361-8"/> 
        <display value="Body position with respect to gravity"/> 
      </coding> 
    </code> 
    <valueCodeableConcept> 
      <coding> 
        <system value="http://snomed.info/sct"/> 
        <code value="10904000"/> 
        <display value="Standing position"/> 
      </coding> 
    </valueCodeableConcept> 
  </component> 


</

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.