Every cleared 510(k) has a public summary attached to it, sitting in FDA’s own database for anyone to read. Most people outside a submission never open one; most people inside regulatory affairs open dozens before they really learn what the document can, and can’t, tell them.
What a 510(k) summary is, and isn’t
Under 21 CFR 807.92, a submitter clearing a device through the 510(k) pathway must provide either a summary of the safety and effectiveness information in the submission or a statement that the information will be made available to anyone who requests it. Almost everyone chooses the summary, because it becomes the public record instead of an open-ended promise to hand over data on demand. That summary covers the device and submitter name, the predicate device or devices it was compared to, a description of the device, its indications for use, a technological comparison to the predicate, and a summary of the performance data supporting a conclusion of substantial equivalence — the same conclusion covered in depth in the free 510(k) pathway course.
What the summary is not is FDA’s own account of the review. It is written by the applicant, describing the applicant’s argument, and FDA’s acceptance of that argument is expressed only as the clearance itself — there is no published reviewer narrative explaining which parts of the comparison mattered most or which questions came up along the way. Reading a summary tells you what was argued and that it worked. It does not tell you how close the call was, or what an interactive review deficiency letter might have asked for along the way.
Reading one for a specific question
A summary is most useful when you open it already knowing what you’re trying to find out, rather than reading it end to end out of general curiosity. Researching predicate options for your own device means comparing the indications for use statement word for word against yours, not just matching the device category. Researching testing expectations for a device type means reading the performance data section for the kinds of tests actually cited — bench testing, biocompatibility testing referenced against ISO 10993, software documentation, sterilization validation — as a signal of what a reviewer expected to see. And checking which box is marked for the review pathway itself, Traditional, Special, or Abbreviated, changes what the comparison in front of you actually had to prove.
- Confirm the predicate’s indications for use actually match yours, not just its general device category.
- Check whether the clearance predates a guidance document or standard revision that would change the comparison today.
- Check FDA’s recall and safety communication history for that device before tying your own submission to it.
- Note the review pathway on the summary — it changes what the comparison in front of you had to prove.
Two habits that misread a summary
Mistaking a summary for proof the same design will clear
Only cleared submissions are public. Nothing in the database says how many similar submissions didn’t clear, or why — a short summary of one success says nothing about the attempts that never became one.
Copying a predicate’s comparison table without re-deriving it
The table exists because someone built the actual substantial equivalence argument behind it. Reusing its structure without redoing the comparison for your own device just moves the same unverified assumption into a new submission.
Sources & further reading
- FDA — Content and Format of a 510(k) Summary, 21 CFR 807.92 ecfr.gov
- FDA — 510(k) Premarket Notification Database accessdata.fda.gov
- Regulatory Academy — The 510(k) Pathway, a free five-lesson course regulatoryacademy.com
- Regulatory Academy — Choosing the Predicate regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.
