Historical FDA Advisory Committee Votes by Company

Find a company's historical FDA advisory committee appearances by sponsor, drug, and normalized asset key, while keeping meeting rows distinct from vote questions and later FDA decisions.

Historical FDA advisory committee votes by company are best retrieved in two passes. Search the sponsor name to identify relevant meetings, then use each program's asset_key to collect every appearance and vote question for that asset. Alphanume's FDA Advisory Committee Votes dataset covers drug and biologic meetings from 2024 forward, with one row per vote question and tallies verified against official minutes.

The Advisory Committee Votes documentation defines sponsor search, drug search, meeting status, vote evidence, and source-material links. This is a historical research workflow. It is not a complete forward medical calendar, and an advisory committee vote is not the FDA's final decision.

Search the sponsor, then stabilize the program

Company names change and meeting materials can refer to a sponsor, partner, or subsidiary. Begin with a case-insensitive sponsor substring, inspect the returned company and product fields, then save asset_key for program-level retrieval. The normalized asset key is more useful than ticker for linking repeated appearances because the dataset is organized around FDA meeting materials rather than an equity master.

Do not count returned rows as meetings until grouping by meeting_key. A single meeting can contain several vote questions. Conversely, a meeting without a numeric tally is retained so the coverage denominator survives. That row carries vote_seq=0 and a vote_evidence value explaining whether minutes are unavailable, no vote occurred, or the meeting was not held.

Retrieve every recorded appearance

After confirming the sponsor match, query the asset key without a narrow tally filter. Keep no-tally rows because they distinguish missing minutes from a discussion-only meeting. Save meeting date, status, committee, center, topic type, question text, yes, no, abstain, favorable-answer coding, and all official material URLs.

GET /v1/biotech/advisory-committees
sponsor=<company name substring>
date_gte=2024-01-01

For each confirmed program:
  GET /v1/biotech/advisory-committees?asset_key=<asset_key>
  group meetings by meeting_key
  order questions by vote_seq
  keep meeting_status, vote_evidence, vote_yes, vote_no,
       vote_abstain, favorable_answer, vote_outcome_favorable,
       minutes_url, transcript_url, materials_url

The endpoint also supports drug and application substring filters. Those are useful for resolving an ambiguous sponsor result, but the final audit table should retain the served meeting and record identifiers. A name search is a discovery method, not a durable primary key.

Read question polarity before comparing votes

Raw yes and no counts cannot be compared across questions without reading their wording. A yes vote can favor a product on one question and oppose it on another, such as a question asking whether use should be restricted. The dataset resolves this with favorable_answer and vote_outcome_favorable. Ties and questions without a product-favorable side can remain null.

• Use vote_yes, vote_no, and vote_abstain when reporting the literal tally.
• Use favorable_answer to interpret the direction of the question.
• Keep null vote_outcome_favorable values rather than forcing them into wins or losses.
• Open the official minutes link when a tally will support a published claim.

Minutes can appear months after a meeting. Recent rows may initially state that minutes are not posted and later be re-projected when FDA publishes new materials. For a current historical inventory, poll updated_since. For a strict point-in-time study, retain retrieval dates and earlier raw responses.

Company-level summaries also need a rule for joint meetings and shared development programs. A committee abbreviation can match a joint meeting even when it is not listed first, while sponsor text may not capture every economic partner. Keep the full committee list and the sponsor exactly as served, then maintain a separate, dated mapping if the research question is about public-company exposure. That mapping should state whether licensing partners, acquirers, and former sponsors are included. It should never silently rewrite the FDA source record.

Do not turn an AdCom tally into an FDA forecast

The principal failure mode is treating a favorable committee outcome as approval. Advisory committees provide outside advice, and FDA can make a different decision. The data can support a statement about how the panel voted, not a claim that approval was assured. A second failure is using scheduled rows as though a vote occurred. Check meeting_status, has_tally, and vote_evidence before calculating company history.

Coverage begins on 2024-01-01, so the result is not an all-time sponsor history. A company with zero returned rows may have had older meetings, may appear under another sponsor string, or may have no meeting in the coverage period. State the start date and the search terms in any exported table.

Create a company vote ledger

As a concrete next action, search one issuer by sponsor, confirm each matched product, and rerun the query by asset key. Export one row per vote question with a separate meeting identifier, literal tally, interpreted favorable side, vote evidence, and minutes URL. Add a meeting-level summary only after grouping the questions. The resulting ledger answers what was actually voted on, when, and with what evidence, while leaving the later FDA decision as a separate research join.