Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Example NutritionOrder/infantenteral (Narrative)

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

This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile NutritionOrder .

Generated Narrative: NutritionOrder infantenteral

Resource NutritionOrder "infantenteral"

identifier : id: 123 http://www.acme.org/nutritionorders /123

status : active Active

intent : order Order

subject : Patient/example: Peter Chalmers "Peter CHALMERS"

encounter : Encounter/example: Inpatient

dateTime : 2014-09-17

orderer : Practitioner/example: Dr Adam Careful "Adam CAREFUL"

enteralFormula

BaseFormulaTypes - Concept * infant formula + iron ( SNOMED CT #412414007) baseFormulaProductName : Acme Infant Formula + Iron

additive Types - Concept type * Carbohydrate ( Enteral Formula Additive Type Code #carbohydrate) productName : Acme High Carbohydrate Additive

caloricDensity : 20 calories per ounce (Details: UCUM code cal/[foz_us] codecal/[foz_us] = 'cal/foz_us')

routeOfAdministration : Swallow, oral ( RouteOfAdministration #PO)

administration

Schedules

- Timing
* Starting 2014-09-17, Once per 3 hours

quantity : 4 ounces (Details: UCUM code [foz_us] code[foz_us] = 'foz_us')

maxVolumeToDeliver administrationInstruction : 32 ounces (Details: UCUM code [foz_us] = 'foz_us')

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

additive

ModularTypes

- Concept
* Carbohydrate

productName : Acme High Carbohydrate Additive

 

 

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.