Method·August 29, 2026 · 4 min read

No IDE is confirmed until the PMA is

An investigational device exemption's existence is confidential by FDA's own rule until the device wins premarket approval or a product development protocol notice takes effect. Until then, the sponsor and the reviewing IRB, not FDA, decide whether an IDE even has to exist.

By Connor Griggs — Regulatory & Quality Strategist

A device company’s regulatory history becomes public in stages. A 510(k) clears and the decision posts. A PMA is approved and the summary follows. A recall opens, a warning letter goes out, a classification changes — each one eventually lands in a database FDA Radar or anyone else can read. An Investigational Device Exemption is different. For as long as the underlying study runs, FDA’s own rule keeps its existence confidential — not because no one has built the right database yet, but because the regulation says so.

The rule, plainly

Under 21 CFR 812.38, FDA will not disclose that an IDE exists — unless the sponsor has already publicly disclosed or acknowledged it — until one of two things happens: FDA approves a premarket approval application for the device under investigation, or a notice of completion of a product development protocol for the device becomes effective. Both are downstream events. A study can enroll its first subject years before either one occurs, if it occurs at all.

Even once existence is acknowledged, the rule doesn’t hand over the file. The confidentiality protection lifts for the fact that an IDE exists, not for the data and information inside it, which stays protected under the same section’s narrower disclosure exceptions.

Who decides risk before FDA sees anything

The gap runs deeper than confidentiality. For many device studies, FDA never reviews an application at all before enrollment starts. Under 21 CFR 812.66, the sponsor makes the initial call on whether its own study poses a significant risk or a nonsignificant risk, and presents that determination, with its reasoning, to the reviewing IRB. Unless FDA has already made a risk determination for the study, the IRB reviews the sponsor’s call and can modify it if it disagrees.

If the study lands — sponsor and IRB agreed — as a nonsignificant risk study, the sponsor proceeds under the abbreviated requirements at 21 CFR 812.2(b): IRB approval, labeling under 812.5, informed consent, monitoring, and recordkeeping. No IDE application goes to FDA. No submission exists for FDA to have received, let alone disclose.

If the IRB disagrees with a sponsor’s nonsignificant-risk proposal and calls the study significant risk instead, the sponsor has to tell FDA — but on a short clock and a narrow question. Under 21 CFR 812.150(b)(9), the sponsor reports the IRB’s determination within five working days of learning of it. That report, not a public posting, is the first point FDA is even on notice the study exists.

For a nonsignificant-risk study, there is no application for FDA to have received. There is nothing yet for a confidentiality rule to protect, because there is nothing yet FDA has been told.

What that means for reading a portfolio

Put the two rules together and a specific, structural gap follows: a competitor’s ongoing U.S. clinical device study is not something any FDA record can surface while it runs. Not because FDA Radar, or any other service built on FDA’s public data, hasn’t indexed it yet — because for a nonsignificant-risk study, no FDA record of it exists yet to index, and for a significant-risk study under IDE review, the confidentiality rule keeps its existence unconfirmed regardless. A device that later clears through a 510(k) or wins PMA approval can carry years of investigational history that never surfaces anywhere public until the clearance or approval itself does — and even a PMA approval only confirms that an IDE existed, not what it contained.

The practice

Reading a competitor’s pipeline for signs of an active clinical device program means watching for what a study eventually produces — a PMA approval, a De Novo grant, a 510(k) built on data that had to come from somewhere — not searching for the IDE itself, which is built by rule to stay unconfirmed until one of those events happens. Whether a specific device study qualifies as significant or nonsignificant risk, and what that determination should be for a program of your own, is a call for the sponsor and its reviewing IRB to make under 812.66 — this is a description of how that determination and FDA’s own confidentiality rule work, and what they leave out of the public record, regulatory intelligence and method, never regulatory advice about any specific device’s risk classification.

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.
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.
Practice
The panel is a category, not a meeting
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