Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 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 . Page versions: R5 R4B R4 R3 R2

Nutritionorder-example-proteinsupplement.xml

Raw XML (canonical form)

Nutrition Order Protein Supplement Example (id = "proteinsupplement")

<NutritionOrder xmlns="http://hl7.org/fhir">
  <id value="proteinsupplement"/>
  <!--    id = proteinsupplement  file name = nutritionorder-example-proteinsupplement.xml  Name=
   Protein Supplement  Description = Nutrition Order Protein Supplement Canonical Example
edited by Eric Haas Health eData Inc
...narrative generated by FHIR build
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h3>Nutrition Order Protein Supplement Canonical Example</h3>
      <ul>
        <li>
          <b>Patient: </b>Peter Chalmers</li>
        <li>
          <b>Orderer: </b>Dr Adam Careful</li>
        <li>
          <b>Date: </b>2014-09-17</li>
        <li>
          <b>Supplement(Brand): </b>High protein powder ( Beneprotein )</li>
        <li>
          <b>Schedule: </b>1 scoop with meal</li>
      </ul>
    </div>
  </text>
   --><!--    EH: This example has no food exclusions or preferences    -->
  <text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: proteinsupplement</p><p><b>patient</b>: <a>Peter Chalmers</a></p><p><b>orderer</b>: <a>Dr Adam Careful</a></p><p><b>identifier</b>: 123</p><p><b>encounter</b>: <a>Inpatient</a></p><p><b>dateTime</b>: 17/09/2014</p><p><b>status</b>: active</p><h3>Supplements</h3><table><tr><td>-</td><td><b>Type</b></td><td><b>ProductName</b></td><td><b>Schedule</b></td><td><b>Quantity</b></td><td><b>Instruction</b></td></tr><tr><td>*</td><td>High Protein Powder <span>(Details : {SNOMED CT code '442991000124104' = '442991000124104', given as 'Adult high
               protein formula'}; {http://goodhealthhospital.org/supplement-type-codes code '1000' =
               '??', given as 'High Protein Powder'})</span></td><td>Beneprotein</td><td>Starting 10/02/2015, Do at meals</td><td>1 scoop<span> (Details: http://unitsofmeasure.org code {scoop} = '??')</span></td><td>Beneprotein 1 scoop TID with meal.starting on  2015-02-10</td></tr></table></div></text><patient>
    <reference value="Patient/example"/>
    <display value="Peter Chalmers"/>
  </patient>
  <orderer>
    <reference value="Practitioner/example"/>
    <display value="Dr Adam Careful"/>
  </orderer>
  <identifier>
    <system value="http://goodhealthhospital.org/nutrition-orders"/>
    <value value="123"/>
  </identifier>
  <encounter>
    <reference value="Encounter/example"/>
    <display value="Inpatient"/>
  </encounter>
  <dateTime value="2014-09-17"/>  <status value="active"/>


  <!--    EH: use supplement element    -->
  <supplement>
    <type>
      <coding>
        <system value="http://snomed.info/sct"/>
        <code value="442991000124104"/>
        <display value="Adult high protein formula"/>
      </coding>
      <coding>
        <system value="http://goodhealthhospital.org/supplement-type-codes"/>
        <code value="1000"/>
        <display value="High Protein Powder"/>
      </coding>
      <text value="High Protein Powder"/>
    </type>
    <productName value="Beneprotein"/>
    <schedule>
      <repeat>
        <boundsPeriod>
          <start value="2015-02-10"/>
        </boundsPeriod>
        <when value="C"/>
      </repeat>
    </schedule>
    <quantity>
      <value value="1"/>
      <unit value="scoop"/>
      <system value="http://unitsofmeasure.org"/>
      <code value="{scoop}"/>
    </quantity>
    <!--    EH:  use the .instructions element to list diet  supplement order   -->
    <instruction value="Beneprotein 1 scoop TID with meal.starting on  2015-02-10"/>
  </supplement>
</NutritionOrder>

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.