What is an FDA 510(k) premarket notification?

A 510(k) is a premarket notification to FDA showing that a device is substantially equivalent to a legally marketed predicate device: it has the same intended use, and either the same technological characteristics or different ones that do not raise different questions of safety and effectiveness. The device cannot be marketed until FDA issues an order finding it substantially equivalent.

Many Class I, II, and III devices that do not need a premarket approval (PMA) need a 510(k) before they can be marketed in the US. The submitter compares its device to a predicate and shows it is at least as safe and effective. FDA's substantial equivalence decision has a 90 FDA review day goal, with the clock stopping while FDA waits for answers, so elapsed time is longer. Domestic manufacturers, specification developers, some repackagers and relabelers, and foreign manufacturers must submit. Some Class I and II devices are exempt by regulation, within the limits each exemption sets.

Choosing a predicate

  • Any legally marketed device can serve as a predicate, but a recently cleared 510(k) device is the usual choice.
  • The submission names a primary predicate that is most similar to the new device. Combining features from several predicates into one argument, known as split predicates, is not accepted.
  • FDA's 510(k) database lists every cleared device, and searching by product code is usually the most effective approach.
  • If no predicate exists, the De Novo pathway can classify a novel device into Class I or II, and a device granted De Novo can then serve as a predicate for later 510(k)s.

What it means for software

For SaMD and other device software, the 510(k) carries the software documentation described in FDA's 2023 guidance on device software functions: a Documentation Level statement, a software description, a risk management file, requirements, architecture, development and maintenance practices, and testing. A cleared product can still change, but a new 510(k) may be needed when a change could significantly affect safety or effectiveness, or when the intended use changes, and the 510(k) holder decides whether that threshold is met. This is the main reason teams plan their change control, and sometimes a PCCP, early.

Example

A company builds software that measures a value from medical images, similar to tools already on the market. It searches the 510(k) database by the product code its competitors used, picks the closest cleared device as its primary predicate, and builds its comparison around intended use and technology. A year later it wants to extend the software to a new patient population. That is a change in intended use, so it plans a new submission instead of shipping the change as a routine update. Onix Health produces the software documentation for submissions like this. The manufacturer files the 510(k) and holds the clearance.