Section 523 of the Food, Drug, and Cosmetic Act — added by the Food and Drug Administration Modernization Act of 1997 — lets FDA accredit private organizations to review certain 510(k)s. Decades on, the 510(k) Third Party Review Program is still treated by most device teams as a footnote rather than a routing decision. That is a planning gap, not a compliance one: FDA says close to half of the 510(k)s it receives carry a product code eligible for the program, and most teams never check.
What the program actually does
An accredited Review Organization applies FDA's own substantive review criteria to an eligible 510(k), then forwards its recommendation and the full documented review to FDA. FDA does not rubber-stamp that recommendation — it retains final decision authority, including the ability to request more information or find the device not substantially equivalent. What changes is who does the first, often slower, pass: a Review Organization working your submission exclusively, instead of your file taking its place in FDA's 510(k) clearance queue alongside everything else the agency is reviewing that quarter.
Eligibility is a lookup, not a guess
The mistake we see most often is a team assuming their device is too novel, too Class II, or too complex for third-party review — without ever checking FDA's eligible-device list. Eligibility runs on product code, not on how the sponsor feels about the device's complexity. The exclusions, by contrast, are categorical and worth knowing cold before you plan around the program:
- All Class III devices. Premarket approval territory sits outside the program entirely; it is a 510(k)-only mechanism.
- Permanently implantable Class II devices. Excluded regardless of product code, even where the device would otherwise be eligible.
- Life-sustaining or life-supporting Class II devices. Same categorical exclusion as implantables.
- Any 510(k) that requires clinical data. If your submission strategy depends on clinical evidence to support substantial equivalence, the file goes to FDA directly, not to a Review Organization.
The Review Organization is not a lighter-touch reviewer. It applies FDA's own criteria to the same file FDA would see — the difference is whose desk it sits on first. Why the submission doesn't get thinner
The fee mechanics most teams get backwards
Because this is a voluntary, privately accredited program, the fee relationship runs differently than a standard 510(k). FDA does not charge its own user fee for a submission reviewed through the program; the sponsor negotiates and pays the Review Organization directly, and that fee is set by agreement between the two parties rather than by FDA's annual MDUFA fee schedule. That makes the Review Organization relationship a vendor negotiation as much as a regulatory one — worth scoping before you commit a submission timeline to it, the same way you would scope a pre-submission meeting strategy before relying on it.
- Pull your product code and check it against FDA's current eligible-device list before you plan a submission route around either option.
- Rule out the categorical exclusions — Class III, permanently implantable, life-sustaining/life-supporting, or clinical-data-dependent — before engaging a Review Organization.
- Scope the Review Organization relationship like a vendor contract: fee, timeline, and documentation expectations, in writing, before the submission is built.
- Build to FDA's standard regardless of route. The Review Organization's criteria are FDA's criteria; nothing about the file gets lighter.
None of this changes your technical file. What changes is sequencing: a correctly scoped third-party review can take a submission off FDA's own queue and onto a dedicated reviewer's desk, while an incorrectly scoped one just adds a vendor relationship on top of the same FDA review you would have had anyway. The decision is worth five minutes against FDA's eligible-device list before it becomes a submission-strategy assumption nobody checked.
Frequently asked questions
Which 510(k) devices are eligible for FDA's Third Party Review Program?
Most Class I and Class II devices are eligible, checked by product code against FDA's published eligible-device list or the agency's Device Classification Database. FDA has said roughly half of the 510(k)s it receives fall into an eligible product code — eligibility is a lookup, not a judgment call.
Does FDA charge a user fee for third-party-reviewed 510(k)s?
No separate FDA user fee applies to the third-party review itself. The submitter negotiates and pays a fee directly to the accredited Review Organization; FDA's standard 510(k) user fee structure sits outside that arrangement.
Does an accredited third party's recommendation guarantee FDA clearance?
No. The Review Organization applies the same substantive criteria FDA would and forwards its recommendation and documented review to FDA, but FDA makes the final decision — it can still request more information or determine the device is not substantially equivalent.
Sources & further reading
- FDA. 510(k) Third Party Review Program — program overview. fda.gov
- FDA. How to Submit a 510(k) Through the Third Party Review Program. fda.gov
- Food, Drug, and Cosmetic Act Section 523 (21 U.S.C. 360m), added by the Food and Drug Administration Modernization Act of 1997, Section 210. govinfo.gov
This article is provided for general informational purposes and reflects the regulatory landscape as of October 2026. It is not legal or regulatory advice. Confirm current third-party review eligibility and the active Review Organization roster with FDA before acting.
