Description
Encode explicitly reported dietary-recall meal and time wording.
Dietary arithmetic depends on as-purchased versus edible mass, per-serving versus per-100-gram bases, measured versus trace states and recall periods. A recorded allergen list is not a verified allergen-free declaration. Portion counts, label intervals and mass differences use supplied assumptions rather than establishing actual intake or nutritional suitability.
Encode explicitly reported dietary-recall meal and time wording.
When to use this tool
Use Dietary Recall Meal Code when you already have recallId, mealCode, reportedTime and need to encode explicitly reported dietary-recall meal and time wording.
How to use the tool and how it works
- Enter recallId, mealCode, reportedTime. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read label. Use the output convention below.
Enter recallId, mealCode, reportedTime using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in label. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recallId | Recall Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| mealCode | Meal Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| reportedTime | Reported Time | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| label | Label | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recallId": "R17",
"mealCode": "breakfast",
"reportedTime": "08:00"
},
"output": {
"label": "[\"R17\",\"breakfast\",\"08:00\"]"
}
}Limitations and assumptions
- The result records supplied values without inferring meal composition or adequacy. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Check original food labels, composition sources, ingredient/allergen information and dietary records before combining amounts. Use a complete appropriately interpreted dietary assessment when requirements or suitable intake matter; local scaling and source labels do not make those judgments.
References
Similar or alternative tools
- Fortification Nutrient Label Basis Pair
Preserve an explicit fortified-nutrient label transcription and reporting basis.
- Nutrition Diary Entry Time Ambiguity Label
Preserve a supplied nutrition-diary time transcription and explicit ambiguity note.