A Dietary Assessment App for Hospitalized Patients at Nutritional Risk: Development and Evaluation of the MyFood App
Bibliographic record
Abstract
BACKGROUND: Disease-related malnutrition is a common challenge among hospitalized patients. There seems to be a lack of an effective system to follow-up nutritional monitoring and treatment of patients at nutritional risk after risk assessment. We identify a need for a more standardized system to prevent and treat disease-related malnutrition. OBJECTIVE: We aimed to develop a dietary assessment app for tablets for use in a hospital setting and to evaluate the app's ability to measure individual intake of energy, protein, liquid, and food and beverage items among hospitalized patients for two days. We also aimed to measure patients' experiences using the app. METHODS: We have developed the MyFood app, which consists of three modules: 1) collection of information about the patient, 2) dietary assessment function, and 3) evaluation of recorded intake compared to individual needs. We used observations from digital photography of the meals, combined with partial weighing of the meal components, as a reference method to evaluate the app's dietary assessment system for two days. Differences in the intake estimations of energy, protein, liquid, and food and beverage items between MyFood and the photograph method were analyzed on both group and individual level. RESULTS: Thirty-two patients hospitalized at Oslo University Hospital were included in the study. The data collection period ran from March to May 2017. About half of the patients had ≥90% agreement between MyFood and the photograph method for energy, protein, and liquid intake on both recording days. Dinner was the meal with the lowest percent agreement between methods. MyFood overestimated patients' intake of bread and cereals and underestimated fruit consumption. Agreement between methods increased from day 1 to day 2 for bread and cereals, spreads, egg, yogurt, soup, hot dishes, and desserts. Ninety percent of participants reported that MyFood was easy to use, and 97% found the app easy to navigate. CONCLUSIONS: We developed the MyFood app as a tool to monitor dietary intake among hospitalized patients at nutritional risk. The recorded intake of energy, protein, and liquid using MyFood showed good agreement with the photograph method for the majority of participants. The app's ability to estimate intake within food groups was good, except for bread and cereals which were overestimated and fruits which were underestimated. The app was well accepted among study participants and has the potential to be a dietary assessment tool for use among patients in clinical practice.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.010 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".