Category 1 Lead Benchmark Context
HMI normalizes Category 1 lead benchmarks into ppb so FDA action levels, EU maximum levels, Prop 65 exposure screens, and observed occurrence data can be compared on one concentration scale. The conversion makes the numbers comparable; it does not make them the same kind of value.
| Value class | ppb view | What it means |
|---|---|---|
| FDA action/guidance level | Stored directly in ppb when established | U.S. regulatory context; often nonbinding guidance that FDA may consider in enforcement |
| EU maximum level | Converted from mg/kg to ppb | Binding EU market-entry ceiling where the product scope matches |
| Prop 65 lead MADL screen | 500 ÷ grams/day | Exposure-based warning screen derived from 0.5 ug/day lead MADL, not a food-category concentration limit |
| Occurrence data | Stored in ppb | What has actually been measured in products or source datasets |
| HMTc standards use | ppb-normalized but separately typed | Standards input/context only after scope, basis, and evidence fitness review |
Why this helps HMTc standards
The ppb-normalized view lets HMTc apply a clean standards workflow:
- Regulatory cap check: a proposed HMTc value should not exceed the most protective applicable finalized regulatory ceiling for the same product, metal, and basis.
- Feasibility check: occurrence medians, P90s, P95s, and maxima show whether a stricter value is realistically achievable.
- Scope firewall: formula, dry cereal, fruit puree, juice, and snacks cannot silently borrow each other’s regulatory values.
- Basis matching: powder, liquid, as-sold, ready-to-eat, prepared-for-feeding, and serving-based exposure values stay labelled.
- Public claim control: regulatory values, exposure screens, occurrence values, and HMTc thresholds remain separate data objects.
Why this helps the broader community
The public takeaway is simple: legal is not the same as low. A product can be under FDA or EU lead values and still look elevated compared with observed category medians or a Prop 65 serving-based exposure screen. The reverse can also happen for tiny serving sizes, where a Prop 65 ppb equivalent may look high because daily intake is small.
This page therefore shows all lead reference points in ppb, while preserving what each number actually does.
Category 1 lead crosswalk
| Product row | Current FDA lead ppb view | EU lead ppb view | Prop 65 ppb-equivalent screen | Standards interpretation |
|---|---|---|---|---|
| Infant formula, powder (non-soy) | Not established | 20 ppb | 5 ppb at 100 g/day powder assumption | No FDA formula-specific lead action level; do not borrow processed-baby-food values. |
| Infant formula, powder (soy-based) | Not established | 20 ppb | 5 ppb at 100 g/day powder assumption | Same legal structure as non-soy powder, but occurrence review should stay soy-specific. |
| Infant formula, RTF liquid (non-soy) | Not established | 10 ppb | 0.625 ppb at 800 g/day liquid assumption | Keep liquid/prepared occurrence data separate from powder data. |
| Infant formula, RTF liquid (soy-based) | Not established | 10 ppb | 0.625 ppb at 800 g/day liquid assumption | Formula-specific exposure model required before standards use. |
| Baby cereals and grain products, dry (non-rice) | 20 ppb | 20 ppb | 33.3 ppb at 15 g/day | FDA and EU align at 20 ppb for lead; occurrence data decide whether HMTc can go lower. |
| Baby cereals and grain products, dry (rice-based) | 20 ppb | 20 ppb | 33.3 ppb at 15 g/day | Lead limit is the same as non-rice cereal; rice still drives iAs/Cd/Pb occurrence review. |
| Fruit purees | 10 ppb | 20 ppb | 4.5 ppb at 110 g/day | FDA 10 ppb is the regulatory cap/context; Prop 65 shows why serving size matters. |
| Non-root vegetable purees | 10 ppb | 20 ppb | 4.5 ppb at 110 g/day | Non-root vegetables should not inherit the FDA 20 ppb root-vegetable value. |
| Root-vegetable purees | 20 ppb if single-ingredient carrot or sweet potato | 20 ppb | 4.5 ppb at 110 g/day | FDA 20 ppb applies only where the root-vegetable scope matches; mixtures can route to 10 ppb. |
| Meat and poultry purees | 10 ppb | 20 ppb | 4.5 ppb at 110 g/day | Use FDA 10 ppb as cap/context, then compare with measured meat/poultry occurrence. |
| Fish-containing baby foods | 10 ppb when covered as a mixture | 20 ppb | 4.5 ppb at 110 g/day | Scope review needed for fish products; lead is not the whole fish-food risk story. |
| Mixed meals, non-rice | 10 ppb | 20 ppb | 4.5 ppb at 110 g/day; 2.9 ppb at 170 g/day toddler meal | Keep rice status and ingredient drivers separate. |
| Mixed meals, rice-containing | 10 ppb | 20 ppb | 4.5 ppb at 110 g/day; 2.9 ppb at 170 g/day toddler meal | Do not substitute dry-infant-cereal lead values for rice-containing meals. |
| Fruit juice, not canned | 50 ppb current Juice HACCP context | 20 ppb if infant/young-child-labelled drink | 4.2 ppb at 120 g/day | Track 10/20 ppb FDA juice values as draft-only until finalized. |
| Teething and snacks, non-rice | Not established | 20 ppb if processed cereal-based infant/young-child food | 71.4 ppb at 7 g/day | FDA snack gap remains visible; do not borrow dry-cereal action levels. |
| Teething and snacks, rice-based | Not established | 20 ppb if processed cereal-based infant/young-child food | 71.4 ppb at 7 g/day | Rice snacks remain a priority, but infant-rice-cereal values do not automatically apply. |
Formula
Prop 65 conversion:
lead ppb equivalent = 500 ÷ grams consumed per dayThe numerator is 500 ng/day, equal to OEHHA’s 0.5 ug/day lead MADL. Since 1 ppb equals 1 ng/g, dividing 500 ng/day by grams/day gives the concentration in ppb that would reach the MADL under that intake assumption.
Formula rows use labelled illustrative intake assumptions because infant formula exposure depends on preparation, age, body weight, and daily volume. Those assumptions are not HMTc standards and should be replaced by an approved formula-specific exposure model before threshold decisions.
Sources
- fda-ctz-Pb-babyfood-2025
- fda2004-juice-haccp-lead
- fda2022-draft-lead-juice
- eu2023-915-lead-infant-young-child-foods
- oehha-lead-prop65
- ecfr-21cfr10112-serving-sizes
The structured ppb-normalized lead benchmark values that power this page are maintained in the staff Standards Workbench and applied to per-product pages by the lead-benchmark-context generator (tools/evidence/apply-lead-benchmark-context.mjs).
Who this page is for
Pending. The brand-legal, retailer-compliance, HMTc-internal, and regulator audiences are listed in OPERATING.md Part 2; this section will frame what each is looking for on this page.
Methodology
Pending. This section will state the speciation, basis-preservation, row-fit, and pooling rules from CLAUDE.md Part 6 that govern downstream sections of this page.
Literature Evidence Summary
Pending: regenerated by tools/evidence/apply-product-hmtc-evidence-summaries.mjs once sources route and the pooling engine emits aggregate rows for this product category.
Source Evidence Inventory
Hand-curated section. Populated by the synthesis pass as sources contribute.
Broad Product Context: Author-Scope Index
Pending: regenerated by tools/evidence/apply-product-broad-context.mjs once broad-scope sources route to this page.
Federal/Regulatory Limits vs Field Findings
Pending: regenerated by tools/apply-product-crosswalk-sections.mjs once applicable_regulations are identified and field-finding evidence is pooled.
Levers to reduce contamination
Cat 4 (produce, nuts, seeds) regulatory enforcement intersects two domains: heavy-metal contamination (the focus of this row) and microbial contamination (FDA recall notices for E. coli/Salmonella/Listeria in fresh produce, a separate concern). FDA Total Diet Study and Pesticide Data Program surveillance reports establish the heavy-metal occurrence baseline (FDA 2022). State-level Cd-in-leafy-greens enforcement has been active in California under Prop 65; the related Mateel Environmental settlement framework has shaped compliance practice. Per CLAUDE.md Part 12, individual brand recall actions are not enumerated here.
How standards math uses this page
The percentile arithmetic that informs HMTc thresholds for this product category lives on the staff Standards Workbench (data/workbench/standards/<this-slug>.md). This public page reports literature evidence; the workbench applies the methodology in CLAUDE.md Part 19. The gap between literature evidence and HMTc thresholds is named honestly on the workbench, not hidden.
Historical recalls and enforcement
Cat 4 (produce, nuts, seeds) regulatory enforcement intersects two domains: heavy-metal contamination (the focus of this row) and microbial contamination (FDA recall notices for E. coli/Salmonella/Listeria in fresh produce, a separate concern). FDA Total Diet Study and Pesticide Data Program surveillance reports establish the heavy-metal occurrence baseline (FDA 2022). State-level Cd-in-leafy-greens enforcement has been active in California under Prop 65; the related Mateel Environmental settlement framework has shaped compliance practice. Per CLAUDE.md Part 12, individual brand recall actions are not enumerated here.
Page history
The five most recent substantive edits to this page. The full version history lives in git; when DOI minting comes online (see schema docs), each entry below will also link to a version-pinned DataCite DOI.
| Commit | Date | Description |
|---|---|---|
| b0f3d38 | 2026-06-12 | batch | corpus rescreen b04 old terminal skips |