FDA Market-Entry Product ID Sample

1. What the team starts with

ExampleCo describes its idea in plain commercial / engineering language: “A wearable, non-invasive single-lead cardiac activity monitor with a companion mobile app that summarises a multi-day recording window for clinician review.” This is a clear product story for a customer or investor. It is not yet a regulatory-language Product ID an FDA reviewer or consultant can work with.

2. Regulatory-language Product ID profile

The pack translates the commercial description into the language FDA and qualified RA/QA reviewers actually use.

3. Candidate market-entry pathway map

Every item below is a candidate review clue for the qualified RA/QA reviewer or consultant. None is a pathway determination by TrueMedDevice.

• Candidate pathway context

  Public-record review of how similar cardiac activity monitors have historically reached the U.S. market — most often via 510(k) substantial equivalence, with De Novo as a candidate clue when no suitable predicate is identified. Pathway determination is the FDA's, not TrueMedDevice's.

• Forms and submission artefacts

  Candidate forms, fees, eSTAR template references, and submission-preparation checklist excerpted from public FDA guidance. The pack lists each form by name and links to its FDA source page.

• Fee schedule

  Public FDA user fee references for the relevant fiscal year — small-business eligibility flagged so the qualified RA/QA reviewer can confirm and apply.

• Timeline expectations (high-level)

  Public-record review-time medians for the relevant product family in recent fiscal years, sourced from FDA performance reports. Not a commitment from TrueMedDevice or FDA.

• Standards landscape

  FDA-recognized consensus standards likely to apply to the product family, organized so the qualified reviewer can pull the standard and assess gaps. Each standard is named with its FDA recognition number when known.

4. Similar product landscape

Each row of a real pack carries a source URL into the FDA 510(k), De Novo, or PMA database. The rows below are illustrative placeholders so the buyer can see the shape — the paid pack replaces them with source-linked rows for the buyer’s actual predicate set.

5. Public safety signal starter map

Categories of public record the pack sweeps for predicate-family evidence. Real packs include source-linked findings, not just categories.

• FDA Recalls (Enforcement Reports)

  Sweep for predicate-family recalls in the last five years — root cause, status, and source URL per row in the paid pack.

• MAUDE adverse event reports

  Predicate-family event-type breakdown over the last five years, with verbatim public reason text for review-relevant rows. MAUDE is subject to substantial under-reporting and is not an incidence rate.

• FDA Warning Letters

  Manufacturer-level and category-level warning letters in the last five years, with the regulator's stated observations.

• Safety Communications and Public Notices

  FDA Safety Communications and Public Health Notices that name the product family or its components.

• Recognized standards drift

  Changes to FDA-recognized consensus standards that touch the product family — flagged for qualified standards review.

6. Questions to ask your RA/QA reviewer or consultant

• What product code does the qualified RA/QA reviewer believe applies, and what is the public basis for that view?
• Which of the candidate predicates is closest to ExampleCo's intended use, indications, technology, and use environment — and where do material differences exist?
• Which FDA-recognized consensus standards must be addressed to support the comparison to each candidate predicate?
• What recall, MAUDE, warning-letter, and Safety Communication themes from the predicate family must be addressed in the design history file or risk management file?
• What submission-preparation work is required before an eSTAR draft is ready — testing, labeling, instructions for use, human-factors plan, cybersecurity plan, SaMD documentation?
• Which open questions remain unanswered and require qualified RA/QA or consultant judgment before any submission decision is made?

7. What the buyer gets

• Regulatory-language Product ID profile (intended use, indications, environment, user type, technology characteristics, candidate classification / product-code clues for qualified review).
• Candidate market-entry pathway map (510(k) / De Novo / PMA context as candidate review clues only — not a pathway determination), forms, fees, eSTAR preparation checklist, and public-record timeline expectations.
• Similar-product landscape table — predicate candidates, manufacturers, clearance / licence dates, and source URLs.
• Public safety signal starter map across recalls, MAUDE events, warning letters, and Safety Communications.
• Candidate review-point list — questions for the qualified RA/QA reviewer or consultant.
• Source ledger — every row's source URL recorded for verification.
• Consultant briefing sheet — a one-page summary your RA/QA or external consultant can read before judgement work begins.
• Optional: monthly Product ID workspace for follow-up questions and signal refresh, anchored to the same Product ID file.