Release 4 R5 Final QA

This page is part of the FHIR Specification (v4.0.1: R4 (v5.0.0-draft-final: Final QA Preview for R5 - Mixed Normative and STU see ballot notes ) in it's permanent home (it will always be available at this URL). ). 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-infantenteral

Example ValueSet/history-absent-reason (XML)

Orders and Observations Terminology Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : Encounter , Patient , Practitioner
This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile NutritionOrder .

baseFormulaProductName : Acme Infant Formula Raw XML ( canonical form + Iron additiveType : Carbohydrate (Details : {http://terminology.hl7.org/CodeSystem/entformula-additive code 'carbohydrate' = 'Carbohydrate', given as 'Carbohydrate'}) additiveProductName : Acme High Carbohydrate Additive caloricDensity : 20 calories per ounce (Details: UCUM code cal/[foz_us] = 'cal/foz_us') also see XML Format Specification )

routeofAdministration : Swallow, oral (Details : {http://terminology.hl7.org/CodeSystem/v3-RouteOfAdministration code 'PO' = 'Swallow, oral', given as 'Swallow, oral'}) Definition for Value SetFamily History Absent Reason

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

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="history-absent-reason"/> 
  <meta> 
    <lastUpdated value="2023-03-01T23:03:57.298+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <ul> 
        <li> Include all codes defined in 
          <a href="http://terminology.hl7.org/4.0.0/CodeSystem-history-absent-reason.html">
            <code> http://terminology.hl7.org/CodeSystem/history-absent-reason</code> 
          </a> 
        </li> 
      </ul> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pc"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="draft"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/history-absent-reason"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.3.269"/> 
  </identifier> 
  <version value="5.0.0-draft-final"/> 
  <name value="FamilyHistoryAbsentReason"/> 
  <title value="Family History Absent Reason"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2020-12-28T16:55:11+11:00"/> 
  <publisher value="HL7 (FHIR Project)"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
    <telecom> 
      <system value="email"/> 
      <value value="fhir@lists.hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="Codes describing the reason why a family member's history is not available."/> 
  <jurisdiction> 
    <coding> 
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> 
      <code value="001"/> 
      <display value="World"/> 
    </coding> 
  </jurisdiction> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://terminology.hl7.org/CodeSystem/history-absent-reason"/> 
    </include> 
  </compose> 

*
Starting
17/09/2014,
Do
Once
per
3
hours
4
ounces
(Details:
UCUM
code
[foz_us]
=
'foz_us')
maxVolumeToDeliver
:
32
ounces
(Details:
UCUM
code
[foz_us]
=
'foz_us')


</

ValueSet

>


administrationInstruction
:
Add
high
calorie
high
carbohydrate
additive
to
increase
cal/oz
from
24
cal/oz
to
27
cal/oz.
   

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.