> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/implementation-guides/ncpt-implementation-guide/4-snomed-ct-content/4.4-nutrition-monitoring-and-evaluation.md).
# Nutrition Monitoring and Evaluation
## Content and Modeling
* **Main hierarchies**
* Terminology for **Nutrition Monitoring and Evaluation** is predominantly but not exclusively from the Observable Entity hierarchy, but also from the Clinical Finding hierarchy, which encompass questions, outcomes, and indicators relevant to evaluating nutrition interventions and goals.
* The content is modeled in alignment with these previously described hierarchies
* **Templates**
* As part of the content development process, authoring templates were created to support future content additions and quality assurance of existing and new content in this area. The templates described in the assessment and reassessment section are also applicable to monitoring and evaluation. [Nutritional intake (observable entity) - v3.0](https://conf.spaces.snomed.org/wiki/spaces/SCTEMPLATES/pages/134001915/Nutritional+intake+observable+entity+-+v3.0)
## Examples
This will also include concepts from Nutrition Assessment and Reassessment section with some additional examples given here. With the exception of historical assessment content, Nutrition Assessment and Reassessment concepts are modified to achieve nutrition care goals and track nutrition care progress in the Nutrition Monitoring and Evaluation step of the NCP.
#### 390802008 |Goal achieved (finding)|
#### 870605008 |Target weight for length z-score (observable entity)|
Provide Feedback
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.snomed.org/implementation-guides/ncpt-implementation-guide/4-snomed-ct-content/4.4-nutrition-monitoring-and-evaluation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
