Nutrition Intake is utilized to capture details about the consumption of foods, fluids, and enteral nutrition.

Note that the representation of this resource as a Basic with extensions in the R4 space is a simplification of the proposed modeling of the NutritionIntake in the R5 resource. Specifically, this mapping makes use of the code element in Basic bound to an example Foods value set to specify that the nutrition intake modeled here is more granular than the approach taken in the R5 resource. In other words, we would expect to see multiple instances of the Basic resource with a single code for each consumedItem, as opposed to modeling intake with a single resource containing multiple consumed items. This approach lends itself more readily to use within measurement and analytic contexts. More discussion is needed with the stewards of the NutritionIntake resource to determine whether this approach is reasonable and make sure there is alignment with the ultimate approach taken in the NutritionIntake resource.

The food item that was consumed

Nutrition Intake is utilized to capture details about the consumption of foods, fluids, and enteral nutrition.

Note that the representation of this resource as a Basic with extensions in the R4 space is a simplification of the proposed modeling of the NutritionIntake in the R5 resource. Specifically, this mapping makes use of the code element in Basic bound to an example Foods value set to specify that the nutrition intake modeled here is more granular than the approach taken in the R5 resource. In other words, we would expect to see multiple instances of the Basic resource with a single code for each consumedItem, as opposed to modeling intake with a single resource containing multiple consumed items. This approach lends itself more readily to use within measurement and analytic contexts. More discussion is needed with the stewards of the NutritionIntake resource to determine whether this approach is reasonable and make sure there is alignment with the ultimate approach taken in the NutritionIntake resource.

An Extension

• value @ url

The individual the event is recorded for.

The Encounter during which this event was created or to which the creation of this record is tightly associated.

The date when this event occurred.

This indicates when the event actually occurred or is occurring, not when it was asked/requested/ordered to occur.

An Extension

• value @ url

The current status of the event.

The food item that was consumed

Nutrition Intake is utilized to capture details about the consumption of foods, fluids, and enteral nutrition.

Note that the representation of this resource as a Basic with extensions in the R4 space is a simplification of the proposed modeling of the NutritionIntake in the R5 resource. Specifically, this mapping makes use of the code element in Basic bound to an example Foods value set to specify that the nutrition intake modeled here is more granular than the approach taken in the R5 resource. In other words, we would expect to see multiple instances of the Basic resource with a single code for each consumedItem, as opposed to modeling intake with a single resource containing multiple consumed items. This approach lends itself more readily to use within measurement and analytic contexts. More discussion is needed with the stewards of the NutritionIntake resource to determine whether this approach is reasonable and make sure there is alignment with the ultimate approach taken in the NutritionIntake resource.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

An Extension

• value @ url

The individual the event is recorded for.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

• value @ url

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

The Encounter during which this event was created or to which the creation of this record is tightly associated.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

• value @ url

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

The date when this event occurred.

This indicates when the event actually occurred or is occurring, not when it was asked/requested/ordered to occur.

An Extension

• value @ url

The current status of the event.

Identifier assigned to the resource for business purposes, outside the context of FHIR.

The food item that was consumed

Must be able to distinguish different types of Basic resources.

Because resource references will only be able to indicate 'Basic', the type of reference will need to be specified in a Profile identified as part of the resource. Refer to the resource notes section for information on appropriate terminologies for this code.

This element is labeled as a modifier because it defines the meaning of the resource and cannot be ignored.

Identifies the patient, practitioner, device or any other resource that is the "focus" of this resource.

Needed for partitioning the resource by Patient.

Optional as not all potential resources will have subjects. Resources associated with multiple subjects can handle this via extension.

Identifies when the resource was first created.

Allows ordering resource instances by time.

Indicates who was responsible for creating the resource instance.

Needed for partitioning the resource.