Start hereClassify the device and determine route
~246 days leftOpen step
Guide library
Authorization North America

FDA medical devices

U.S. medical device market entry · 510(k), De Novo and PMA

Classify a medical device, select the right submission pathway and assemble the evidence package.

Who it applies to

Manufacturers and sponsors planning to market a medical device in the United States. Device classification and intended use determine the pathway.

What you’ll produce

Applicable clearance, De Novo classification, PMA approval or documented exemption.

FDA days can exclude time on hold for sponsor responses. QMSR obligations and any applicable exemptions must be evaluated independently of the submission route.

Check FDA outcome rates and fees Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which use and claims are we funding?
Have Regulatory, Clinical and Product sign off on intended use, indications, user and patient population. Confirm the proposed pathway against FDA classification and precedent before funding expensive studies.
Which evidence could move the launch date?
Build the budget from protocols, lab lead times, external testing, submission fees and possible follow-up studies. Check small business status and timing where relevant. Plan for sponsor-response time while FDA review is on hold.
Who can change the tested version?
Name Regulatory Affairs as submission lead and Quality as version and change owner. Require approval before changing labeling, materials, software or intended use after test planning.

How to spend the first week

  1. Bring the draft labeling, device description and configuration, markets, proposed claims, the current risk file and public regulatory records for comparable devices.
  2. Build a route memo and a claim-to-evidence matrix. Find the questions that could invalidate the proposed route or test design, and decide whether to use FDA’s Q-Submission process.
  3. Ask Quality, Engineering, Clinical and Regulatory to agree who owns protocols, device version, lot traceability, submissions and postmarket handoff.

What to review each week

Track claims with approved evidence, protocols awaiting agreement, deviations affecting the tested configuration, FDA requests due and unresolved launch conditions.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

FDA medical devices kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Classify the device and determine route · Regulatory affairs [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Bring the draft labeling, device description and configuration, markets, proposed claims, the current risk file and public regulatory records for comparable devices.
2. Build a route memo and a claim-to-evidence matrix. Find the questions that could invalidate the proposed route or test design, and decide whether to use FDA’s Q-Submission process.
3. Ask Quality, Engineering, Clinical and Regulatory to agree who owns protocols, device version, lot traceability, submissions and postmarket handoff.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • What device claim and intended use are you asking FDA to review?
  • If pursuing 510(k), what makes the predicate appropriate, and what differences need evidence?

Worked scenario

A device team drafts a broader label after its main performance study. Regulatory affairs checks whether the study actually supports the new claim before locking the submission and coordinating further evidence.

What to read next

  • ISO 13485

    Build quality system evidence and reconcile the applicable QMSR obligations.

  • EU medical devices

    Plan separate classification and conformity work for the EU market.

FROM THE SOURCE

Cases and numbers

Published FDA classification · 5 November 2026

FDA classifies an AI-assisted cytology imaging system

FDA classified a digital cervical cytology slide imaging system with an artificial intelligence algorithm into class II with special controls. The rule identifies the device type and controls for that classification.

What to check Use a classification decision to compare intended use, technology and special controls. Record differences so the regulatory team can assess what evidence they change.

FDA classification rule 2026-22593 (opens in a new tab)

FDA performance report · FY 2026

951 of 964Substantially equivalent among SE or NSE decisions reported through Q3

Read decisions in the context of an open cohort

The preliminary cohort excludes submissions still under review, withdrawals and other dispositions from the SE/NSE decision denominator.

What to check Use 510(k) outcome data as background. Base your submission plan on the predicate comparison, testing and clearance route for your device.

FDA MDUFA report, Table 6.6 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
Test this project’s launch date Practice reviewing an evidence packet
The whole journeyabout 246 days across 4 steps
  1. 01Classify the device and determine routeRegulatory affairs · ~21 days
  2. 02Agree the evidence strategyRegulatory + clinical + quality · ~45 days
  3. 03Generate evidence and compile dossierEngineering + clinical + quality · ~90 days
  4. 04Manage review and postmarket controlsRegulatory affairs + postmarket lead · ~90 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 13 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Classify the device and determine routeRegulatory affairsBefore study designSet a start dateClassification memo; Predicate search; Submission strategyOpen
Agree the evidence strategyRegulatory + clinical + qualityBefore tests or studiesSet a start dateTesting matrix; Study protocols; FDA feedback recordOpen
Generate evidence and compile dossierEngineering + clinical + qualityBefore submissionSet a start dateTest reports; Risk file; Labeling; Submission dossierOpen
Manage review and postmarket controlsRegulatory affairs + postmarket leadFDA clock and ongoing obligationsSet a start dateFDA decision; Registration/listing record; Postmarket planOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Classify the device and determine route

    Who Regulatory affairs When Before study design

    Lock intended use and indications. Identify classification and product code, exemptions or appropriate predicate. Compare 510(k), De Novo and PMA routes.

    How to do this step

    Before you start

    Intended use, patient and user populations, use environment, draft indications and design description.

    1. Search the FDA classification and decision databases using candidate product codes. Save search terms, dates, records and reasons the results fit or do not fit.
    2. For a 510(k) hypothesis, compare intended use and technological characteristics against a legally marketed predicate. Identify differences and their safety and effectiveness implications.
    3. Write the route decision and unresolved questions. Include Quality’s assessment of manufacturing and postmarket obligations so leadership can estimate the full launch work.

    What a reviewer should see

    A predicate comparison names the record, identifies differences and ties each difference to an evidence question and owner.

    When to escalate

    Raise a novel intended use, no defensible predicate or conflicting classifications before committing to a 510(k) budget.

    What to produce

    Classification memoSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Predicate searchSpreadsheet

    Gather first

    • Device intended use, indications and design
    • FDA classification and public 510(k) databases
    • Relevant technological characteristics and differences

    How to prepare it

    1. Search by device name, intended use and product code. Save the query, date and candidate identifiers.
    2. Compare indications, technology and risk differences using public summaries and official records. Record which differences need testing and why a candidate was kept or dropped.
    3. Have regulatory affairs verify eligibility and the proposed comparison before relying on a predicate. Keep a search trail even when the route changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Search inputs
    Intended use and proposed product code from the regulatory strategy
    Candidate identifier
    Enter verified 510(k) number from FDA database.
    Comparison
    Compare indications first, then power, materials, software and performance.
    Difference and evidence
    New battery design. Electrical testing and risk rationale required.
    Decision and owner
    Regulatory affairs to confirm before protocol freeze.

    Check before handing it over

    Each candidate references a real FDA record and eligibility is documented separately from technical similarity.

    Give the comparison and open evidence questions to the regulatory and test owners.

    Submission strategyMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

  2. 02

    Agree the evidence strategy

    Who Regulatory + clinical + quality When Before tests or studies

    Map performance, biocompatibility, software, cybersecurity and clinical evidence where applicable. Consider Q-Submission feedback and IDE requirements.

    How to do this step

    Before you start

    Classification memo, hazard analysis, draft claims, relevant FDA guidance, candidate test standards and configuration.

    1. Build one matrix linking each claim and foreseeable risk to protocol, acceptance criteria, specimen version and responsible lab or team.
    2. Set measurable endpoints and acceptance criteria before testing. Document the rationale for sample size and worst-case configurations with the relevant experts.
    3. If you request a Q-Submission discussion, ask focused questions that will change a decision. Record feedback, what changed and which points still need resolution.

    What a reviewer should see

    An accuracy claim points to a protocol with the measurement range, acceptance criterion, selected units, reporting format and accountable reviewer.

    When to escalate

    Escalate conflicting criteria, a protocol based on an unrepresentative configuration or a study whose outcome cannot support the claim.

    What to produce

    Testing matrixSpreadsheet

    Gather first

    • Intended use, labeling claims and design inputs
    • Current risk file and applicable guidance
    • Design baselines, protocols and qualified lab or team
    • Acceptance criteria and sample rationale

    How to prepare it

    1. Create a row for each claim and each risk control needing verification. Record the requirement ID, expected measured result, relevant configuration and owner before testing.
    2. Link the signed protocol and justify the sample and test conditions, including relevant worst cases. Record exact hardware, firmware, lot, equipment and environmental conditions at execution.
    3. Enter the observed result, raw data, deviations and report revision. Link failed attempts and approved justification for any retest. Have Quality cross-check the submission and labeling against the agreed configuration.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Claim and risk reference
    DI-042, low-power alert appears before measurement stops. Risk RM-017, missed low-power condition during monitoring.
    Approved protocol and version
    VP-014 Rev C, hardware H2.1 and firmware 1.4.2. Test at the low end of operating temperature and maximum configured sampling rate.
    Acceptance criterion
    Fictional design input: Every test unit displays and logs the alert at least 10 minutes before it can no longer take readings.
    Test sample and justification
    Eight devices from two pilot lots. Protocol sample rationale S-014 addresses unit variation for this verification. Lot IDs and calibration records are listed in the protocol.
    Observed result and disposition
    8 of 8 units showed the alert 13.2 to 15.1 minutes before measurement stopped. PASS for this criterion. No protocol deviations.
    Evidence and release owner
    Signed report VR-014 Rev A, timestamps in RAW-014.csv and instrument record CAL-09. Quality signed review on 2026-10-15. Regulatory mapped the result to the labeling claim.

    Check before handing it over

    The signed protocol, exact device version, raw measurements and report support the same conclusion. The sample, criteria and results are specific to the device and its risks.

    Quality releases the final evidence. Regulatory links the accepted report and rationale to the applicable submission sections.

    Study protocolsSpreadsheet

    Gather first

    • Product claims and risk file
    • Applicable standards, study design and acceptance evidence
    • Design configuration and test facilities

    How to prepare it

    1. Trace each claim and risk control to a test objective and acceptance criterion. Specify units, sample rationale, version and worst-case configurations.
    2. Write the method and expected evidence before testing. Assign approvals and record protocol deviations and their effects.
    3. Compare results to the criteria. Keep failed cases, raw data and rationale for repeat testing. Link the approved reports back to the requirements.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or claim
    Battery alert appears before the device can no longer capture readings.
    Protocol and design
    TR-014, test the production hardware and locked firmware at worst-case temperature.
    Acceptance criteria
    Use the limits approved in the design input before testing.
    Sample and method
    Record sample sizes, lot IDs, conditions and operator.
    Result and evidence
    Link signed protocol, raw output and approved report.

    Check before handing it over

    Every essential claim and risk control has evidence or a documented justification for the gap.

    Give the approved protocol to the testing team and the traceability matrix to the submission owner.

    FDA feedback recordMemo

    Gather first

    • FDA correspondence and meeting materials
    • Current device and study version
    • Regulatory strategy and open questions

    How to prepare it

    1. Link each question to what was submitted and keep the exact written feedback or meeting minutes in the project record.
    2. Summarize what the feedback changes in scope, design or tests. Mark unresolved issues, who owns them and when you will confirm them.
    3. Reconcile planned changes against the approved protocol and submission strategy. Refine or request further feedback where needed.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Interaction reference
    FDA meeting or correspondence ID and date
    Question
    Is the proposed worst-case test configuration appropriate for the intended use?
    Feedback summary
    Enter a faithful summary with reference to the official written response.
    Impact and action
    Regulatory and engineering review protocol TR-014 before freeze.
    Decision status
    Open until the protocol and rationale are approved.

    Check before handing it over

    Each decision cites the actual feedback and identifies what remains open.

    Send action items to the affected technical owners and keep the official correspondence with the submission file.

  3. 03

    Generate evidence and compile dossier

    Who Engineering + clinical + quality When Before submission

    Execute validation under controlled conditions, document deviations, finalize labeling and prepare the pathway-specific submission format.

    How to do this step

    Before you start

    Approved protocols, controlled drawings and versions, risk file, final test reports and labeling draft.

    1. Check each report against the protocol, tested device and preapproved acceptance criteria. Have Quality record deviations, impact and any repeat or additional testing.
    2. Walk from the intended use and claims through risk controls, verification and the matching sections of the submission. Resolve mismatched version numbers or claims before submission.
    3. Use the current required submission format for the selected route. For an eSTAR submission, have a second reviewer validate responses, relevant attachments and completion before uploading through the required channel.

    What a reviewer should see

    The dossier crosswalk links each claim and material risk to an actual report and location. The submission copy and receipt have a version and secure home.

    When to escalate

    Do not release a package whose reports, labeling and submission identify different device configurations without documented reconciliation and Regulatory approval.

    What to produce

    Test reportsMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Risk fileSpreadsheet

    Gather first

    • Intended use, use environment and product architecture
    • Hazards, complaints and design inputs
    • Approved risk method and verification evidence

    How to prepare it

    1. Describe the sequence from hazard through hazardous situation to possible harm. Apply the approved risk criteria and record the original and residual risk.
    2. Select controls in the required order. Trace each control to design requirements and verification, while considering new risks introduced by the control.
    3. Obtain the required risk decisions and update the file from complaints, field data and substantial design changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Hazard sequence
    Battery depletion interrupts capture during home use.
    Possible harm
    A needed reading is unavailable to the user.
    Control and requirement
    Show an early low-charge warning and preserve the last completed reading.
    Verification evidence
    TR-014 worst-case battery testing and UI review
    Residual risk and action
    Record decision under the approved risk method. Monitor postmarket reports.

    Check before handing it over

    Each control traces to a test or review and residual risk is resolved through the documented approval route.

    Give the approved file to quality, product engineering and the submission or conformity lead.

    LabelingMemo

    Gather first

    • Approved intended use and indications
    • Risk controls, warnings and test evidence
    • Labeling rules, markets and device configuration

    How to prepare it

    1. List the required label locations and formats for the product, packaging, instructions and software. Pull claims and warnings from the approved regulatory and risk files.
    2. Check language, symbol, version and identification requirements in each market. Route clinical, usability and regulatory review and reconcile changes to the design.
    3. Proof the production art or software screens, approve the exact version and retain a copy with the submission and release records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Label location
    Device instructions for use
    Claim or control
    Explain when a low-charge warning appears and what action the user should take.
    Supporting evidence
    Approved intended use, risk control R-014 and usability review
    Version and market
    IFU v3, applicable market and language versions listed
    Approval
    Regulatory and quality approval before release

    Check before handing it over

    The production artifact agrees with the intended use and evidence. Warnings and symbols are consistent across channels.

    Give the approved labeling files and control history to manufacturing, release and regulatory teams.

    Submission dossierMemo

    Gather first

    • Confirmed FDA submission pathway
    • Current FDA submission instructions and template
    • Approved design, risk, testing, clinical, software and labeling records as applicable

    How to prepare it

    1. Confirm the submission route, current eSTAR requirement or permitted alternative and relevant guidance. List each section and technical reviewer before assembling files.
    2. Map intended use and claims to risk controls and evidence. Use the same device description, configurations and revision across the application, tests and proposed labeling.
    3. Run the applicable template validation and internal completeness review. Ask regulatory affairs to submit through the accepted channel and retain the submitted copy and tracking receipt.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Path and product code
    Enter the confirmed path and FDA product code.
    Reviewed evidence section
    Performance test TR-014 supports the low-charge alert claim.
    Version consistency
    Same locked firmware and device configuration in labeling and test report.
    Acceptance or readiness check
    Check all required fields and attachments in the current applicable template.
    Owner and receipt
    Regulatory affairs submits. Record tracking number and response owner.

    Check before handing it over

    The selected route is justified, the requested files are complete and the claims match the evidence.

    Use the current FDA template where required. This download is a project index, and it can accompany your internal review.

  4. 04

    Manage review and postmarket controls

    Who Regulatory affairs + postmarket lead When FDA clock and ongoing obligations

    Track acknowledgment and information requests. After the decision, confirm registration/listing, change control, reporting and applicable postmarket obligations.

    How to do this step

    Before you start

    Submission receipt, frozen dossier, FDA correspondence, regulatory obligations and manufacturing change records.

    1. Log FDA correspondence with date received, official response deadline, owners and submission route. Break each question into evidence requests and approve the response before transmission.
    2. On decision, verify the indications, model and conditions against proposed marketing copy and release materials. Put applicable registration, listing and other launch obligations on the release checklist.
    3. Assign owners for complaint handling, reportability, corrections or removals and changes. Preserve the cleared or approved configuration for future comparisons.

    What a reviewer should see

    The release file links the official decision, authorized claims, current labeling and signed launch checklist.

    When to escalate

    Escalate a hold or missing evidence immediately, and route changes proposed during review to Regulatory before shipping or modifying the submission.

    What to produce

    FDA decisionIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Registration/listing recordIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

    Postmarket planMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

Common questions

How do we choose between 510(k), De Novo and PMA?

Start with the device’s intended use, classification and any applicable exemption. A 510(k) generally relies on substantial equivalence to a legally marketed predicate. Eligible low- to moderate-risk devices without a predicate may use De Novo. PMA generally applies to Class III devices.

FDA · Overview of device regulation (opens in a new tab)

How should we plan around a 90 FDA day target?

Track both the FDA review clock and total elapsed time. A review clock can stop while the sponsor answers a request. Give the response team owners, internal deadlines and access to the underlying tests and technical records.

FDA · 510(k) submission process (opens in a new tab)
PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes