U.S. / FDAMaster research guideAs of: 2026-05-22

What should a foreign manufacturer prepare before U.S. medical device market entry?

A foreign medical device manufacturer planning U.S. market entry should prepare six blocks of evidence before engaging a regulatory consultant or filing with FDA. As of 2026-05-22, those blocks are: (1) a written product description and intended-use statement; (2) candidate FDA product-code and device-classification clues; (3) a candidate predicate shortlist and similar-device landscape; (4) a public safety-history scan covering similar devices; (5) a forms / fees / eSTAR / typical review-timeline reference card; and (6) a consultant brief that hands the above to a qualified RA/QA professional or regulatory consultant. Final classification, submission pathway, predicate selection, U.S. agent appointment, and licence eligibility decisions belong to your RA/QA team or qualified consultant in consultation with FDA. This guide prepares the inputs, not the determinations.

For founders, manufacturers, RA/QA teams, and regulatory consultants. For RA/QA or consultant review.

This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, compliance, safety, or effectiveness. We prepare a source-backed evidence pack from public FDA sources so qualified RA/QA professionals or regulatory consultants can review and decide.

1. Device description and intended use

Every downstream artifact depends on a clear, written product description and an unambiguous intended-use statement. FDA reads both at the start of any submission. The description should cover: device type, principle of operation, energy used, materials, components, accessories, and any accompanying software. The intended-use statement should name the intended population, intended user, intended environment of use, and intended clinical purpose.

What this surfaces: a regulatory-language product profile that grounds all subsequent research and that a consultant can review on first reading.

2. FDA product code and classification clues

FDA Product Classification maps a device description to one or more candidate three-letter product codes. Each code is tied to a 21 CFR regulation citation, a device class (I, II, or III), and a review panel. The candidate code is the entry point for similar-device research, for pathway-clue research, and for recognized-standards research.

Multiple candidate codes often apply, especially for novel or multi-modal devices. The right discipline is to capture all plausible candidates as candidate clues and let RA/QA or a qualified consultant narrow them with FDA input — through a Pre-Submission (Q-Sub) where helpful.

What this surfaces: candidate FDA product codes, candidate device-class clues, and the CFR section that governs each candidate.

3. Similar-device landscape and candidate predicate research

With candidate product codes in hand, the FDA 510(k) database and PMA database surface devices already authorized in those codes. The output of this step is a candidate predicate shortlist — direct similar products and indirect similar products — with K-numbers, applicants, decision dates, and notes on technological characteristics.

A structured similar-product comparison table is the artifact that survives into the consultant conversation. It is not a substantial-equivalence determination — that is FDA's call. It is the source-cited input that makes the substantial-equivalence argument easier to build.

For the step-by-step database workflow, see our FDA 510(k) similar-device research workflow.

4. Public safety-history scan

FDA MAUDE (voluntary adverse event reports), FDA Recalls, FDA Warning Letters, FDA Safety Communications, and FDA Import Alerts are the public surfaces for safety and enforcement history on similar devices. Reading them as a category — not just for the candidate predicate, but for the broader product family — surfaces failure modes, common labelling issues, and recurring inspection findings.

Two cautions. First: MAUDE counts are not incidence rates; reports are voluntary and unverified. Second: absence statements must be scoped and dated. "No open warning letters found for manufacturer X in covered sources as of 2026-05-22" is the right shape.

What this surfaces: candidate review points for design, risk management, verification & validation, usability, labelling, cybersecurity, and PMS planning — each tied back to a public record.

5. User fees, forms, eSTAR, and consultant brief preparation

FDA publishes annual MDUFA user-fee schedules with separate standard and Small Business Determination (SBD) fee tiers. FDA also publishes guidance documents and Recognized Consensus Standards databases that vary by device category. Most 510(k) and De Novo submissions are now filed using eSTAR — FDA's interactive PDF submission template — which structures the submission contents at the point of authoring.

A reference card that pulls together the current-year fee, the relevant forms, eSTAR references, the candidate guidance documents, the candidate recognized standards, and FDA's published MDUFA performance goals is the simplest way to keep this surface visible across the submission-planning phase. Reference-card numbers are dated; confirm against fda.gov before budgeting or scheduling.

What this surfaces: a dated reference card so the consultant brief — and the founder budget — start from current data.

What TrueMedDevice prepares

The U.S. / FDA Market-Entry Product Evidence Pack delivers the research above as a source-cited artifact. Each item below is shipped as part of the pack:

✓FDA-style product regulatory-language profile (intended use, indications, users, environment, technological characteristics)
✓Candidate FDA product-code / regulation / class / pathway clues drawn from public FDA data
✓Direct and indirect similar-product comparison with K-numbers, applicants, decision dates
✓Public safety-history scan (MAUDE themes, FDA recalls, FDA Warning Letters, FDA Safety Communications, Import Alerts) — scoped and dated
✓FDA forms / fees / eSTAR / guidance / recognized consensus standards reference card (dated)
✓Preparation gap checklist for design, risk, verification, usability, labeling, cybersecurity, sterility, biocompatibility, clinical, and performance evidence categories
✓Source ledger — every claim cited to a public FDA record with access date
✓Consultant briefing sheet — structured for handoff to qualified RA/QA or regulatory consultant

What must still be reviewed by qualified RA/QA or consultants

The pack is research preparation, not regulatory determination. Every item below remains a judgment call made by your RA/QA team or qualified consultant in consultation with FDA:

→Final device classification (Class I, II, or III)
→Final submission pathway (510(k), De Novo, PMA, or 510(k)-exempt)
→Predicate selection and the substantial-equivalence argument
→U.S. agent appointment for foreign manufacturers
→Whether to file a Pre-Submission (Q-Sub) before the formal 510(k)
→Quality-system scope and conformance evidence
→Standards applicability, testing plan, and study design
→Labelling claims, IFU language, and marketing-material review
→Inspection-readiness posture and field-action policy

This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, compliance, safety, or effectiveness. We prepare a source-backed evidence pack from public FDA sources so qualified RA/QA professionals or regulatory consultants can review and decide.

Related research

Frequently asked questions

What is a predicate device?

A predicate device is a U.S. medical device that has already been cleared by FDA via the 510(k) pathway, and that a manufacturer cites in a new 510(k) submission to argue that their device is similar enough to be cleared on the same basis. Predicate selection is the manufacturer's strategic decision, made with RA/QA and consultant input. This guide shows how to surface candidate predicate devices from public FDA data — it does not select the predicate for you and does not determine substantial equivalence.

What's the difference between FDA-cleared and FDA-approved?

"FDA-cleared" refers to devices that have been authorized via the 510(k) pathway based on substantial equivalence to a predicate device. "FDA-approved" is reserved for Class III devices authorized via the Premarket Approval (PMA) pathway. Most marketed medical devices are cleared, not approved. Using "FDA-approved" to describe a 510(k) device is a factual error.

Do I need a U.S. agent if I'm a foreign manufacturer?

FDA requires every foreign establishment that imports or offers for import medical devices into the U.S. to designate a U.S. agent. The U.S. agent is the formal communication channel between FDA and the foreign establishment for routine and emergency communications. U.S. agent selection is the manufacturer's decision; this guide surfaces the obligation context from public FDA sources for RA/QA or consultant review.

How do I search the FDA 510(k) database?

The FDA 510(k) database lives at accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm. Search by applicant, device name, 510(k) number, product code, decision date, or several other fields. The openFDA API at api.fda.gov also provides programmatic access. See our FDA 510(k) Similar-Device Research Workflow insight for a step-by-step walk-through.

What evidence should I bring to a regulatory consultant?

Before a paid consultant call, gather: (1) a written intended-use statement, (2) candidate FDA product-code clues with sources, (3) candidate submission-pathway clues with rationale, (4) a candidate predicate shortlist with K-numbers, (5) a safety-history scan of similar devices (MAUDE, recalls, warning letters), and (6) a forms / fees / typical review-timeline reference. The Product Evidence Pack delivers each of these as a source-cited artifact. Classification, pathway, predicate selection, and submission strategy decisions remain with your RA/QA team or qualified consultant.

Want this research run on your product?

The U.S. / FDA Market-Entry Product Evidence Pack delivers the workflow above — product profile, candidate product-code and pathway clues, similar-product comparison with candidate predicate shortlist, safety-history scan, forms/fees/timeline reference, source ledger, and consultant briefing sheet — as a source-cited artifact for qualified RA/QA or consultant review.

See the U.S. / FDA Market-Entry Product Evidence Pack