Practice·August 21, 2026 · 3 min read

The panel is a category, not a meeting

Every 510(k) FDA Radar ingests carries a line reading "Panel: Cardiovascular Devices Panel of the Medical Devices Advisory Committee" or similar — openFDA's own field, on every record. It names which specialty reviews that device type administratively. It does not mean that panel, or any panel, ever actually met to discuss this device — most clearances, and most approvals, never see one.

By Connor Griggs — Regulatory & Quality Strategist

Open any 510(k) record FDA Radar has ingested and, most of the time, one of the lines reads Panel: followed by a name like “Cardiovascular Devices Panel of the Medical Devices Advisory Committee.” It reads like provenance — proof that a panel of outside experts looked at this device. For the overwhelming majority of clearances carrying that line, no panel looked at anything. The field means something narrower, and real, and it is not that.

What the field actually is

openFDA’s 510(k) record carries a field, advisory_committee_description (FDA Radar stores it as advisory_committee), that names the medical specialty panel a device type is administratively assigned to for review purposes — derived from the product code, populated on essentially every record, whether or not a human being from that panel was ever in a room with this submission. FDA Radar’s own ingestion renders it as the “Panel:” line, verbatim, in the summary text attached to every 510(k) item — an accurate label for what the field is, and an easy one to misread as a record of what happened.

What an actual meeting requires

A real advisory committee meeting is a different, rarer thing, governed by 21 CFR Part 14. FDA must publish a Federal Register notice at least 15 days before the meeting; background materials are generally posted on FDA’s own site no later than two business days beforehand; the committee hears testimony, asks questions, and in many cases votes — and that vote is a recommendation FDA is not bound to follow. Convening one is reserved for the small number of device submissions each year novel, high-risk, or contested enough to warrant a public hearing. Most 510(k)s, and most PMAs, are decided without one ever being scheduled — the panel field on the record is populated regardless.

The field names who would review a device like this, not who did. Reading it as the second thing costs nothing on ninety-nine records and misleads on the hundredth, with no marker on the record itself telling you which one you’re looking at.

When a meeting notice does show up

When FDA does convene one, the notice reaches the Federal Register feed FDA Radar ingests directly — and lands in the same bucket as any other miscellaneous filing. FDA Radar’s categorizer sorts a Federal Register document into FDA Guidance or Classification Change only on specific title conventions; a meeting announcement matches neither, so it falls to the general Federal Register Noticebucket, with no field marking it a meeting and nothing connecting it forward to whatever FDA eventually decides. The notice is an invitation to a hearing, not its outcome; the vote, when the meeting happens, posts afterward to FDA’s own advisory committee calendar, not as a new Federal Register document, and the decision it was about can land weeks or months later still, in a submission record with no field pointing back to the meeting that preceded it.

The practice

Read the Panel line on a clearance for what it names — a specialty category, not an event — and if the question is genuinely whether an advisory committee met on a device or a device type, check FDA’s own advisory committee calendar rather than infer it from a field that is populated whether or not one did. When a meeting notice does appear in the feed, read it as the opening of a public process with an outcome that will post elsewhere, later, unlinked. What a specific panel assignment or a specific meeting implies about a specific device is a judgment for a regulatory professional reading the record itself — this is regulatory intelligence and method, never regulatory advice about a specific filing.

FDA Radar ingests the Federal Register directly, every business day; see what we monitor and how often for the rest of the pipeline. The Panel field on a 510(k) is real, ingested, and exactly as narrow as FDA defines it.

Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.

Method
The lab is accredited. Not the device.
Practice
Breakthrough is law. STeP is a guidance.
Practice
MDSAP replaces routine. Not for-cause.
Method
No field on a 510(k) says what it treats
Method
Discretion is a policy. Exclusion is a statute.
Practice
Designated by one office. Approved by another.
Method
MedSun sits beside MAUDE, not inside it
Practice
The five-unit device never gets a K-number
Practice
Meeting the criteria isn't a tracking order
Method
The PMA clock doesn't stop at approval
Practice
The K-number doesn't track today's device
Method
A MAUDE report proves it was filed
Practice
Not every MDR starts with the manufacturer
Method
Completed. Not terminated.
Practice
The device-ban list has three entries
Method
The UDI exception has its own deadline
Method
MDUFA VI is being negotiated in public
Practice
The inspection manual changed, not the rule
Method
The count Congress had to legislate
Practice
The small-business rate isn't retroactive
Method
A detention order has no docket to read
Practice
PMA approvals moved off the Federal Register
Method
A citizen petition names names
Practice
A market withdrawal isn't a recall
Method
Not every device letter comes from CDRH
Practice
Closed on one device. Open on the rest.
Method
No IDE is confirmed until the PMA is
Practice
The remedial-action call sets the clock
Method
Jurisdiction is a letter, not a field
Practice
An address is not a footprint
Method
The final rule that isn't final yet
Practice
The special controls aren't in the record
Method
Exempt from GMP. Not from complaints.
Practice
The notify list isn't the shortage list
Method
A constraint can't be skipped. A script can.
Practice
No cron sends this. A person does.
Method
Corrected, not rewritten
Practice
Quiet is a finding, not a default
Method
The summary is public. The statement isn't.
Practice
A competitor's 513(g) leaves no trace
Practice
An empty response field proves nothing
Method
A petition is public. Its outcome isn't.
Method
An accessory carries its own classification
Method
A TPLC report is a category, not a device
Practice
A 522 order is a question, not a verdict
Method
A PCCP change leaves no new record
Practice
Not every signal becomes a recall
Method
eSTAR did not remove the acceptance check
Practice
An early alert has no recall number yet
Practice
A consent decree isn't a database row
Method
The record has no cybersecurity field
Practice
Classification Change is not one event
Method
Publication date is not effective date
Method
One event. Many recall numbers.
Practice
Quantity is a sentence, not a number
Practice
How a firm told you is a field too
Method
A RIN outlives the document number
Method
The docket ID is not the comments
Practice
The 510(k) record doesn't name the predicate
Practice
The 510(k) FDA didn't review first
Method
The letter FDA doesn't have to post
Practice
Cleared doesn't say which track it took
Method
The clock stops. The calendar doesn't.
Method
Why a guessed match never reaches you
Practice
The standards list never names a device
Method
The guidance isn't in the Federal Register.
Practice
Filtered. Not discarded.
Method
There are two recall databases, not one
Practice
Breakthrough status is confidential by law
Practice
One MAUDE report is not one malfunction
Method
A supplement number is not a track
Method
Cleared is not approved
Practice
Nationwide doesn't mean your building
Practice
Not every correction reaches FDA
Method
Registered. Not reviewed.
Method
Contact ODE is not a pathway
Practice
Almost no recall is FDA-mandated
Method
FDA's device names read like a card catalog
Practice
openFDA is free. It is not unlimited.
Method
GUDID stores the model. Not the box.
Practice
Detention doesn't need a warning letter
Method
A Class I device, a Class I recall
Practice
21 CFR 820 didn't move. Its contents did.
Method
The product code that doesn't exist yet
Practice
The classification posts. The 483 behind it doesn't.
Method
A recall has three dates, and the pipeline had to pick one
Practice
The count is real. The rate is not.
Method
The firm on the record is not the firm on the box
Practice
Low confidence is an instruction, not a hedge
Method
The same company, spelled three ways
Practice
A device that was never a medical device
Method
FDA's warning letters, addressed by column number
Practice
Your regulation has a decimal. FDA's watch doesn't.
Method
Three letters is too short to search for
Practice
Most warning letters never close
Method
The guidance that skipped the draft
Practice
Ongoing, as of when?
Method
The least interesting fact in a 510(k)
Practice
No recall arrives with a product code attached
Practice
The deadline that doesn't email you
Method
The warning letter has two dates
Method
How to monitor FDA without drowning
Practice
Your predicate was recalled. Now what?
Method
Why no item reaches you without a human