Method·August 7, 2026 · 3 min read

A supplement number is not a track

openFDA's PMA record logs a supplement number and a free-text reason for every change to an approved device — not which of FDA's four review tracks, from a same-day call to a full panel, that change actually took.

By Connor Griggs — Regulatory & Quality Strategist

A PMA approval reads like the end of a story: FDA found reasonable assurance of safety and effectiveness, and the device is on the market. For an approved Class III device that stays on the market for years, the approval is closer to a starting line. Materials change. Software changes. Manufacturing sites change. Every one of those changes to an approved device has to go back to FDA as a PMA supplement, and FDA runs supplements through four genuinely different reviews, not one.

Four tracks, not four names for one process

21 CFR 814.39 sets out the supplement pathways, and the track a change takes depends on what the change actually is. A panel-track supplement is for a significant change in the device’s design or performance, or a new indication for use — substantial enough that FDA can route it to the same outside advisory panel that reviewed the original PMA. A 180-day supplement covers a significant change in components, materials, design, specification, software, color additives, or labeling that does not rise to panel-track territory; FDA’s own goal for these is in the name. A real-time supplement is for a minor change — to design, software, sterilization, or labeling — reviewed interactively, in a meeting or call FDA has agreed to hold, with both sides settling the supplement’s status inside that forum rather than waiting out a fixed clock. And a change to manufacturing procedures or methods that affects safety or effectiveness goes in as a 30-day notice — effective 30 days after FDA receives it, unless FDA decides the notice is inadequate, in which case it does not simply get rejected. It gets converted, mid-review, into a full 135-day PMA supplement.

Four different questions get asked, on four different clocks, and the public record uses the same word — supplement — for the answer to all of them.

What the public record actually keeps

openFDA’s field reference for the PMA endpoint documents a supplement_number for every change filed against an approved device, and a free-text supplement_reason describing what the applicant said the change was for. What it does not carry is a field naming which of the four tracks a given supplement travelled — panel-track, 180-day, real-time, or a 30-day notice, converted or not. Two supplements can sit side by side in the record, both approved, both carrying a short reason line, and one of them cleared a phone call while the other cleared an advisory panel. The record does not distinguish them for you.

The practice

Reading a competitor’s or your own device’s supplement history off the public PMA record, the reason text is the only field that says anything about substance, and it is written by the applicant, not audited into a controlled vocabulary the way a decision code is. A reason line mentioning a design change or a new indication is worth reading against FDA’s own guidance on which changes trigger which track, rather than assumed from the approval date alone — a fast turnaround is consistent with a real-time supplement, but it is not proof of one, and a slow one is not proof of a panel-track review either. Determining which track a specific supplement took, and what that implies for a device you are tracking, is a question for the guidance documents and, where it matters, a regulatory professional — this is regulatory intelligence and method, never regulatory advice about your own filing strategy.

PMA supplement data sits outside FDA Radar’s current source coverage — the product watches 510(k) clearances, not PMA approvals or their supplements — so this one is a method note for reading the public record directly, the same discipline the rest of our sourcing is held to.

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.

Practice
One MAUDE report is not one malfunction
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