Contents

<Observation xmlns="http://hl7.org/fhir">
  <id value="example"/>

  <!--
    Observations are often coded in multiple code systems.
      - Loinc provides a very specific code (though not usefully more specific in this particular case)
      - snomed provides a clinically relevant code that is usually less granular than LOINC
      - the source system provides it's 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="3141-9"/>
       <display value="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>

  <!--  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"/>
    <units value="lbs"/>
    <system value="http://unitsofmeasure.org"/>
    <code value="[lb_av]"/>
  </valueQuantity>
  <!--  the mandatory quality flags:  -->
  <status value="final"/>
  <reliability value="ok"/>
  <subject>
      <reference value="Patient/example"/>
  </subject>

</Observation>

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
plan_executor-1.0.2	fixtures/validation/observations/observation-example(example).xml