> 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/5-information-models-and-terminology-binding/5.4-hl7-fhir-and-ncpt/5.4.1-fhir-resources-for-nutrition-assessment-and-reassessment.md).
# FHIR Resources for Nutrition Assessment and Reassessment
> Nutrition Assessment involves collecting and analyzing data to identify nutrition-related issues.
## Nutrition Assessment Data and Associated FHIR Resources
Several FHIR resources can represent different aspects of the assessment:
| Types of data collected | Purpose | Example | FHIR Resource |
| ----------------------------------------------- | -------------------------------------------------------- | ----------------------------- | --------------------------------------------------------------------- |
| Food- and nutrition-related history | Capture dietary habits and intake information | Food diary entries | **Observation NutritionOrderNutritionProduct\*\*\*\*NutritionIntake** |
| Anthropometric measurements | Record physical measurements such as weight, height, BMI | Weight: 70 kg, Height: 170 cm | **Observation** |
| Tests | Document laboratory or diagnostic tests | Blood glucose levels | **Observation** |
| Test results | Record results of tests | Hemoglobin A1c: 5.5% | **Observation** |
| Nutrition-focused physical examination findings | Detailed findings from a nutrition-focused physical exam | Skin condition, hair texture | **Observation\*\*\*\*Condition** |
| Patient history | Capture medical history | Chronic conditions, surgeries | **Observation** |
## Example
{% code overflow="wrap" %}
```json
Nutrition Assessment
[code]
{
"resourceType": "Observation",
"id": "observation-weight",
"status": "final",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/observation-category",
"code": "vital-signs",
"display": "Vital Signs"
}
]
}
],
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "27113001",
"display": "Body weight (observable entity)"
}
],
"text": "Body Weight"
},
"subject": {
"reference": "Patient/example"
},
"valueQuantity": {
"value": 70,
"unit": "kg",
"system": "http://unitsofmeasure.org",
"code": "kg"
}
}
[/code]
```
{% endcode %}
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/5-information-models-and-terminology-binding/5.4-hl7-fhir-and-ncpt/5.4.1-fhir-resources-for-nutrition-assessment-and-reassessment.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.