A committee no clearance ever names

A 510(k) or PMA record carries fields naming who reviewed it and under what standard — a specialty panel assignment, a review center, a decision. FDA also runs a standing committee built to touch none of that machinery at all: not assigned to a device type, not tied to a product code, and never a party to a single clearance or approval decision in its own right.

A committee built to seat one kind of member

Section 1137 of the Food and Drug Administration Safety and Innovation Act (2012) directed FDA, for the first time by statute, to develop strategies for soliciting patient views during medical product development and regulatory discussions. Out of that mandate, FDA chartered the Patient Engagement Advisory Committee (PEAC) — the only FDA advisory committee whose charter reserves its voting seats for patients, caregivers, and patient advocates, up to nine of them, with a nonvoting industry representative and a nonvoting consumer representative alongside. No clinician or scientist holds a voting seat. Every other CDRH advisory body reviewing device evidence is built the other way around.

Established, then quiet for two years

FDA established PEAC by Federal Register notice on September 21, 2015, opening a public docket alongside it. The committee’s first actual meeting did not happen until October 11–12, 2017 — close to two years later. Both dates are on the public record precisely because they are administrative acts FDA is required to announce; the gap between them is not a secret, just a fact nothing forces a reader to notice unless they check both.

A specialty panel is assigned to a device type before it is ever convened. This committee is assigned to no device at all, by design — its subject is how FDA weighs a patient’s evidence, not which product reaches the market.

What it advises on, and what it never touches

PEAC’s charter scopes its advice to cross-cutting method questions: clinical trial design, patient preference information, device labeling conventions, unmet clinical needs, benefit-risk frameworks. It does not clear a 510(k), approve a PMA, or classify a product code, and nothing in its charter ties a session to an application number or a CFR regulation the way a classification order or a warning letter does. A recommendation from a PEAC meeting can go on to shape a guidance document FDA issues months or years later — but the guidance, when it arrives, carries no field, citation, or structured link back to the committee session that shaped it. The Federal Register record FDA Radar ingests daily has a document number, a docket ID, a regulation identifier number; it has no field for “the advisory committee recommendation this responds to.”

The practice

A portfolio watch keyed to product code, CFR regulation, application number, or firm name — the identifiers this product and every one like it actually join on — has no key to catch a PEAC session at all, and that is not a gap in any one pipeline’s coverage. It is what the committee is: a body whose output is a recommendation about method, not an event attached to a device. Tracing whether patient input shaped a specific later guidance means reading that guidance itself, not querying a field that was never built to hold the answer. What a specific guidance document owes to a specific committee session is a judgment for a regulatory professional reading the record, never a conclusion this post draws for them — this is regulatory intelligence and method, never regulatory advice about a specific filing.

See what we monitor and how often for the rest of FDA Radar’s boundary. PEAC’s own meetings and transcripts sit outside all four sources this product reads today.