The Safety and Performance Pathway keeps the predicate

FDA's Safety and Performance Based Pathway gets described, sometimes, as a way to clear a 510(k) without a predicate — a shortcut around the comparison that otherwise anchors the whole submission. That description gets the mechanics wrong in a way that matters if a team builds a submission strategy on it. The pathway, laid out in FDA's final guidance issued September 20, 2019, doesn't remove the predicate requirement. It changes what the submission has to do once a predicate is named: instead of generating bench data that compares the new device head-to-head against that specific predicate's own performance, a sponsor can show the new device meets performance criteria FDA has already published for that device type.

An expansion of an idea this blog has already covered

The pathway isn't a standalone mechanism invented from scratch — FDA describes it as an expansion of the concept behind the Abbreviated 510(k), which lets a submitter rely on conformance to a recognized consensus standard in place of generating the underlying data itself. The Safety and Performance Based Pathway applies that same substitution logic to a narrower, more specific question: not just whether a standard covers a given test, but whether FDA has published a defined set of performance criteria and testing methodologies for the exact device type at issue, criteria a submitter can test against directly instead of designing a comparison study around one particular predicate's own characteristics.

Where the criteria actually come from

Those criteria aren't invented case by case. FDA's guidance ties them to FDA guidance documents, FDA-recognized consensus standards, or special controls already established for the device type — sometimes stated as an explicit numeric threshold, sometimes described qualitatively where a quantitative test doesn't fit the question, biocompatibility being the guidance's own example of the latter. The pathway is only open where FDA has actually done that work for a given device type: published, device-specific guidance identifying the criteria and the methods for testing against them. FDA has issued this kind of guidance for a small, named set of device types — conventional Foley catheters, cutaneous electrodes for recording purposes, spinal plating systems, orthopaedic non-spinal metallic bone screws and washers, and magnetic resonance receive-only coils among them. A device type without one of these documents doesn't have a performance-criteria route to elect; the pathway isn't a general election available to any submission that would rather skip a comparison study.

The predicate's job narrows; it doesn't disappear

A 510(k) filed under this pathway still has to name a predicate and still has to establish the two things every 510(k) establishes against it: the same intended use, and technological characteristics that don't raise different questions of safety and effectiveness. What changes is how that second question gets answered. Instead of a comparative test protocol built around the specific predicate's own bench data, the submission demonstrates conformance to the published performance criteria for the device type — criteria FDA has already judged adequate to answer the safety-and-effectiveness question for that category, independent of which particular cleared device ends up named as predicate. A submission that reads the pathway as license to drop the predicate discussion entirely has confused the part of the analysis the criteria replaced with the part they didn't touch.

Where this meets the file

A pathway-eligibility check belongs earlier in a submission plan than most teams put it — before a predicate gets selected, not after, since the device type has to already have a published performance-criteria guidance for the pathway to be available at all, and that same guidance is what should shape which predicate makes the strongest fit rather than the other way around. A pathway-eligibility worksheet that checks a device type against FDA's current list of performance-criteria guidances before a predicate search even starts is previewed in the launch catalog. If your program runs this check at a different point in the process, the shelf takes that correction directly.