Skip to main content

Food composition holding register

Source-specific food measurements held for future food-page integration. Inclusion here does not register a new canonical food, generate food mappings, establish a PM-specific dietary requirement or constitute a food recommendation.

Candidate measurements​

Amounts are per 100 g of the specified food, not dry matter. Preparation is part of the observation identity; do not transfer values to other preparations or generic food identities.

Food and preparationSubstanceAmount per 100 gSource studySource record IDBRAIN canonical IDs / integration status
Tilapia, cooked, dry heatBetaine25 mgUSDA Release 2 (2008), printed p. 27NDB 15262Substance: betaine. Food: unassigned; no exact food page identified.
Shrimp, mixed species, cannedBetaine23 mgUSDA Release 2 (2008), printed p. 27NDB 15152Substance: betaine. Existing food: shrimp; preparation-specific observation not yet integrated.
Chicken liver, pan-friedBetaine21 mgUSDA Release 2 (2008), printed p. 15NDB 05661Substance: betaine. Exact food: unassigned. Existing liver is generic and is not an exact identity match.

References​

USDA choline database, Release 2 (2008)​

Patterson KY, Bhagwat SA, Williams JR, Howe JC, Holden JM, Zeisel SH, Dacosta KA, Mar MH. USDA Database for the Choline Content of Common Foods, Release Two. January 2008. Authoritative USDA database and methods (PDF).

The betaine column reports milligrams of betaine per 100 g of food, separately from total choline. Release 2 corrects analytical problems affecting some earlier measurements. Values describe the specified sampled foods, not guaranteed concentrations in every product. The database confidence code concerns total choline and must not be represented as a betaine-specific confidence rating.

Integration safeguards​

  • Preserve the source record ID, substance ID, preparation and citation when later creating or updating a food page.
  • Assign a BRAIN food ID only through the existing canonical registration process; an NDB ID is an external source identifier, not a BRAIN ID.
  • Put the supporting reference on the eventual canonical food page. Keep PM food rows compact.
  • Do not automatically import this holding register into food-source rankings, dietary roll-ups or PM admissions.
  • Retain the source observation and its provenance when promoted; record the destination here rather than silently deleting its history.