Skip to content

AI agent for SaMD regulatory

An Agent built specifically to get your SaMD to market faster, and keep it compliant.

Your question opens a demo booking. We run it through the agent with you on the call.

Built around the regulations and standards your reviewer checks against

  • FDA QMSR
  • EU MDR 2017/745
  • ISO 13485
  • IEC 62304
  • ISO 14971
  • IEC 62366
  • MDCG 2019-11

How it works

From first question to submission pack

The agent takes you down the path one step at a time, and builds every document along the way.

  1. 01 · Set the objective

    Example · FDA

    We're building AI that flags suspected pneumothorax on chest X-rays. We want to sell in the US and we have no QMS.

    I've set your objective and opened a QMS workspace. Next, a few questions about the product.

    Objective
    FDA clearance
    QMS workspace
    Created
    Product profile
    In progress

    Your answers

What it builds

Every document in your submission pack

The agent writes the quality system and the technical file, for FDA, EU MDR or both.

  • One product profile, every document

    You answer once. Your intended use, risks and architecture flow into each file, so they all agree with each other.

  • Written to the standard

    Each document follows the structure its regulation or standard asks for, and shows the requirement it answers.

  • You review and approve

    Nothing goes into the pack until your team has read it and signed it off.

Submission pack

10 documents

  • Quality manual, SOPs and policies

    ISO 13485 · QMSR · FDA and EU MDR

    Drafted
  • Software lifecycle file

    IEC 62304 · FDA and EU MDR

    Drafted
  • Risk management file

    ISO 14971 · FDA and EU MDR

    Drafted
  • Usability engineering file

    IEC 62366 · FDA and EU MDR

    In review
  • Cybersecurity file

    Threat model, SBOM · FDA and EU MDR

    Needs your input
  • Labelling and instructions for use

    Label, IFU · FDA and EU MDR

    Drafted
  • Predicate comparison

    Substantial equivalence · FDA

    Drafted
  • Clinical evaluation report

    MDR Annex XIV · EU MDR

    In review
  • Post-market surveillance plan

    MDR Annex III · EU MDR

    Planned
  • GSPR checklist

    MDR Annex I · EU MDR

    Drafted

Integrations

Works with the tools you already use

The agent reads from where your product is built and files documents where your quality system lives.

  • In progress

    Greenlight Guru

    eQMS

    File approved documents into your QMS

  • In progress

    Qualio

    eQMS

    File approved documents into your QMS

  • Coming soon

    Confluence

    Docs

    Read specs and design notes

  • Coming soon

    GitHub

    Code

    Read your code, releases and SBOM

  • Coming soon

    Jira

    Tickets

    Trace requirements, tests and changes

  • Coming soon

    GitLab

    Code

    Read your code, releases and SBOM

  • Coming soon

    Google Drive

    Docs

    Read the documents you already have

  • Coming soon

    SharePoint

    Docs

    Read the documents you already have

Why an agent

Stop building your submission from blank templates.

Most teams piece a submission together from guidance PDFs, bought templates and consultant hours. Here's what changes.

Templates and consultants

  • Work out your class and pathway from guidance PDFs
  • Buy templates and fill them in by hand
  • Find the gaps when your reviewer does
  • Start again for the second regulator

With the Pathstone agent

  • A classification with the rule it's based on
  • Documents generated from your product profile
  • A gap analysis before you submit
  • One profile for FDA and EU MDR

Model v2.5 released

  • Covered by your PCCP
  • Notify Notified Body: significant change

3 documents updated for your review

After clearance

Ship a new version and stay compliant

Software changes after it's cleared. The agent keeps your file in step with your product.

  • Change impact per release

    Describe the change and see what each regulator needs: a notification, a new submission or nothing at all.

  • Documents that stay current

    The agent updates the files a change touches and flags them for your review, so you're ready for the next audit.

Next markets

Cleared once? Take it further.

Many regulators accept or rely on an FDA clearance or a CE mark. Once you have yours, the agent maps the route into 19 more markets.

  • United States

    FDA

    MDSAP

    Class I listing or 510(k) clearance

    • Class I listing
    • 510(k)
    • PCCP for AI

    Local representative: US Agent

  • Canada

    Health Canada

    MDSAP

    Medical Device Licence (Class II)

    • Class I via MDEL
    • MDL Class II
    • MDSAP certificate

    Local representative: Importer or distributor (MDEL)

  • Brazil

    ANVISA

    MDSAP

    Notificação

    • Notificação (Class I–II)
    • BGMP

    Local representative: Brazil Registration Holder

  • Mexico

    COFEPRIS

    Registro Sanitario

    • Standard registration
    • Equivalency route

    Local representative: Mexican Registration Holder

  • Argentina

    ANMAT

    ANMAT registration

    • Class I–II registration
    • GMP certificate

    Local representative: Local registration holder

  • Colombia

    INVIMA

    Registro Sanitario

    • Class I–IIa automatic
    • Class IIb

    Local representative: Local importer or registration holder

We work with Class I and Class II devices, including EU Class IIa and IIb. Pathways shown are the common routes for software at those classes. Your plan sets out the exact route for your device and claims.

Frequently asked questions

Is Pathstone a consultancy or an agency?

No. Pathstone is an AI platform: software your team uses. The agent writes and checks the documents, and your own people review, approve and submit them. There is no outsourced team of consultants doing the work.

What can I ask the agent?

Anything on the path to FDA or EU MDR: whether your software is a medical device, what class it is, which pathway fits, what a standard requires, or a first draft of a document such as a Pre-Sub question list.

We have no QMS and no documentation. Is it too early?

No. That's the starting point the agent is built for. It sets up your QMS workspace first, then builds the technical documentation on top of it.

Which devices and pathways does it cover?

Class I and Class II software as a medical device, including AI. For FDA that means Class I listings and 510(k) submissions. For EU MDR it means Class I self-declaration, and Class IIa and IIb through a Notified Body. We don't cover De Novo, PMA or Class III devices.

How do I know the answers are right?

Each answer shows the regulation, guidance or standard it's based on, so your team can check it. The gap analysis then tests every document against the requirements before you submit.

Does it replace our regulatory lead or consultant?

No. The agent does the drafting and the checking. Someone at your company reviews and approves every document, and stays accountable for it.

Does the agent submit for us?

It gets your pack ready to submit. You send it to FDA or your Notified Body, and the manufacturer stays responsible for the device.

What happens after we're cleared?

The agent keeps your file current as your software changes, and tells you what each regulator needs for a release. When you're ready for more markets, it maps the route into each one.

Ask your first question.

Bring your product and your target: FDA, EU MDR or both. We'll show you the agent working on your device.

Book a demo

You review and approve every document the agent writes.

Illustration: a globe with routes from United States to 13 other markets.

Choose which cookies we can use. You can change this at any time from the Cookie settings link in the footer.