# Data field guide

Prepared October 14, 2026. Official API responses used here identify October 7, 2026 as their data update date. This is a dated source collection, not a live medical alert or complete recall census.

| File | Row unit | Coverage |
| --- | --- | --- |
| peptide-recalls-actions.csv | One selected firm/date recall action | 10 actions, 2019–2026; drug products and API; source text explicitly confirms a recall |
| genogenix-selected-peptide-records.csv | One FDA product recall number | 11 selected named peptide product records within event 97369 |
| genogenix-event-97369-all-products.csv | One FDA product recall number | All 57 returned records under event 97369, including non-peptides |
| glp1-additional-lot-records.csv | One FDA product recall number | Seven ProRx and three Boothwyn semaglutide records; supplements actions already in the main register |
| manufactured-peptide-recall-examples.csv | One FDA product recall number | Four selected manufactured prescription drug records, not necessarily whole events |
| collagen-recall-example.csv | One FDA food recall number | One Vital Proteins food-product example, outside the main drug register |
| genogenix-event-97369-source-snapshot.json | Original FDA API response | Metadata and complete raw event response used for the 57-record count |
| claim-ledger.csv | One checked claim or grouped source claim | Publication fact-check map; non-publishing support |

Do not sum rows across files. The selected GenoGenix table is a subset of the full event; the event is also one action in the main register.

record_id identifies an editorial action row. recall_number identifies an FDA product recall record. event_id groups FDA product records into an event. firm is the recalling firm, not necessarily a clinic or retailer on a patient's receipt. product_description and code_info preserve source strings in product-level CSVs. Narrative fields in the action CSV summarize the source.

recall_initiated is when recall notification began. company_announcement_date is when the firm issued the reviewed public announcement. fda_publish_date is the notice-posting date when supplied. source_document_date may be a later FDA letter date. report_date and classification_date are separate FDA fields and can differ. Blank fields mean not supplied in the reviewed source; no dates were inferred.

classification and status are product-specific snapshot values when provided. Unknown action-level values do not mean “not classified” or “terminated.” api_last_updated is the official dataset update date. checked_on is when this compilation retrieved or reviewed the source. Those dates are different facts.

lot_details in the action CSV can contain structured JSON text or a source-scope explanation. Product-level code_info is the original detailed code string, including package-specific groups and all-lots wording. Do not collapse all strengths/presentations into one strength. Expiry wording is historical source scope, not a newly assigned shelf life.

For a decision about a package, use the exact FDA source and supplier instructions. Missing matches, blank quantities, and unverified status do not establish safety, approval, or absence of recall.

Original summaries and table arrangement may be reused with credit to Peptide Recall Register. Preserve FDA attribution and the terms applicable to underlying source material. This does not license third-party logos or photographs.

Source detail: ProRx D-0114-2026 omits a unit in its total-strength source string (12.5/5mL). The raw description is preserved; the public table uses the separately stated 2.5 mg/mL concentration and 5 mL vial size without inserting a guessed unit. Boothwyn API lot codes differ from its warning-letter inspection examples; both are retained with their own sources.