Buyer's guide

How to Choose Post-Market Surveillance Software

By Kieran Redington, Founder of MedFortis Updated 23 October 2026 ~9 min read

Post-market surveillance software promises the same thing everywhere: stop monitoring regulators and marketplaces by hand, stay up to date automatically, and go into audits with evidence rather than anecdotes. Behind that promise, products vary a lot: in what they watch, how they prove it, and whether they'll pass your own procurement review. This guide gives you seven criteria, the warning signs, and the questions that show what a product can actually do. (Full disclosure: we make MedFortis, a product in this category. These are the criteria we think any tool, ours included, should be held to.)

First, know what you're buying

PMS software covers the external side of your surveillance obligations. It watches regulator publications, adverse-event databases and the open market, and turns what it finds into alerts and evidence. It is not a QMS. Complaint handling, CAPA, PMCF and document control stay where they are, and this software feeds them. Vendors that blur that line are usually strong on one side and vague about the other.

Base your requirements on the obligation itself. Under EU MDR Articles 83–92, your PMS system must actively and systematically collect this external data and produce a documented PMS report or PSUR from it. Whatever you buy should clearly shorten the path from "a signal exists somewhere" to "the signal is in my report, with evidence".

The seven evaluation criteria

1. Source coverage: regulators

This is where products differ most. Many tools cover the FDA only, because US data is the easiest to work with. If you sell into the UK, EU, Canada or Switzerland, FDA-only monitoring leaves known gaps. MHRA field safety notices, Health Canada recalls, Swissmedic actions and EUDAMED each publish things the FDA never will. Ask for the list of covered regulators, not the phrase "global coverage."

2. Source coverage: the open market

Recalled, diverted and investigational devices often reappear in grey-market and unauthorized listings, and no regulator watches them for you. Check which marketplaces are covered (general ones like Amazon, eBay, Walmart and Google Shopping, and medical resale sites like DotMed and LabX), and how listings are checked. Matching on titles alone buries you in false positives. Checking the images, with a confidence score, is what keeps the volume manageable.

3. Evidence trail

In an audit, "we monitor continuously" is only a claim until you can show a timestamped log. Findings should be captured soon after they're found (listings disappear fast) and hashed, and every user action should be recorded. Many auditors will have FDA 21 CFR Part 11 in mind, so ask whether the vendor claims it and ask for the evidence; a plain statement of what is and isn't covered is worth more than a badge. If evidence is a screenshot folder, keep looking.

4. Workflow as well as alerts

A feed of findings with no workflow becomes a second inbox nobody owns. Look for a triage queue with assignment, notes and status, and a list of authorized sellers so legitimate partners never get flagged. Practical device management matters too: once you have more than a handful of products, bulk import (for example from FDA GUDID by UDI) saves a lot of time.

5. Alerts and integrations

Signals should reach people where they work: notification centre, email, and webhooks or an API for pushing events into your QMS, ticketing or data warehouse. An API also protects you later: if a tool can't export your data, you can't easily leave it.

6. Security and procurement readiness

Your infosec review will ask regardless, so ask first: tenant isolation model (shared database vs isolated environment per customer), SSO (OIDC/SAML) and SCIM provisioning, MFA, role-based access, audit logging, and machine-to-machine API credentials. For device manufacturers this matters, because the data includes your product range and your problems.

7. Reporting outputs

The end product of PMS is a document: your PMSR or PSUR. A tool that produces report-ready annexes from its own data, so you don't have to export CSVs and reformat them, saves time every reporting cycle. Ask to see an actual generated output during the demo, on data resembling yours.

Red flags

Questions to ask every vendor

  1. Exactly which regulators and marketplaces do you ingest, and how often does each update?
  2. Show me a device lookup live. How current is this data, and does it come from your own store or is it scraped on demand?
  3. How is a marketplace listing verified as my device rather than a keyword match?
  4. Walk me through one finding end to end: detection → triage → evidence → takedown/report.
  5. What exactly is preserved per finding, and how would I prove its integrity to an auditor two years later?
  6. What's your tenant isolation model? SSO/SCIM/MFA? Can I see the audit log?
  7. Generate a PSUR-ready annex in front of me. What manual work remains after this?
  8. How do I get my data out: full export, API, or both?
The strongest demo request: ask the vendor to run the tool on your actual device lines before you commit to anything. A vendor confident in its coverage will show you your own data. One who insists on canned demo data is telling you something. (That's what our free demo does, and any good competitor should offer the same.)

The evaluation checklist

CriterionMinimumStrong
Regulator coverageFDA (MAUDE, recalls)+ MHRA, Health Canada, Swissmedic, EUDAMED and further national sources
Open marketeBay keyword search+ Amazon, Walmart, Google Shopping, DotMed, LabX; AI image verification; seller networks
EvidenceFindings storedScreenshot and page copy captured shortly after detection, each hashed, with a full audit trail
WorkflowAlert listTriage queue, assignment, whitelisting, GUDID/UDI bulk import
IntegrationsEmail alerts+ Notification centre, webhooks, API, data export
SecurityPassword loginIsolated environment per customer, OIDC SSO, SCIM, MFA, RBAC, audit log
ReportingCSV exportOn-demand PMS/PSUR-ready annexes

Score honestly against the "strong" column, weight it by your own situation (markets, number of devices, exposure to resale), and ask every vendor, us included, to show you rather than tell you. For grounding on the underlying data sources themselves, our guides to FDA MAUDE and the regulators beyond the FDA cover what each one publishes and where the manual workflows break down.

Try us first, on your own devices

A free MedFortis demo runs the checklist's hardest test for you: a live lookup across regulator sources plus the resale market, on your actual device lines, in 30 minutes.

Book a Demo →

Key takeaways

  • PMS software covers the external side of surveillance. It feeds your QMS rather than replacing it.
  • The seven criteria: regulator coverage, open-market coverage, evidence trail, workflow, integrations, security and reporting outputs.
  • Products differ most on coverage of several regulators (rather than the FDA alone) and keeping evidence (rather than just sending alerts).
  • Warning signs: "global coverage" with no source list, lookups scraped live, no capture when something is found, and compliance badges nobody can back up.
  • Ask every vendor to run their tool on your device lines before you commit.
This article is provided for general information only and is not legal, regulatory or procurement advice. MedFortis is a product in the category discussed; we've disclosed that throughout and encourage you to apply every criterion in this guide to our product as strictly as to any other.