Diet intake Observation
Diet intake observation profile is used to record any source of nutrition (food, meal etc) that is consumed
Below is the
categoryused for this ObservationSystem Code Display http://snomed.info/sct 364395008 Dietary intake (observable entity) Below is a list of possible values of
codefor this Observation (The valueset ObservationCodes has all the Observation codes, the below list only shows the codes that are relevant to this profile)System Code Display http://snomed.info/sct 246251008 Type of meal (attribute) value(x):- codeableConcept - if the meal type is codes, like a mysugr tag related to meal (ValueSet - MealTypes)
- string - if the meal type is a freetext description, like in mySugr logentry
subjectSHALL be referenced only to patient profile.performerSHALL be referenced only to patient profile.deviceSHALL be referenced to Device/DeviceMetric profile.Can have child observations like nutritional values(carb, fat, energy intake etc) using the
relatedelementcomponentmay include related data like type of foods part of that meal etc. Possible codes are below:System Code Display http://roche.com/fhir/rdc/cs carbs-complexity Carbs complexity http://snomed.info/sct 246250009 Type of food (attribute) http://snomed.info/sct 229957008 Food composition types (substance)
Main extensions used in this profile are:
- EventTiming - Event of the day that observation has been taken place.
- RegisteredTimestamp - Timestamp when the observation was registered on the device/application
- Observation-reference - Link to a related image. (mySugr scope)
Overview
`The below overview shows the elements of the resource, data type and the cardinality of each. Further details like "Binding"/"Fixed values"/"contraints" etc can be found on clicking on each element.
Canonical url - http://roche.com/fhir/rdc/StructureDefinition/diet-intake-observation
Details
Table
XML
JSON
Example
Sample with food types and associated image link
NOTE to developer: This is only a sample resource. For the resource structure and valusets always refer the section "Overview" under each profile definition in the Implementation guide. If an element is defined as an array (0..*) in the standard and in RDC profile as an object (0..1), please note that it should still carry the structure of an array with one occurance. The structure for all resources as per the FHIR standard can be found at https://www.hl7.org/fhir/STU3/resourcelist.html