TRV-2026-1886Version 1 · Certified

Written 2026-10-19 10:41:43 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1886
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-19T10:41:43.156112Z
status: published
lens: g_space
sector: health
headline: Blinded professional ratings of artificial intelligence-generated and dietitian-designed meal plans
dek: Objectives: Artificial intelligence-assisted systems increasingly produce personalized meal plans, but their value depends on whether clinicians judge those plans credible and usable. We evaluated complete plans from a constrained artificial intelligence-assisted pipeline under blinded professional review.
Methods: In a cross-sectional exploratory web study, 54 eligible anonymous evaluator records from Brazilian dietitians contributed 130 evaluations of five matched plan pairs, with one pipeline-generated and on…
gain_title: In blinded review by Brazilian dietitians, meal plans from a constrained AI-assisted pipeline scored higher on average than matched dietitian-designed plans, mainly on nutritional adequacy and technical quality.
problem_title: (none)
trace_subject: (none)
gain_reading: In blinded review by Brazilian dietitians, meal plans from a constrained AI-assisted pipeline scored higher on average than matched dietitian-designed plans, mainly on nutritional adequacy and technical quality.
gain_evidence: 31 favored pipeline-generated plans, 6 favored dietitian-designed plans
problem_reading: (none)
problem_evidence: (none)
quick_read: Researchers asked Brazilian dietitians to rate meal plans without knowing whether each came from an AI-assisted pipeline or a dietitian. Five personas each had one pipeline-generated plan and one dietitian-designed plan, and 54 eligible evaluator records produced 130 evaluations across nine rated items.

The result suggests AI-assisted drafting could be credible to clinicians, supporting a structured first-draft workflow where dietitians edit the output. The study was exploratory and rated plans rather than measuring patient outcomes, so it does not show that the plans improve health or that clinicians would adopt them in practice.
limitation: The study was exploratory, and the pair-level pattern was only descriptive because evaluator records overlapped across pairs; it rated plans and did not measure patient outcomes.
tag: Evidence-backed gain
key_points: The study was a cross-sectional exploratory web study with anonymous evaluator records from Brazilian dietitians. | Mean overall ratings were 3.67 for pipeline plans and 3.11 for dietitian-designed plans, with an effect size of 0.86. | Domain differences favored the pipeline by 0.76 for nutritional adequacy, 0.69 for technical quality and 0.21 for practical applicability. | In an optional pairwise task, 32 of 42 eligible choices picked the pipeline-generated plan as more appropriate.
rundown: The design covered five matched plan pairs, one pipeline-generated and one dietitian-designed per persona. Evaluators rated nine items across three domains, and the overall score required all nine items, leaving 124 evaluations with scores.

Among 38 evaluator records with complete scores for both origins, 31 favored the pipeline plans, 6 favored dietitian plans and 1 was tied. Pipeline plans scored higher in all five persona pairs, though the authors call this descriptive because evaluator records overlapped across pairs.

The authors conclude the findings support prospective evaluation of a structured first-draft workflow, with required clinician edits and patient-relevant outcomes as endpoints.
sources:
- peer_reviewed | Nutrition | https://doi.org/10.1016/j.nut.2026.113428 | 2026-10-16
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
eb385b4a1ba57bca02917079d0a87b723fb8d12668341c00f98c036d41c40472
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1886 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.