Severity isn't STeP's gate; safety is

It's tempting to read FDA's Safer Technologies Program as Breakthrough for devices that just aren't serious enough to qualify — a consolation pathway for anything that misses the life-threatening-or-irreversibly-debilitating bar. That reading gets the relationship backwards. STeP, finalized in guidance FDA announced in the Federal Register on January 6, 2021, doesn't ask a device to clear a lower version of Breakthrough's severity test. It asks a genuinely different question, built around a safety improvement rather than a disease's severity, and the two-part test this blog has already covered for Breakthrough and STeP's own eligibility criteria run on separate axes that happen to unlock similar procedural benefits once either one is cleared.

Two different first questions

Breakthrough designation, under Section 515B of the FD&C Act, opens with a disease-and-effectiveness prong: the device has to target a disease or condition that's life-threatening or irreversibly debilitating, with a reasonable expectation of more effective treatment or diagnosis than the current standard of care. STeP's own guidance sets a different first gate. The device has to be intended to treat, diagnose, or prevent a disease or condition that's reasonably expected to reduce the incidence of serious adverse events, other significant safety issues, or issues associated with an existing legally marketed device or the current standard of care — explicitly for diseases and conditions that don't meet Breakthrough's own severity threshold. A device can fail Breakthrough's first prong entirely and still be exactly the kind of device STeP's guidance describes.

What has to stand in severity's place

Where Breakthrough's second prong offers four alternate doors — breakthrough technology, no alternative, significant advantage, or patient interest — STeP asks for one specific thing instead: a reasonable expectation that the device offers a significant safety innovation, addressing a defined safety issue more effectively than the available alternatives. A submission built by cataloging general safety features of the device, without tying them to a specific, named safety problem the device measurably improves on, hasn't made the case STeP's guidance is actually asking for — the standard is comparative and specific, not a general safety-consciousness narrative.

A statute on one side, a guidance document on the other

Breakthrough exists because Congress wrote it into the FD&C Act through the 21st Century Cures Act in 2016. STeP has no equivalent statutory provision behind it; FDA built and operates the entire program under its general administrative authority, through guidance alone. That's not a lesser credential in practice — the guidance is final, and FDA has run the program consistently since 2021 — but it does mean the program's terms can move at guidance speed rather than legislative speed, and a sponsor citing STeP eligibility criteria from an older summary risks citing terms FDA has since revised without any statute forcing a public comment period first. The two programs are also mutually exclusive for a given device: a device accepted into Breakthrough doesn't get to also carry a STeP designation, and the choice isn't a sponsor's preference — it follows from which of the two, structurally different, first-gate tests the device actually clears.

The same toolkit, borrowed on purpose

Once a device clears either gate, the procedural benefits look similar because FDA built STeP to borrow Breakthrough's own mechanics deliberately: more interactive and timely communication during development, sprint discussions to resolve open questions early, and priority review once a marketing submission is filed. None of that touches the evidence a submission still has to carry. A STeP-designated device pursuing a 510(k) still has to establish substantial equivalence; one pursuing a PMA still has to establish reasonable assurance of safety and effectiveness. STeP buys the same kind of speed Breakthrough does, for a case that couldn't have used Breakthrough's own door to get there.

Where this meets the file

A designation-request tracker that files STeP and Breakthrough under one undifferentiated “expedited pathway” column is hiding the one distinction that actually matters for drafting the request: which first-gate test the device is arguing, severity-and-effectiveness or safety-innovation, since the evidence behind each is not interchangeable. Raising the question through a Pre-Submission built around a specific, answerable question before committing to either designation request is the same discipline this blog has already covered for pathway selection generally. A designation-request worksheet that keeps STeP's and Breakthrough's own eligibility tests in separate, clearly labeled fields is previewed in the launch catalog. If your program tracks these differently, the shelf takes that correction directly.