Regulatory strategy and submissions

Your regulatory strategy and submission, written with your team.

We help you work out your software's U.S. Food and Drug Administration (FDA) classification, plan the pathway, and write the submission documentation with you: 510(k), De Novo, and EU Medical Device Regulation (MDR).

In short

What does regulatory strategy for a software device include?

It includes working out your software's FDA classification, choosing the pathway (510(k), De Novo, or PMA), and writing the submission documentation and Design History File (DHF) behind it. FDA makes every classification and marketing authorization decision.

MedDev Solutions writes that documentation with your team, assembles the eSTAR package, and supports Pre-Submission (Q-Sub) meetings and responses to FDA additional information requests.

Sound familiar?

How is a consultant different if your team is still the one doing the work?

The file still has to be written. The Design History File (DHF) still needs the current version of every document your submission points to. We write the submission documentation with your team and keep the DHF in step with your software.

How we work with your team

We write. Your team decides.

We work alongside your team, not in place of it. Here is who does what, from classification to submission.

  1. 01What FDA decides

    Every classification and marketing authorization decision.

    FDA makes every classification and marketing authorization decision. Your software still needs a pathway and a file: the submission documentation and the Design History File (DHF) behind it.

  2. 02What we write

    The strategy, the rationale, and the submission documents.

    We draft the strategy, the classification rationale, and the submission documents, assemble the eSTAR package, and support Pre-Submission (Q-Sub) meetings and responses to FDA additional information requests.

  3. 03What your team owns

    Your regulatory lead reviews and owns each decision.

    Development, quality, testing, and cybersecurity feed the file through one plan, so the DHF and the software describe the same version. Your company remains the manufacturer.

What we deliver

What do we deliver: the submission, or the quality system behind it?

Your product needs a pathway and a file. Your organization needs a quality system that keeps both current. We handle the two together, for software devices.

For your submission

The pathway, the classification, and the documentation for your software device.

  • FDA classification of your software (Software as a Medical Device (SaMD) or software in a device)
  • Pathway strategy: 510(k) or De Novo
  • FDA submission documentation and your Design History File (DHF)
  • FDA, EU MDR and CE marking support

For your organization

The quality and regulatory system behind every submission you make.

  • ISO 13485 quality management system implementation
  • ISO 14971 risk management
  • Fractional Regulatory Affairs and Quality teams
  • Electronic quality management system (eQMS) and application lifecycle management (ALM) digitization
  • Regulatory due-diligence support for investors

How an engagement runs

How does an engagement run?

In five phases, from classification to post-market. Timing depends on your software, your pathway, and where you start. We scope the work with you on the first call.

  1. Classify

    We help you work out the FDA classification of your software and document the rationale.

  2. Plan

    Pathway strategy (510(k) or De Novo, plus EU MDR if you sell in the EU) and a submission plan each team can work to.

  3. Build the file

    Submission documentation and DHF, written with your team as the software and records come in.

  4. Submit and respond

    Submission support, and help preparing responses when FDA asks questions.

  5. Maintain

    Your quality system, DHF, and post-market surveillance kept current after FDA marketing authorization.

Questions we get

Regulatory FAQ

Answer

MedDev Solutions

We add the drafting capacity and the link to development, testing, and cybersecurity, so the file matches the software. Your regulatory lead owns the strategy and the decisions. We work alongside your team, not in place of it. Your company remains the manufacturer and keeps responsibility for its design controls and submission.

MedDev Solutions

Yes, for software. MedDev Solutions helps US medical device companies work out the FDA classification of their software: SaMD or software in a device. We don't classify hardware devices.

MedDev Solutions

No. Labeling and IFUs stay with your team or another provider. We cover the software, its records, and the submission documentation around it.

MedDev Solutions

FDA's Quality Management System Regulation (QMSR), aligned with ISO 13485:2016, took effect February 2, 2026. The same day, FDA stopped using the Quality System Inspection Technique (QSIT) and began inspecting under Compliance Program 7382.850. With your team, we run gap assessments of your quality system against ISO 13485:2016.

MedDev Solutions

For a 510(k), an additional information request places the submission on hold from the request date and stops the review clock. We help your team prepare a complete response.

MedDev Solutions

Yes. We provide FDA, EU MDR and CE marking support for software devices, under EU MDR 2017/745.

MedDev Solutions

No. We can't promise any regulatory outcome. FDA makes every classification and marketing authorization decision. We deliver the analysis, the plan, and the documentation, built with your team.

Something else? Ask us directly on a 30-minute call

Next step

Bring your software and your timeline.We'll map the pathway with you.

In 30 minutes, we'll walk through your software and your submission plan, and suggest a first step. FDA makes the classification decision.