Skip to end of metadata
Go to start of metadata


Becky GradlAcademy of Nutrition and Dietetics
Margaret DittloffJunum
Della DunbarDM&A
Sue Kent
  • Brainstormed on what elements would be needed to build a NutritionProduct resource
    • Texture classification (what needs to be put in for iddsi: as this will be required in the future on labels
    • Allergens: is this a value set, another resource, such as substance? AllergyIntolerance is a resource related to the patient, but we need to know what is in the food that could cause an allergy
    • Nutrients (carbohydrates, protein, vitamins, minerals, etc.)
    • Ingredients
    • Manufacturer (may not be available for everything)--make it optional
    • GS1 codes
    • On Supplements, HCPCS (healthcare common procedure coding system) - used for medicare; HCPS are across supplements; enteral:
      • On MedicationKnowledge resource, there is a MedicineClassification with type and classification; this would be similar to the HCPCS
    • Serving size
    • Menu planning attributes (such as food pyramid classification)
    • Dates (for use by, shelf life, etc.)
    • Source (patient's home, restaurant, etc.), lot number, batch number (lot and/or batch is in the bar codes)
    • External source ID (for USDA database or other food database)
  • In the future, NutritionOrder may want to point to the NutritionProduct resource, especially if NutritionProduct is includes extra details about supplements, such as the GS1 data
  • No labels