IDE reporting doesn't stop at the application

An approved IDE reads, in a lot of files, like the end of the regulatory work on a device study — the protocol cleared, the IRB signed off, enrollment can start. 21 CFR 812.150 treats approval as the point where a second, ongoing set of duties actually begins. The section requires progress reports, and not just one kind: investigators report to sponsors, sponsors report to IRBs and, for higher-risk studies, to FDA itself, on a schedule that keeps running for as long as the investigation does. A study team that filed carefully once and then goes quiet until the final report has skipped most of what 812.150 actually requires.

The chain starts with the investigator, not the sponsor

812.150(a) puts the first reporting duty on the site: an investigator has to submit progress reports on the investigation to the sponsor, the monitor, and the reviewing IRB at regular intervals, and in no event less often than yearly. The same paragraph sets two much shorter clocks on top of that routine cadence — an unanticipated adverse device effect has to reach the sponsor and the reviewing IRB as soon as possible, and no later than ten working days after the investigator first learns of it, and a withdrawal of IRB approval has to be reported within five working days. A site that's current on its annual progress report can still be behind on 812.150 if one of these shorter, event-triggered duties never got built into the study's own tracking.

Whether FDA is on the distribution list depends on an earlier call

812.150(b) sets the sponsor's own obligations, and the reach of one of them turns on a determination made before the study ever opened: whether the device is significant risk or nonsignificant risk. A sponsor of a significant risk device study has to submit progress reports to FDA, at least yearly, in addition to the reports every sponsor owes every reviewing IRB. A nonsignificant risk study — the category this blog has already covered as the one that skips the full IDE application — keeps that same annual reporting duty running to the IRB, but never to FDA, because the abbreviated requirements that let the study proceed without an application never route reporting to the agency either. A sponsor that assumes every IDE study owes FDA a yearly report is applying the significant-risk rule to a population that may never have triggered it.

A treatment IDE adds a second, faster cadence on top

Where a study runs under a treatment IDE — a device made available under Part 812 subpart before the marketing application is complete, because withholding it would deny effective treatment to patients with a serious or life-threatening condition — 812.150 layers a semi-annual reporting duty under 812.36(f) on top of the ordinary annual report the section otherwise sets. That's not a replacement for the yearly report; it runs alongside it, on its own shorter clock, because a study distributing a device to patients ahead of full approval carries a correspondingly tighter obligation to keep FDA and reviewing IRBs current on what's actually happening.

The routine report and the event report aren't interchangeable

None of the shorter, event-triggered duties — the ten-day adverse-effect report, the five-day IRB-withdrawal report — get satisfied by a study's next scheduled annual report arriving on time. They're separate obligations with separate triggers, and a tracking log built around one calendar date for “the IDE report” has nowhere to record that a shorter clock started running the moment a specific event occurred. That's a narrower version of the same lesson this blog has already traced through FDA's own adverse-event reporting for marketed devices: a routine periodic report and an event-triggered one live on different clocks even when they eventually land in the same file.

Where this meets the file

An IDE reporting tracker that separates the routine annual cadence from the event-triggered clocks, and flags whether a given study's risk determination puts FDA on the distribution list at all, is previewed in the launch catalog. If your program's studies report on a different schedule, the shelf takes that correction directly.