A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident.

Referenced by an Order Request (workflow).

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.

An Extension

R5: NutritionOrder.basedOn (new:Reference(CarePlan,NutritionOrder,ServiceRequest))

Element NutritionOrder.basedOn has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.basedOn has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.groupIdentifier (new:Identifier)

Element NutritionOrder.groupIdentifier has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.groupIdentifier has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.priority (new:code)

Element NutritionOrder.priority has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.priority has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supportingInformation (new:Reference(Resource))

Element NutritionOrder.supportingInformation has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supportingInformation has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.performer (new:CodeableReference(CareTeam,Practitioner,PractitionerRole,RelatedPerson,Patient,Organization))

Element NutritionOrder.performer has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.performer has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.outsideFoodAllowed (new:boolean)

Element NutritionOrder.outsideFoodAllowed has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.outsideFoodAllowed has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

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 manageable, 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The workflow status of the nutrition order/request.

Typically the system placing the order sets the status to "requested". Thereafter, the order is maintained by the receiver that updates the status as the request is handled. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Codes identifying the lifecycle stage of the nutrition order.

Indicates the level of authority/intentionality associated with the NutrionOrder and where the request fits into the workflow chain.

When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.

Codes indicating the degree of authority/intentionality associated with a nutrition order.

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

The person (patient) who needs the nutrition order for an oral diet, nutritional supplement and/or enteral or formula feeding.

An Extension

R5: NutritionOrder.subject additional types from child elements (display, identifier, reference, type)

Element NutritionOrder.subject is mapped to FHIR R4 element NutritionOrder.patient as SourceIsBroaderThanTarget. The mappings for NutritionOrder.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element NutritionOrder.subject with unmapped reference targets: Group.

The date and time that this nutrition order was requested.

R5: NutritionOrder.basedOn (new:Reference(CarePlan,NutritionOrder,ServiceRequest))

Element NutritionOrder.basedOn has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.basedOn has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.groupIdentifier (new:Identifier)

Element NutritionOrder.groupIdentifier has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.groupIdentifier has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.priority (new:code)

Element NutritionOrder.priority has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.priority has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supportingInformation (new:Reference(Resource))

Element NutritionOrder.supportingInformation has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supportingInformation has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.performer (new:CodeableReference(CareTeam,Practitioner,PractitionerRole,RelatedPerson,Patient,Organization))

Element NutritionOrder.performer has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.performer has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.outsideFoodAllowed (new:boolean)

Element NutritionOrder.outsideFoodAllowed has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.outsideFoodAllowed has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.subject additional types from child elements (display, identifier, reference, type)

Element NutritionOrder.subject is mapped to FHIR R4 element NutritionOrder.patient as SourceIsBroaderThanTarget. The mappings for NutritionOrder.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element NutritionOrder.subject with unmapped reference targets: Group.

R5: NutritionOrder.oralDiet.schedule.timing (new:Timing)

Element NutritionOrder.oralDiet.schedule.timing has a context of NutritionOrder.oralDiet.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.oralDiet.schedule.timing has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.oralDiet.schedule.asNeeded (new:boolean)

Element NutritionOrder.oralDiet.schedule.asNeeded has a context of NutritionOrder.oralDiet.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.oralDiet.schedule.asNeeded has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.oralDiet.schedule.asNeededFor (new:CodeableConcept)

Element NutritionOrder.oralDiet.schedule.asNeededFor has a context of NutritionOrder.oralDiet.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.oralDiet.schedule.asNeededFor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supplement.type additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/NutritionProduct)) additional types from child elements (reference)

Element NutritionOrder.supplement.type is mapped to FHIR R4 element NutritionOrder.supplement.type as SourceIsBroaderThanTarget. The mappings for NutritionOrder.supplement.type do not cover the following types: CodeableReference. The mappings for NutritionOrder.supplement.type do not cover the following types based on type expansion: reference.

R5: NutritionOrder.supplement.schedule.timing (new:Timing)

Element NutritionOrder.supplement.schedule.timing has a context of NutritionOrder.supplement.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supplement.schedule.timing has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supplement.schedule.asNeeded (new:boolean)

Element NutritionOrder.supplement.schedule.asNeeded has a context of NutritionOrder.supplement.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supplement.schedule.asNeeded has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supplement.schedule.asNeededFor (new:CodeableConcept)

Element NutritionOrder.supplement.schedule.asNeededFor has a context of NutritionOrder.supplement.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supplement.schedule.asNeededFor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.enteralFormula.deliveryDevice (new:CodeableReference(DeviceDefinition))

Element NutritionOrder.enteralFormula.deliveryDevice has a context of NutritionOrder.enteralFormula based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.enteralFormula.deliveryDevice has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.enteralFormula.additive.quantity (new:Quantity[SimpleQuantity])

Element NutritionOrder.enteralFormula.additive.quantity has a context of NutritionOrder.enteralFormula based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.enteralFormula.additive.quantity has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.enteralFormula.baseFormulaType additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/NutritionProduct)) additional types from child elements (reference)

Element NutritionOrder.enteralFormula.baseFormulaType is mapped to FHIR R4 element NutritionOrder.enteralFormula.baseFormulaType as SourceIsBroaderThanTarget. The mappings for NutritionOrder.enteralFormula.baseFormulaType do not cover the following types: CodeableReference. The mappings for NutritionOrder.enteralFormula.baseFormulaType do not cover the following types based on type expansion: reference.

R5: NutritionOrder.enteralFormula.additive.type additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/NutritionProduct)) additional types from child elements (reference)

Element NutritionOrder.enteralFormula.additive.type is mapped to FHIR R4 element NutritionOrder.enteralFormula.additiveType as SourceIsBroaderThanTarget. The mappings for NutritionOrder.enteralFormula.additive.type do not cover the following types: CodeableReference. The mappings for NutritionOrder.enteralFormula.additive.type do not cover the following types based on type expansion: reference.

R5: NutritionOrder.enteralFormula.administration.schedule.timing (new:Timing)

Element NutritionOrder.enteralFormula.administration.schedule.timing has a context of NutritionOrder.enteralFormula.administration.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.enteralFormula.administration.schedule.timing has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.enteralFormula.administration.schedule.asNeeded (new:boolean)

Element NutritionOrder.enteralFormula.administration.schedule.asNeeded has a context of NutritionOrder.enteralFormula.administration.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.enteralFormula.administration.schedule.asNeeded has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.enteralFormula.administration.schedule.asNeededFor (new:CodeableConcept)

Element NutritionOrder.enteralFormula.administration.schedule.asNeededFor has a context of NutritionOrder.enteralFormula.administration.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.enteralFormula.administration.schedule.asNeededFor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to a patient/resident.

Referenced by an Order Request (workflow).

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).

The codes SHOULD be taken from CommonLanguages
(preferred to http://hl7.org/fhir/ValueSet/languages|4.0.1)

A human language.

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

R5: NutritionOrder.basedOn (new:Reference(CarePlan,NutritionOrder,ServiceRequest))

Element NutritionOrder.basedOn has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.basedOn has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.groupIdentifier (new:Identifier)

Element NutritionOrder.groupIdentifier has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.groupIdentifier has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.priority (new:code)

Element NutritionOrder.priority has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.priority has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supportingInformation (new:Reference(Resource))

Element NutritionOrder.supportingInformation has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supportingInformation has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.performer (new:CodeableReference(CareTeam,Practitioner,PractitionerRole,RelatedPerson,Patient,Organization))

Element NutritionOrder.performer has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.performer has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.outsideFoodAllowed (new:boolean)

Element NutritionOrder.outsideFoodAllowed has a context of NutritionOrder based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.outsideFoodAllowed has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

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 manageable, 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifiers assigned to this order by the order sender or by the order receiver.

The Identifier.type element can be to indicate filler vs. placer if needed. This is explained in further detail here.

The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this NutritionOrder.

Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this NutritionOrder.

This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.

The URL pointing to a protocol, guideline, orderset or other definition that is adhered to in whole or in part by this NutritionOrder.

The workflow status of the nutrition order/request.

Typically the system placing the order sets the status to "requested". Thereafter, the order is maintained by the receiver that updates the status as the request is handled. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Codes identifying the lifecycle stage of the nutrition order.

Indicates the level of authority/intentionality associated with the NutrionOrder and where the request fits into the workflow chain.

When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.

Codes indicating the degree of authority/intentionality associated with a nutrition order.

Proposals/recommendations, plans and orders all use the same structure and can exist in the same fulfillment chain.

The person (patient) who needs the nutrition order for an oral diet, nutritional supplement and/or enteral or formula feeding.

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

An Extension

R5: NutritionOrder.subject additional types from child elements (display, identifier, reference, type)

Element NutritionOrder.subject is mapped to FHIR R4 element NutritionOrder.patient as SourceIsBroaderThanTarget. The mappings for NutritionOrder.subject do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension alternate-reference has been mapped as the representation of FHIR R5 element NutritionOrder.subject with unmapped reference targets: Group.

A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.

The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Unless not suitable, these codes SHALL be taken from ResourceType
(extensible to http://hl7.org/fhir/ValueSet/resource-types|4.0.1)

Aa resource (or, for logical models, the URI of the logical model).

An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Plain text narrative that identifies the resource in addition to the resource reference.

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

An encounter that provides additional information about the healthcare context in which this request is made.

The date and time that this nutrition order was requested.

The practitioner that holds legal responsibility for ordering the diet, nutritional supplement, or formula feedings.

A link to a record of allergies or intolerances which should be included in the nutrition order.

Information on a patient's food allergies and intolerances to inform healthcare personnel about the type of foods that the patient shouldn't receive or consume.

This modifier is used to convey order-specific modifiers about the type of food that should be given. These can be derived from patient allergies, intolerances, or preferences such as Halal, Vegan or Kosher. This modifier applies to the entire nutrition order inclusive of the oral diet, nutritional supplements and enteral formula feedings.

Information on a patient's food preferences that inform healthcare personnel about the food that the patient should receive or consume.

Medical, cultural or ethical food preferences to help with catering requirements.

This modifier is used to convey Order-specific modifier about the type of oral food or oral fluids that should not be given. These can be derived from patient allergies, intolerances, or preferences such as No Red Meat, No Soy or No Wheat or Gluten-Free. While it should not be necessary to repeat allergy or intolerance information captured in the referenced AllergyIntolerance resource in the excludeFoodModifier, this element may be used to convey additional specificity related to foods that should be eliminated from the patient’s diet for any reason. This modifier applies to the entire nutrition order inclusive of the oral diet, nutritional supplements and enteral formula feedings.

Information on a patient's food allergies, intolerances and preferences to inform healthcare personnel about the type of foods that the patient shouldn't receive or consume.

Codes used to indicate the type of food that should NOT be given to the patient.

Diet given orally in contrast to enteral (tube) feeding.

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The kind of diet or dietary restriction such as fiber restricted diet or diabetic diet.

Codes used to indicate the type of diet being ordered for a patient.

The time period and frequency at which the diet should be given. The diet should be given for the combination of all schedules if more than one schedule is present.

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

An Extension

R5: NutritionOrder.oralDiet.schedule.timing (new:Timing)

Element NutritionOrder.oralDiet.schedule.timing has a context of NutritionOrder.oralDiet.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.oralDiet.schedule.timing has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.oralDiet.schedule.asNeeded (new:boolean)

Element NutritionOrder.oralDiet.schedule.asNeeded has a context of NutritionOrder.oralDiet.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.oralDiet.schedule.asNeeded has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.oralDiet.schedule.asNeededFor (new:CodeableConcept)

Element NutritionOrder.oralDiet.schedule.asNeededFor has a context of NutritionOrder.oralDiet.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.oralDiet.schedule.asNeededFor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifies specific times when the event occurs.

In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.

A set of rules that describe when the event is scheduled.

Many timing schedules are determined by regular repetitions.

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.

Either a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.

A total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values.

If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.

Repetitions may be limited by end time or total occurrences.

If present, indicates that the count is a range - so to perform the action between [count] and [countMax] times.

How long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration.

For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

Some activities are not instantaneous and need to be maintained for a period of time.

If present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length.

For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

Some activities are not instantaneous and need to be maintained for a period of time.

The units of time for the duration, in UCUM units.

A unit of time (units from UCUM).

The number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency.

If present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range.

Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length.

If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days.

The units of time for the period in UCUM units.

A unit of time (units from UCUM).

If one or more days of week is provided, then the action happens only on the specified day(s).

If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.

Specified time of day for action to take place.

When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.

An approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur.

When more than one event is listed, the event is tied to the union of the specified events.

The codes SHALL be taken from EventTiming
(required to http://hl7.org/fhir/ValueSet/event-timing|4.0.1)

Real world event relating to the schedule.

Timings are frequently determined by occurrences such as waking, eating and sleep.

The number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event.

A code for the timing schedule (or just text in code.text). Some codes such as BID are ubiquitous, but many institutions define their own additional codes. If a code is provided, the code is understood to be a complete statement of whatever is specified in the structured timing data, and either the code or the data may be used to interpret the Timing, with the exception that .repeat.bounds still applies over the code (and is not contained in the code).

BID etc. are defined as 'at institutionally specified times'. For example, an institution may choose that BID is "always at 7am and 6pm". If it is inappropriate for this choice to be made, the code BID should not be used. Instead, a distinct organization-specific code should be used in place of the HL7-defined BID code and/or a structured representation should be used (in this case, specifying the two event times).

Code for a known / defined timing pattern.

Class that defines the quantity and type of nutrient modifications (for example carbohydrate, fiber or sodium) required for the oral diet.

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The nutrient that is being modified such as carbohydrate or sodium.

Codes for types of nutrients that are being modified such as carbohydrate or sodium.

The quantity of the specified nutrient to include in diet.

Class that describes any texture modifications required for the patient to safely consume various types of solid foods.

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Any texture modifications (for solid foods) that should be made, e.g. easy to chew, chopped, ground, and pureed.

Coupled with the foodType (Meat).

Codes for food consistency types or texture modifications to apply to foods.

The food type(s) (e.g. meats, all foods) that the texture modification applies to. This could be all foods types.

Coupled with the texture.modifier; could be (All Foods).

Codes for types of foods that are texture-modified.

The required consistency (e.g. honey-thick, nectar-thick, thin, thickened.) of liquids or fluids served to the patient.

Codes used to represent the consistency of fluids and liquids provided to the patient.

Free text or additional instructions or information pertaining to the oral diet.

Free text dosage instructions can be used for cases where the instructions are too complex to code.

Oral nutritional products given in order to add further nutritional value to the patient's diet.

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

The kind of nutritional supplement product required such as a high protein or pediatric clear liquid supplement.

Codes for nutritional supplements to be provided to the patient.

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

An Extension

R5: NutritionOrder.supplement.type additional types (CodeableReference(http://hl7.org/fhir/StructureDefinition/NutritionProduct)) additional types from child elements (reference)

Element NutritionOrder.supplement.type is mapped to FHIR R4 element NutritionOrder.supplement.type as SourceIsBroaderThanTarget. The mappings for NutritionOrder.supplement.type do not cover the following types: CodeableReference. The mappings for NutritionOrder.supplement.type do not cover the following types based on type expansion: reference.

A reference to a code defined by a terminology system.

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

The product or brand name of the nutritional supplement such as "Acme Protein Shake".

The time period and frequency at which the supplement(s) should be given. The supplement should be given for the combination of all schedules if more than one schedule is present.

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

An Extension

R5: NutritionOrder.supplement.schedule.timing (new:Timing)

Element NutritionOrder.supplement.schedule.timing has a context of NutritionOrder.supplement.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supplement.schedule.timing has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supplement.schedule.asNeeded (new:boolean)

Element NutritionOrder.supplement.schedule.asNeeded has a context of NutritionOrder.supplement.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supplement.schedule.asNeeded has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

R5: NutritionOrder.supplement.schedule.asNeededFor (new:CodeableConcept)

Element NutritionOrder.supplement.schedule.asNeededFor has a context of NutritionOrder.supplement.schedule based on following the parent source element upwards and mapping to NutritionOrder. Element NutritionOrder.supplement.schedule.asNeededFor has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Identifies specific times when the event occurs.

In a Medication Administration Record, for instance, you need to take a general specification, and turn it into a precise specification.

A set of rules that describe when the event is scheduled.

Many timing schedules are determined by regular repetitions.

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.

Either a duration for the length of the timing schedule, a range of possible length, or outer bounds for start and/or end limits of the timing schedule.

A total count of the desired number of repetitions across the duration of the entire timing specification. If countMax is present, this element indicates the lower bound of the allowed range of count values.

If you have both bounds and count, then this should be understood as within the bounds period, until count times happens.

Repetitions may be limited by end time or total occurrences.

If present, indicates that the count is a range - so to perform the action between [count] and [countMax] times.

How long this thing happens for when it happens. If durationMax is present, this element indicates the lower bound of the allowed range of the duration.

For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

Some activities are not instantaneous and need to be maintained for a period of time.

If present, indicates that the duration is a range - so to perform the action between [duration] and [durationMax] time length.

For some events the duration is part of the definition of the event (e.g. IV infusions, where the duration is implicit in the specified quantity and rate). For others, it's part of the timing specification (e.g. exercise).

Some activities are not instantaneous and need to be maintained for a period of time.

The units of time for the duration, in UCUM units.

A unit of time (units from UCUM).

The number of times to repeat the action within the specified period. If frequencyMax is present, this element indicates the lower bound of the allowed range of the frequency.

If present, indicates that the frequency is a range - so to repeat between [frequency] and [frequencyMax] times within the period or period range.

Indicates the duration of time over which repetitions are to occur; e.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period. If periodMax is present, this element indicates the lower bound of the allowed range of the period length.

If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days.

The units of time for the period in UCUM units.

A unit of time (units from UCUM).

If one or more days of week is provided, then the action happens only on the specified day(s).

If no days are specified, the action is assumed to happen every day as otherwise specified. The elements frequency and period cannot be used as well as dayOfWeek.

Specified time of day for action to take place.

When time of day is specified, it is inferred that the action happens every day (as filtered by dayofWeek) on the specified times. The elements when, frequency and period cannot be used as well as timeOfDay.

An approximate time period during the day, potentially linked to an event of daily living that indicates when the action should occur.

When more than one event is listed, the event is tied to the union of the specified events.

The codes SHALL be taken from EventTiming
(required to http://hl7.org/fhir/ValueSet/event-timing|4.0.1)

Real world event relating to the schedule.

Timings are frequently determined by occurrences such as waking, eating and sleep.

The number of minutes from the event. If the event code does not indicate whether the minutes is before or after the event, then the offset is assumed to be after the event.