pub struct NutritionIntakeInner {Show 48 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub instantiates_canonical: Vec<Option<String>>,
pub instantiates_canonical_ext: Vec<Option<FieldExtension>>,
pub instantiates_uri: Vec<Option<String>>,
pub instantiates_uri_ext: Vec<Option<FieldExtension>>,
pub based_on: Vec<Option<Reference>>,
pub based_on_ext: Vec<Option<FieldExtension>>,
pub part_of: Vec<Option<Reference>>,
pub part_of_ext: Vec<Option<FieldExtension>>,
pub status: EventStatus,
pub status_ext: Option<FieldExtension>,
pub status_reason: Vec<Option<CodeableConcept>>,
pub status_reason_ext: Vec<Option<FieldExtension>>,
pub code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub subject: Reference,
pub subject_ext: Option<FieldExtension>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub occurrence: Option<NutritionIntakeOccurrence>,
pub occurrence_ext: Option<NutritionIntakeOccurrenceExtension>,
pub recorded: Option<DateTime>,
pub recorded_ext: Option<FieldExtension>,
pub reported: Option<NutritionIntakeReported>,
pub reported_ext: Option<NutritionIntakeReportedExtension>,
pub consumed_item: Vec<Option<NutritionIntakeConsumedItem>>,
pub consumed_item_ext: Vec<Option<FieldExtension>>,
pub ingredient_label: Vec<Option<NutritionIntakeIngredientLabel>>,
pub ingredient_label_ext: Vec<Option<FieldExtension>>,
pub performer: Vec<Option<NutritionIntakePerformer>>,
pub performer_ext: Vec<Option<FieldExtension>>,
pub location: Option<Reference>,
pub location_ext: Option<FieldExtension>,
pub derived_from: Vec<Option<Reference>>,
pub derived_from_ext: Vec<Option<FieldExtension>>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
A record of food or fluid that is being consumed by a patient. A NutritionIntake may indicate that the patient may be consuming the food or fluid now or has consumed the food or fluid in the past. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay or through an app that tracks food or fluids consumed. The consumption information may come from sources such as the patient’s memory, from a nutrition label, or from a clinician documenting observed intake.
NutritionIntake v5.0.0
Record of food or fluid being taken by a patient
A record of food or fluid that is being consumed by a patient. A NutritionIntake may indicate that the patient may be consuming the food or fluid now or has consumed the food or fluid in the past. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay or through an app that tracks food or fluids consumed. The consumption information may come from sources such as the patient’s memory, from a nutrition label, or from a clinician documenting observed intake.
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
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.
implicit_rules: Option<String>A set of rules under which this content was created
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 its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
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).
text: Option<Narrative>Text summary of the resource, for human interpretation
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 a 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.
contained: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
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.
extension: Vec<Extension>Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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.
modifier_extension: Vec<Extension>Extensions that cannot be ignored
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
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.
identifier: Vec<Option<Identifier>>External identifier
Identifiers associated with this Nutrition Intake that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.
This is a business identifier, not a resource identifier.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_canonical: Vec<Option<String>>Instantiates FHIR protocol or definition
Instantiates FHIR protocol or definition.
instantiates_canonical_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_uri: Vec<Option<String>>Instantiates external protocol or definition
Instantiates external protocol or definition.
instantiates_uri_ext: Vec<Option<FieldExtension>>Extension field.
based_on: Vec<Option<Reference>>Fulfils plan, proposal or order
A plan, proposal or order that is fulfilled in whole or in part by this event.
based_on_ext: Vec<Option<FieldExtension>>Extension field.
part_of: Vec<Option<Reference>>Part of referenced event
A larger event of which this particular event is a component or step.
part_of_ext: Vec<Option<FieldExtension>>Extension field.
status: EventStatusNutritionIntakeStatus; preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
A code representing the patient or other source’s judgment about the state of the intake that this assertion is about. Generally, this will be active or completed.
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 or fluid 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.
status_ext: Option<FieldExtension>Extension field.
status_reason: Vec<Option<CodeableConcept>>NutritionIntakeStatusReason; Reason for current status
Captures the reason for the current state of the NutritionIntake.
This is generally only used for “exception” statuses such as “not-taken”, “on-hold”, “cancelled” or “entered-in-error”. The reason for performing the event at all is captured in reasonCode, not here.
status_reason_ext: Vec<Option<FieldExtension>>Extension field.
code: Option<CodeableConcept>NutritionIntakeCategory; Code representing an overall type of nutrition intake
Overall type of nutrition intake.
code_ext: Option<FieldExtension>Extension field.
subject: ReferenceWho is/was consuming the food or fluid
The person, animal or group who is/was consuming the food or fluid.
subject_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>Encounter associated with NutritionIntake
The encounter that establishes the context for this NutritionIntake.
encounter_ext: Option<FieldExtension>Extension field.
occurrence: Option<NutritionIntakeOccurrence>The date/time or interval when the food or fluid is/was consumed
The interval of time during which it is being asserted that the patient is/was consuming the food or fluid.
This attribute reflects the period over which the patient consumed the food fluid and is expected to be populated on the majority of NutritionIntake. If the food or fluid is still being taken and is expected to continue indefinitely at the time the usage is recorded, the “end” date will be omitted. If the end date is known, then it is included as the “end date”. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.
occurrence_ext: Option<NutritionIntakeOccurrenceExtension>Extension field.
recorded: Option<DateTime>When the intake was recorded
The date when the Nutrition Intake was asserted by the information source.
recorded_ext: Option<FieldExtension>Extension field.
reported: Option<NutritionIntakeReported>Person or organization that provided the information about the consumption of this food or fluid
The person or organization that provided the information about the consumption of this food or fluid. Note: Use derivedFrom when a NutritionIntake is derived from other resources.
reported_ext: Option<NutritionIntakeReportedExtension>Extension field.
consumed_item: Vec<Option<NutritionIntakeConsumedItem>>What food or fluid product or item was consumed
What food or fluid product or item was consumed.
consumed_item_ext: Vec<Option<FieldExtension>>Extension field.
ingredient_label: Vec<Option<NutritionIntakeIngredientLabel>>Total nutrient for the whole meal, product, serving
Total nutrient amounts for the whole meal, product, serving, etc.
Individual item nutrients are not currently included in the resource and will likely end up as a reference in nutritionProduct to represent the individual items.
ingredient_label_ext: Vec<Option<FieldExtension>>Extension field.
performer: Vec<Option<NutritionIntakePerformer>>Who was performed in the intake
Who performed the intake and how they were involved.
performer_ext: Vec<Option<FieldExtension>>Extension field.
location: Option<Reference>Where the intake occurred
Where the intake occurred.
location_ext: Option<FieldExtension>Extension field.
derived_from: Vec<Option<Reference>>Additional supporting information
Allows linking the NutritionIntake to the underlying NutritionOrder, or to other information, such as AllergyIntolerance, that supports or is used to derive the NutritionIntake.
Likely references would be to AllergyIntolerance, Observation or QuestionnaireAnswers.
derived_from_ext: Vec<Option<FieldExtension>>Extension field.
reason: Vec<Option<CodeableReference>>IntakeReason; Reason for why the food or fluid is /was consumed
A reason, Condition or observation for why the food or fluid is /was consumed.
reason_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Further information about the consumption
Provides extra information about the Nutrition Intake that is not conveyed by the other attributes.
note_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for NutritionIntakeInner
impl Clone for NutritionIntakeInner
Source§fn clone(&self) -> NutritionIntakeInner
fn clone(&self) -> NutritionIntakeInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more