Release 4B Snapshot 3: Connectathon 32 Base

This page is part of the Snapshot #3 for FHIR Specification (v4.3.0: R4B - STU ). The current version which supercedes this version is 5.0.0 R5 , released to support Connectathon 32 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Nutritionorder-example-infantenteral

Example NutritionOrder/infantenteral (Narrative)

Orders and Observations 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 .


Generated Narrative Narrative: NutritionOrder

Resource NutritionOrder "infantenteral"

identifier : id: 123 id: 123

status : active

intent : order

patient 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

- baseFormulaType : Concept
* infant formula + iron ( SNOMED CT #412414007)

baseFormulaProductName : Acme Infant Formula + Iron

additiveType : additive

Types

- Concept
* Carbohydrate ( Enteral Formula Additive Type Code #carbohydrate)

additiveProductName productName : Acme High Carbohydrate Additive

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

routeofAdministration routeOfAdministration : Swallow, oral ( RouteOfAdministration #PO)

administration

Administrations Schedules

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

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

maxVolumeToDeliver : 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.


 

 

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.