FDA readiness for software medical devices

You shouldn't have to manage five teams to submit one product.

One team inside yours across development, quality, regulatory, testing, and cybersecurity. We do the work, not just the advice, through FDA submission.

Built for software: Software as a Medical Device (SaMD), software in a device, embedded firmware, and AI-enabled device software.

16

years of our team's experience in software-driven MedTech, in Israel and now the US

1,000+

submissions and projects delivered globally by our group, including our Israel company, MedDev Soft

Standards we help clients work to

  • IEC 62304
  • ISO 13485
  • ISO 14971
  • IEC 81001-5-1
  • ISO/IEC 42001

Regulatory from day one

Regulatory starts before development, and stays through post-market.

  1. Strategy

    Before development

    Regulatory pathway across 510(k), De Novo and Premarket Approval (PMA), Pre-Submission (Q-Sub) meetings, quality management system (QMS) setup, and, for teams building AI-enabled device software, ISO/IEC 42001 implementation and EU AI Act readiness.

    Regulatory pathway
  2. Development

    While the code is written

    IEC 62304 development with secure-by-design practices and ISO 14971 risk management. Requirements, risk controls, and tests traced end to end.

    IEC 62304 records
  3. Submission

    When the file comes together

    Verification and validation (V&V), traceability, and electronic Submission Template And Resource (eSTAR) package assembly: software, V&V, risk, and cybersecurity sections.

    eSTAR package
  4. Post-market

    After launch

    Post-market surveillance, sustaining software engineering, and AI/ML changes managed through a Predetermined Change Control Plan (PCCP).

    PCCP

Your company remains the manufacturer and keeps responsibility for its design controls and submission.

How we work

One plan. Every handoff traced, from code to test evidence.

  1. 01Working apart

    Five teams, five plans, and you in the middle.

  2. 02Handoffs mapped

    Every handoff is mapped, from one function to the next.

  3. 03One plan

    Five functions run from one plan.

  4. 04Submission file

    A submission file that builds as the work happens.

Bring your submission plan. We'll look at the handoffs with you.

Sound familiar?

Same handoff.A very different week.

You're tired of being the project manager between five different departments.

The handoffCode to records

Without one team
  • Development closes tickets while regulatory waits for records.
  • Each fix lands on your calendar.
With one team
  • Requirements, code, and IEC 62304 records written as one set.
  • One team coordinates the handoff, inside your program.

The handoffTesting to cybersecurity

Without one team
  • Testing and cybersecurity run their own plans.
  • Cybersecurity findings arrive after testing is done.
With one team
  • Threat model, cybersecurity risk assessment, Software Bill of Materials (SBOM), and testing documentation that trace to each other.
  • The evidence from your security testing, documented for your submission.

Submission file

Watch the submission file build.

Diagram, not product software: SRS, code, test report and risk file build the DHF, then the eSTAR software, V&V, risk and cybersecurity sections fill.

What we deliver

Pick the piece you're missing. We connect it to the rest.

FDA Cybersecurity

Premarket cybersecurity documentation a reviewer can trace.

Threat modeling · Cybersecurity risk analysis · Premarket cybersecurity documentation, including your security testing evidence

See cybersecurity services

AI/ML Device Compliance

A PCCP that sets out which model changes you plan, and how each one is validated.

Alignment with FDA guidance for AI-enabled device software · ISO/IEC 42001 implementation · Predetermined Change Control Plans (PCCP)

See AI/ML compliance services

Software Development & IEC 62304 SQA

Requirements, risk, and tests traced in one IEC 62304 documentation set.

IEC 62304 software development · Software quality assurance (SQA) · Verification and validation (V&V) for SaMD and embedded firmware

See software and SQA services

Regulatory Strategy & Submissions

An eSTAR package with its software, V&V, risk, and cybersecurity sections assembled.

Software classification · 510(k) and De Novo submissions · Design History File (DHF) · Fractional Regulatory Affairs and Quality teams

See regulatory services

Free checklist

Five handoffs to own before your FDA submission

The handoffs between your five functions, in one checklist you can run with your team.

  • Code to records
  • Records to test evidence
  • and three more

Questions we get

Before you book the call

Answer

MedDev Solutions

Your team knows the product, and they stay at the center of it. We add specialists where you're thin, such as cybersecurity or IEC 62304 documentation.

MedDev Solutions

Most consultants hand you a gap list. We close it: we write the documents, build and test the software, and prepare the cybersecurity documentation, including the evidence from your security testing. Your team reviews and owns the result.

MedDev Solutions

We integrate. We work inside your program, toward your submission plan.

See how the Integrated Submission Program works

MedDev Solutions

We'll scope and price the first step with you on a call.

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

Next step

One team inside yours.Through FDA submission.

Early R&D or close to submission: in 30 minutes, we'll look at where your program stands and which handoffs need an owner.