Breakthrough Devices Program and SaMD Considerations

1. Key takeaways

The Breakthrough Devices Program is FDA’s voluntary accelerated pathway for devices intended to treat or diagnose life-threatening or irreversibly debilitating diseases or conditions, and for devices designated as breakthrough under FD&C Act §515B. Software as a Medical Device (SaMD), by contrast, is not a separate pathway: it is submitted through the ordinary Class I / II / III routes, but it carries dedicated labeling provisions at 21 CFR 801.50.

• The Breakthrough Devices Program accelerates communication and prioritizes resources; it does not lower the scientific review standard.
• SaMD has no standalone US market pathway, but it does have standalone labeling rules under 21 CFR 801.50.
• The device definition in FD&C Act §201(h) reaches software, so claims of being software rather than a device carry no weight.
• SaMD is subject to UDI obligations under 21 CFR Part 830, including data submission to GUDID, with records handled differently from physical devices.
• Where software serves as an accessory to a device, the Accessory Classification Request Q-Sub can be used to confirm its classification.

2. Legal basis

The table below lists the authorities governing the Breakthrough Devices Program and the software-specific obligations that apply regardless of pathway, verified in 2026.

3. Expert insights

Insight 1: The Breakthrough Devices Program is communication acceleration, not a lowered standard. The program provides a more intensive communication mechanism with FDA and priority access to agency resources; the scientific standard of review is not reduced in any respect. Sponsors should not read acceptance into the program as making the device easier to clear or approve. The benefit lies in earlier and richer interaction, which helps teams identify and resolve issues sooner, not in a softer evidentiary bar at the finish line.

Insight 2: SaMD has no separate market pathway in the United States, but it does have separate labeling provisions. The device definition in FD&C Act §201(h) does not list software as a distinct category, yet software is regulated as a device in practice, and 21 CFR 801.50 provides dedicated labeling rules. Two conclusions follow at once: the argument that we are software and therefore not a device does not hold, and the assumption that software is exempt from labeling obligations does not hold either. Both propositions should be corrected wherever they appear in internal planning documents.

Insight 3: UDI obligations apply to SaMD just as they do to hardware. Under 21 CFR Part 830, SaMD must be assigned a UDI and its data must be submitted to GUDID. The way a software product is recorded in GUDID differs from how a physical device is recorded, so the GUDID data field requirements must be checked before submission. Treat the UDI workstream as a real deliverable with its own owner, rather than as an afterthought appended to the submission checklist.

Insight 4: The Accessory Classification Request is available for software accessories. According to the FDA eSTAR Program page, the Q-Sub types include the Accessory Classification Request. Where software functions as an accessory to a device, this Q-Sub can be used to ask FDA to confirm its classification. Settling the accessory question early prevents the downstream confusion of a product whose regulatory identity shifts between its host device and its own status.

Taken together, these points sketch a consistent theme: software does not escape the device framework by being software, and acceleration does not replace evidence. The sponsors who navigate this space most effectively treat every software product as a regulated device from day one, with labeling, UDI, and cybersecurity workstreams running alongside development rather than trailing behind it. They also frame acceleration requests honestly, seeking the Breakthrough designation only where the qualifying condition genuinely exists and relying on ordinary pathway discipline everywhere else. That restraint protects credibility with the agency and keeps the program on a schedule the evidence can actually support.

4. Practical recommendations

• Assess Breakthrough Devices Program eligibility starting from the life-threatening or irreversibly debilitating disease or condition criterion.
• For SaMD projects, plan the 21 CFR 801.50 labeling work and the UDI / GUDID submission in parallel with the program from the outset.
• Where software serves as an accessory, use the Accessory Classification Request Q-Sub to confirm classification.
• Prepare the cybersecurity documentation in step with submissions for devices that contain software.
• For products containing AI or machine learning, plan the change management approach in advance, so that every algorithm update does not trigger a new premarket submission.

5. Verification checklist

• □ Breakthrough Devices Program eligibility assessed, with a written conclusion.
• □ SaMD projects confirmed against the 21 CFR 801.50 labeling requirements.
• □ UDI assignment and GUDID data submission planned.
• □ If the product is a software accessory, an Accessory Classification Request Q-Sub is planned.
• □ Cybersecurity documentation included in the submission materials list.
• □ For products with AI / machine learning, an algorithm change management plan is in place.
• □ Product labeling reviewed to confirm no claim of exemption from the device framework on the basis of being software.

A final observation concerns how software projects budget for these obligations. Because SaMD rides the ordinary classification routes, teams accustomed to hardware submissions sometimes underestimate the labeling and UDI effort and the cybersecurity documentation burden, none of which shrinks merely because the product ships as code rather than in a box. Building these line items into the project plan from the start, with named owners and review checkpoints, keeps the submission date stable even when development cycles are short and releases are frequent, which is the normal rhythm of software work.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, US Agent and local testing support for the United States market. Our team manages FDA establishment registration and listing, 510(k)/De Novo/PMA submissions, and supports post-market reporting obligations. Business enquiries: info@grzanglobal.com