The July 23–24 Pharmacy Compounding Advisory Committee materials are more informative than a headline about peptides being “approved” or “banned.” They describe a substance-by-substance evaluation under the 503A compounding framework. Reading the original documents closes part of our earlier coverage gap; it does not justify inventing the committee’s vote totals.
What was on the agenda
The FDA briefing introduction, PDF pages 4–6, identifies seven peptide families: BPC-157, KPV, TB-500, MOTS-c, emideltide (DSIP), Epitalon and Semax. For each it separately discusses free-base and acetate forms. That produces fourteen substance questions, not fourteen independently approved medicines or fourteen separate clinical-trial programs.
The introduction also records withdrawn nominations and says FDA elected to proceed with the evaluations at its discretion. Withdrawal is therefore not evidence that the meeting had no subject to consider. Nor is proceeding with consideration a decision to include a substance on the bulks list.
The documents have different jobs
The briefing’s opening page says the materials seek the advisory committee’s advice and that FDA does not intend to issue its final determination until committee input has been considered and reviews finalized. Its points-to-consider section, PDF pages 6–8, proposes not including the fourteen listed substances. That is the staff position presented for consideration—not evidence of how the committee ultimately voted.
The meeting page explains that advisory recommendations are nonbinding. This review has read the briefing introduction and relevant FDA presentation passages, but has not verified original minutes or a transcript establishing substance-specific vote outcomes. A final agenda listing a vote is not the vote result. That gap stays visible.
Identity is part of the evidence, not an administrative detail
The July 23 FDA slides identify TB-500 as a seven-amino-acid synthetic fragment of thymosin beta-4 (PDF page 98); the pharmacology discussion on PDF page 105 distinguishes that fragment from the full-length peptide. Evidence involving one cannot simply be relabeled as evidence for the other. A short commercial name is not enough to establish that a study, nomination and offered product are the same substance.
The same presentation says there was insufficient clinical safety information to characterize BPC-157 free base and acetate (PDF page 55). It says FDA had not identified clinical studies or human exposure data for KPV via any route (PDF page 82), and describes corresponding gaps for TB-500 (PDF pages 110–112). These are attributed findings within FDA’s evaluation—not a demonstration that each substance causes a particular harm, and not proof that a missing risk is zero.
Why July and October must remain separate
The October HHS interim-policy analysis concerns a later enforcement-policy document, not the July staff presentation or a new-drug approval. Each stage needs its own source and conditions. A later enforcement position cannot retroactively turn the July briefing into an approval, settle clinical effectiveness or erase product-quality uncertainties.
For a practice, the useful output is a chain of identifiable records: exact substance and form; proposed use and route; FDA staff assessment; committee recommendation if verified; later agency action; and applicable current conditions. When a link in that chain is unresolved, label it rather than replace it with an approval badge.
Evidence record
Event date: 2026-07-23. Source review: 2026-10-29. Editorial publication: 2026-10-29. Original source links below retain their publication dates. These dates are not interchangeable. This is targeted source synthesis, not an exhaustive archive or a qualified clinical/legal review.
- FDA briefing introduction; PDF pages 1 and 3–8 ↗
- FDA July 23 presentation; PDF pages 55, 82, 98, 105 and 110–112 ↗
- FDA meeting page; nonbinding advisory role and agenda ↗
Revision history
29 October 2026: expanded against the specifically cited source passages. Source review is not qualified clinical or legal review. Report a proposed correction through Contact us; do not include patient data.