Regulatory Services
Every medical device program carries regulatory risks: classification uncertainty, predicate selection vulnerabilities, data package gaps, and submission timing dependencies. A regulatory risk assessment maps these risks before the development program is designed around assumptions that haven't been validated with FDA.
Assess Your Regulatory RiskRisk Mapping
The regulatory pathway for a medical device — 510(k), De Novo, or PMA — determines the review standard, the type of evidence required, the development timeline, and ultimately the time-to-market. Getting the pathway wrong, or discovering mid-development that the assumed pathway is unavailable, is one of the costliest regulatory mistakes a device company can make. Classification risk — the probability that FDA will classify the device differently than the company assumed — is the upstream driver of pathway risk.
Classification risk is not always obvious. A device that appears to fall into an existing 510(k)-eligible product code may have a technological characteristic or intended use that FDA would view as requiring a De Novo or PMA pathway. FDA's 510(k) review database is the most reliable source of information about how the agency has treated similar devices — but interpreting that database requires understanding what was actually cleared and why, not just what the product code says. We analyze the clearance history for the relevant device category and identify the risks that exist for the specific device and intended use before a pathway is selected.
A 510(k) submission rises or falls on predicate selection. The predicate must be legally marketed, have a substantially equivalent intended use to the subject device, have the same or different technological characteristics that don't raise new questions of safety and effectiveness. A predicate that is technically legally marketed but that was cleared under circumstances FDA now considers inadequate, or that has since been voluntarily recalled or had its clearance order rescinded, creates a substantial equivalence argument FDA may not accept.
We analyze the predicate landscape for every 510(k) program at the outset — reviewing the predicate's clearance history, any post-clearance FDA actions, the technological characteristics comparison, and the adequacy of the predicate's performance data as a benchmark for the subject device's test requirements. Predicate selection risk is identified and mitigated before submission, not discovered in an FDA deficiency letter.
A regulatory risk assessment maps the data package requirements for the device's classification and intended use against the data the development program is planned to generate. The gap between what FDA will expect and what the current plan will produce is the data package risk. For 510(k) devices, this includes biocompatibility, electrical safety, EMC, sterility validation, performance testing, and HFE as applicable. For PMA devices, the data requirements are device-specific and extensively guided by FDA's device-specific PMA guidance documents. Identifying data package gaps at program initiation — when filling them is still part of the program plan — is far less expensive than discovering them after the development program is complete.
A regulatory risk assessment evaluates the likely FDA pathway for your device — classification, submission type, required data, and timeline risk. It is most useful at the start of development or when considering a new indication, design change, or market expansion.
We assess: likely FDA device classification (Class I, II, III), applicable submission type (510(k), De Novo, PMA, or exempt), predicate availability, required testing, estimated timeline, and known regulatory risks specific to your device type and intended use.
No. A regulatory risk assessment is an internal strategic document we prepare for your team. A Q-Sub is a formal submission to FDA requesting their written feedback. We typically recommend starting with our assessment, then using it to formulate targeted Q-Sub questions.
Get Started
The most expensive regulatory risks are the ones discovered after the development program is designed around them. We map regulatory risk at program initiation so your development plan is built on validated assumptions.