User Tools

Site Tools


documentation:next_cdm:multi_level_linkage

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
documentation:next_cdm:multi_level_linkage [2017/03/01 17:03]
clairblacketer
documentation:next_cdm:multi_level_linkage [2017/03/01 17:06] (current)
clairblacketer
Line 5: Line 5:
 **Proposal** **Proposal**
  
-Add table similar to the DRUG_STRENGTH table that would contain information about foods such as calories, fat, and sugar content. The specific use case I am thinking of is related to the [[http://​www.cdc.gov/​nchs/​nhanes.htm|NHANES]] dataset; a U.S. based survey that combines both health and nutrition information. I cannot currently store the nutrition information effectively because it would require two levels of association in any of the event tables. For example:+Add an optional ​table similar to the DRUG_STRENGTH table that would contain information about foods such as calories, fat, and sugar content. The specific use case I am thinking of is related to the [[http://​www.cdc.gov/​nchs/​nhanes.htm|NHANES]] dataset; a U.S. based survey that combines both health and nutrition information. I cannot currently store the nutrition information effectively because it would require two levels of association in any of the event tables. For example:
  
          ​Patient_id -> Date of Meal -> Food item consumed -> Calories in Food item          ​Patient_id -> Date of Meal -> Food item consumed -> Calories in Food item
Line 12: Line 12:
 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' is mapped to OBSERVATION_CONCEPT_ID (This also assumes that the food codes would be added to the vocabulary. If not, the 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.). ​ 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' is mapped to OBSERVATION_CONCEPT_ID (This also assumes that the food codes would be added to the vocabulary. If not, the 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.). ​
  
-My proposal is that we create ​reference table similar to the DRUG_STRENGTH table to house this information. This would also require the addition of USDA food codes to the vocabulary, as well the addition of food attributes to the vocabulary. ​+My proposal is that we create ​an optional ​reference table similar to the DRUG_STRENGTH table to house this information. This would also require the addition of USDA food codes to the vocabulary, as well the addition of food attributes to the vocabulary. ​
  
 ^Field^Required^Type^Description^ ^Field^Required^Type^Description^
documentation/next_cdm/multi_level_linkage.txt ยท Last modified: 2017/03/01 17:06 by clairblacketer