documentation:next_cdm:multi_level_linkage
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
documentation:next_cdm:multi_level_linkage [2016/01/07 13:51] clairblacketer |
documentation:next_cdm:multi_level_linkage [2016/01/07 13:59] clairblacketer |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| Patient_id -> Date of Meal -> Food item consumed -> Grams of Fat in Food | Patient_id -> Date of Meal -> Food item consumed -> Grams of Fat in Food | ||
| - | This {{:documentation:next_cdm:nhanes_dr1iff_g_example.xlsx|file}} was taken straight from the NHANES website and shows how the dietary data are constructed. | + | This {{:documentation:next_cdm:nhanes_dr1iff_g_example.xlsx|file}} was taken straight from the NHANES website and shows how the dietary data are constructed. Using the current CDM and assuming they would be routed to the OBSERVATION table 'Respondent sequence number' is PERSON_ID and then 'USDA food code' could be mapped to OBSERVATION_CONCEPT_ID (this also assumes that the food codes would be added to the vocabulary. If not, they food code would go in OBSERVATION_SOURCE_VALUE and OBSERVATION_CONCEPT_ID would be mapped to 0). The problem with this is then I would only be able to see what foods a person ate on a day but I would not know anything about those foods (grams, calories, protein, etc.) |
documentation/next_cdm/multi_level_linkage.txt ยท Last modified: 2017/03/01 17:06 by clairblacketer
Page Tools
