View raw Markdown
type: resourceresource: NutritionIntake

NutritionIntake

Introduction

Scope and Usage

Note to Balloters: To ensure this resource is ready for Normative status, we are seeking ballot comment on the substantive content. The key changes made since R5 include:

  • Removed the instantiates workflow elements NutritionIntake.instantiatesCanonical and NutritionIntake.instantiatesUri and advise implementers to use the workflow instantiates extensions
  • Consolidated NutritionIntake.consumedItem and NutritionIntake.ingredientLabel into a NutritionIntake.nutritionItem backbone
  • The nutritionintake-status-reason code system used in NutritionIntake.statusReason is currently defined in the FHIR specification, but is expected to be moved to HL7 Terminology (THO).

Note to Implementers: For an overview of this resource and others in the Nutrition domain, also see the module page.

The NutritionIntake resource, in conjunction with the NutritionProduct resource, is utilized to capture details about the consumption of foods (i.e., solid and/or liquid), supplements, enteral nutrition, and infant formula. Dietitians and other practitioners use the data to calculate how much nutrition a patient has taken in. NutritionIntake represents the event of consuming food (i.e. solid and/or liquid), etc. and NutritionProduct represents the actual food and formula items.

NutritionIntake can also be used to record a person’s intake through the use of food tracking apps (e.g.MyFitnessPal), inpatient hospital consumption or administration, or a student’s meal consumption in a school district.

NutritionIntake can be utilized in many environments where food is served or consumed: hospitals/acute care, meal tracking systems, enteral or supplement in a home setting, outpatient settings, long-term care, etc. NutritionIntake should be general enough to capture intake regardless of country or region.

Parenteral nutrition is out of scope as this ordering is handled through MedicationRequest, thus administration of parenteral nutrition should also be captured through MedicationAdministration.

Boundaries and Relationships

Background and Context

As a dietitian, it is important to be able to know what a person is consuming and/or administered to assess the adequacy of the patient’s intake. Capturing a patient’s intake is important to establish a baseline, determine care, track trends, and see improvement in that patient. Dietitians might use intake data to see patterns, such as when a diabetic patient’s blood glucose is consistently high given the distribution of carbohydrates. Other practitioners have the need to monitor intake as well; for example, a nurse might need to know intake for administering insulin prior to meals, a speech therapist needs this information for ensuring safe administration of food, or a physician may need to ensure a patient fluid restriction is consistent with recommendations.

Having intake documented within its own resource allows for consistency in documentation across multiple disciplines and settings. In some instances, the Observation resource has been extended to capture intake; while this allows for a quick way to document intake, the Observation resource does not provide all the detail necessary, such as capturing energy and nutrients (including vitamins, minerals, carbohydrates, etc.). Previous implementation attempts of using the Observation resource have noted this is cumbersome and has required too many extensions without being able to document all the necessary details tied to ingredients in food (i.e., solid and/or liquid) products.

Note to Balloters: The nutritionintake-status-reason code system used in NutritionIntake.statusReason is currently defined in the FHIR specification, but is expected to be moved to HL7 Terminology (THO).

Notes

Notes:

StructureDefinition

Elements (Simplified)

Mappings

Resource Packs

list-NutritionIntake-packs.xml

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

<List xmlns="http://hl7.org/fhir">
  <id value="NutritionIntake-packs"/>
  <status value="current"/>
  <mode value="working"/>
</List>

Search Parameters

Full Search Parameters

Examples

Full Examples

Mapping Exceptions

nutritionintake-event-mapping-exceptions.xml

Divergent Elements

Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is. | resource=NutritionIntake is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for NutritionIntake.status contains codes that assert the status of the consumption of the food (i.e. solid and/or liquid), breastmilk, infant formula, supplements, enteral formula by the patient (for example, stopped or on hold) as well as codes that assert the status of the Nutrition Intake itself (for example, entered in error).

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Unmapped Elements

nutritionintake-fivews-mapping-exceptions.xml

Unmapped Elements