Get the food information from the server
Query parameters
Exact catalogue row. Prefer this when the caller already has an rxfood_id from search (shared names have multiple nutrition_source siblings).
When resolving by food_name, only return a DBFood whose nutrition_source or primary_data_origin_code matches (e.g. cnf).
Response
successful operation
Example response
{
"nutrient_overrides": {
"aa_patient": {
"ontology": {
"id": 42,
"levels": [
"food"
]
}
},
"bb_reviewer": {
"ontology": {
"id": 42,
"levels": [
"food"
]
}
},
"cc_external": {
"ontology": {
"id": 42,
"levels": [
"food"
]
}
},
"dd_estimate": {
"ontology": {
"id": 42,
"levels": [
"food"
]
}
},
"ee_validation": {
"ontology": {
"id": 42,
"levels": [
"food"
]
}
}
}
}Changes
Changed in 2 of the 15 revisions of this API.8
- ○
added the new optional
queryrequest parameternutrition_sourcenew-optional-request-parameter
- ○
added the new optional
queryrequest parameterrxfood_idnew-optional-request-parameter
- ○
the
queryrequest parameterfood_namebecame optionalrequest-parameter-became-optional
- ○
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○