Description
Preserve an explicit fortified-nutrient label transcription and reporting basis.
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.
Preserve an explicit fortified-nutrient label transcription and reporting basis.
When to use this tool
Use Fortification Nutrient Label Basis Pair when you already have productId, nutrientLabelText, basisText and need to preserve an explicit fortified-nutrient label transcription and reporting basis.
How to use the tool and how it works
- Enter productId, nutrientLabelText, basisText. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter productId, nutrientLabelText, basisText using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| productId | Product Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| nutrientLabelText | Nutrient Label Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| basisText | Basis Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"productId": "P17",
"nutrientLabelText": "8 mg",
"basisText": "per 100 g"
},
"output": {
"token": "[\"P17\",\"8 mg\",\"per 100 g\"]"
}
}Limitations and assumptions
- The result records supplied values without assessing adequacy or regulation. 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
- Nutrition Diary Entry Time Ambiguity Label
Preserve a supplied nutrition-diary time transcription and explicit ambiguity note.
- Dietary Recall Meal Code
Encode explicitly reported dietary-recall meal and time wording.