Author: Stephanie Knighten, Senior Director, Medical Device Writing Services, M.S. Forensic Science
Bringing a medical device to the U.S. market requires a clear understanding of the applicable FDA regulatory pathway. For many Class II devices—and certain Class I and Class III devices—that pathway is the Premarket Notification, commonly called a 510(k).
A successful 510(k) requires more than identifying a similar product and compiling test reports. Manufacturers must determine the correct device classification, define supportable indications for use, select an appropriate predicate device, generate the necessary performance evidence, and present a clear and defensible substantial-equivalence argument.
Every component of the submission must tell the same regulatory story. The device description, predicate comparison, risk documentation, testing, labeling, software information, and 510(k) Summary must consistently describe the same device, claims, configurations, and performance characteristics.
Criterion Edge helps medical device manufacturers translate complex development records into clear, cohesive, and submission-ready 510(k) documentation. Our senior medical device writers work across regulatory, engineering, quality, clinical, software, cybersecurity, and human-factors teams to identify documentation gaps, coordinate technical inputs, and develop a submission designed for efficient FDA review.
What is a 510(k)?
A 510(k) is a premarket submission provided to the U.S. Food and Drug Administration to demonstrate that a medical device is substantially equivalent to a legally marketed device.
The legally marketed device used as the basis for comparison is generally called the predicate device.
A new device does not need to be identical to the predicate. Instead, the manufacturer must demonstrate that the new device:
- Has the same intended use as the predicate device; and
- Has the same technological characteristics as the predicate device;
or
- Has the same intended use as the predicate device;
- Has different technological characteristics that do not raise different questions of safety and effectiveness; and
- Is demonstrated through appropriate scientific evidence to be at least as safe and effective as the predicate device.
FDA evaluates the intended use, technological characteristics, and supporting performance data to determine whether the new device is substantially equivalent, or SE, to the predicate. A device may not be commercially distributed in the United States until FDA issues an SE decision.
When FDA determines that a device is substantially equivalent, the device is considered FDA cleared. It should not be described as “FDA approved,” because FDA approval generally refers to devices reviewed through the Premarket Approval, or PMA, pathway.
What is the purpose of a 510(k)?
The purpose of a 510(k) is to provide FDA with sufficient information to determine whether a device may enter the U.S. market based on substantial equivalence to a legally marketed device.
The submission allows FDA to evaluate:
- What the device is intended to do;
- Which patients, users, anatomical sites, and use environments are included;
- How the device operates;
- How it compares with the selected predicate device;
- Whether differences from the predicate could affect safety or effectiveness;
- Whether the submitted testing adequately addresses those differences; and
- Whether the labeling accurately describes the device, its performance, its limitations, and its residual risks.
A 510(k) is therefore not simply a side-by-side product comparison. FDA may review bench performance, engineering data, software validation, cybersecurity, biocompatibility, electrical safety, electromagnetic compatibility, sterility, shelf life, usability, animal testing, clinical evidence, and other information relevant to the device.
The strongest submissions connect each technological difference to the applicable risks and supporting evidence. The reviewer should be able to see why a difference does not raise a new safety or effectiveness question and how the test data support that conclusion.
Which devices require a 510(k)?
A 510(k) is generally required when a person or company intends to introduce a medical device into U.S. commercial distribution for the first time and the device:
- Is subject to premarket notification requirements;
- Is not exempt from 510(k) requirements;
- Does not require a PMA; and
- Has an appropriate legally marketed device against which substantial equivalence can be evaluated.
The 510(k) pathway is most commonly associated with Class II devices, although some Class I and Class III devices are also subject to 510(k) requirements.
A new 510(k) may also be required when a legally marketed device is modified and the change:
- Could significantly affect the device’s safety or effectiveness; or Represents a major change or modification in the device’s intended use.
The manufacturer is responsible for evaluating the regulatory significance of device changes and documenting the rationale for submitting—or not submitting—a new 510(k).
Who submits a 510(k)?
FDA requirements focus on the actions that trigger a premarket notification rather than assigning responsibility based on one particular company title.
Parties that may be required to submit a 510(k) include:
- Domestic finished-device manufacturers introducing a device to the U.S. market;
- Specification developers that design a finished device but contract with another organization to manufacture it;
- Repackagers or relabelers that make significant labeling changes or otherwise significantly affect the device; and
- Foreign manufacturers or exporters introducing a device into the United States.
A contract manufacturer that manufactures a device entirely according to another company’s specifications does not ordinarily hold the 510(k) solely because it performs the manufacturing. The specification developer or other party introducing the device under its specifications is generally responsible for the submission.
When is a 510(k) not required?
A 510(k) may not be required when:
- The product does not meet the definition of a medical device;
- The device type is expressly exempt from premarket notification;
- The device is a qualifying preamendments device that has not been significantly changed;
- The device is not being commercially distributed;
- The product is an unfinished component supplied to another manufacturer;
- A distributor markets another manufacturer’s cleared device without significantly changing its labeling or condition;
- A change to an existing cleared device does not meet the threshold for a new submission; or
- Another pathway, such as De Novo or PMA, is appropriate.
A 510(k)-exempt device is not exempt from all FDA requirements. Manufacturers may still need to comply with requirements related to establishment registration, device listing, labeling, quality systems, complaint handling, Medical Device Reporting, corrections and removals, and other post-market obligations.
Manufacturers must also evaluate whether the device remains within the limitations of the applicable exemption. A device may lose its exempt status when, for example, it has a different intended use or operates using a different fundamental scientific technology than devices within the exempt generic type.
What is the regulatory context for a 510(k)?
The 510(k) framework was established under the Federal Food, Drug, and Cosmetic Act and is implemented primarily through 21 CFR Part 807, Subpart E.
The regulatory framework addresses:
- When a premarket notification is required;
- When a device may be exempt;
- Information required in the submission;
- Submission format;
- Substantial equivalence;
- The 510(k) Summary and 510(k) Statement;
- Required certifications and statements;
- Confidentiality; and
- FDA action on the submission.
The general information required in a premarket notification is described in 21 CFR 807.87. Depending on the device, the submission must include identifying and classification information, proposed labeling, statements concerning the device’s intended use, comparison with a legally marketed device, supporting performance data, required certifications, and other information needed for FDA’s review.
Manufacturers must also consider requirements and recommendations from:
- Device-specific classification regulations;
- Applicable special controls;
- FDA device-specific guidance documents;
- FDA cross-cutting guidance documents;
- FDA-recognized consensus standards;
- The Quality Management System Regulation;
- Human-subject protection and investigational-device requirements, when clinical data are generated;
- Cybersecurity requirements for qualifying cyber devices;
- Radiation-control requirements, when applicable;
- Unique Device Identification requirements;
- Establishment registration and device-listing requirements; and
- Applicable labeling regulations.
The regulatory strategy should identify these requirements before testing is finalized. Waiting until the submission is being assembled can reveal gaps that require new testing, revised labeling, or additional technical documentation.
What is substantial equivalence?
Substantial equivalence is the central regulatory concept underlying the 510(k) pathway.
FDA’s evaluation generally addresses five connected questions:
- Is the proposed predicate device legally marketed?
- Do the new device and predicate have the same intended use?
- Do the devices have the same technological characteristics?
- When technological characteristics differ, do the differences raise different questions of safety or effectiveness?
- Do the submitted data demonstrate that the new device is at least as safe and effective as the predicate?
A device may have different design features, materials, software functions, energy outputs, or performance specifications and still be found substantially equivalent. Those differences must, however, be transparently identified and scientifically evaluated.
The substantial-equivalence discussion should explain:
- What is the same;
- What is different;
- Why each difference is or is not clinically and technically significant;
- Which risks are associated with the difference;
- Which test or analysis addresses those risks; and
- Why the results support substantial equivalence.
FDA does not consider substantial equivalence to mean that two devices must be identical. FDA first evaluates intended use and technological characteristics and then considers the scientific methods and performance data used to address relevant differences.
What is a predicate device?
A predicate is a legally marketed device used as the basis for demonstrating substantial equivalence.
A legally marketed predicate may include:
- A device legally marketed before May 28, 1976 that has not been significantly modified;
- A device previously found substantially equivalent through the 510(k) process;
- A device reclassified from Class III into Class I or Class II; or
- A device granted marketing authorization through the De Novo classification process that is not exempt from premarket notification
The predicate must be legally marketed and cannot be a device being marketed in violation of the Federal Food, Drug, and Cosmetic Act.
How do you select the right predicate?
Predicate selection is one of the most consequential decisions in a 510(k) strategy.
The primary predicate should generally be the legally marketed device that provides the strongest overall comparison in terms of intended use and technological characteristics. An unsuitable predicate can result in avoidable FDA questions, additional testing, or a conclusion that the 510(k) pathway is not appropriate.
A predicate evaluation should consider:
- Intended use;
- Indications for use;
- Target patient population;
- Intended user;
- Use environment;
- Anatomical site;
- Operating principle;
- Mechanism of action;
- Energy source;
- Design and construction;
- Materials;
- Patient-contact type and duration;
- Software functionality;
- Connectivity;
- Sterility status;
- Reprocessing;
- Performance specifications;
- Accessories;
- Applicable special controls; and
- Known safety or performance concerns.
Manufacturers should review the predicate’s publicly available clearance documentation, including its:
- 510(k) Summary;
- Indications for Use statement;
- FDA decision letter;
- Product code;
- Regulation number;
- Classification information; and
- Publicly available labeling.
The predicate should not be selected solely because the device has similar marketing language or a similar commercial appearance. It must support the statutory substantial-equivalence framework.
Can more than one predicate device be used?
A manufacturer may reference more than one legally marketed device in certain circumstances. However, multiple devices should not be combined to construct a new intended use or technological profile that no individual predicate supports.
The submission should generally identify one primary predicate that supports the overall substantial-equivalence determination.
Other legally marketed devices may sometimes be included as:
- Additional predicates, when appropriate under FDA’s framework; or
- Reference devices that support a particular test method, design feature, or scientific rationale.
The submission should clearly explain the role of each device. FDA should be able to distinguish:
- Which device supports the substantial-equivalence determination;
- Which devices provide supplemental technical information; and
- Why each comparison is relevant.
What are the types of 510(k) submissions?
FDA recognizes three principal 510(k) programs: Traditional, Special, and Abbreviated.
Traditional 510(k)
A Traditional 510(k) may be used for any device eligible for the 510(k) pathway.
It is commonly used for:
- A new device entering the U.S. market;
- A submission from a new manufacturer;
- A device with significant technological differences from its predicate;
- A modification that does not qualify for the Special 510(k) program;
- A submission requiring extensive performance data; or
- A device for which the substantial-equivalence analysis requires detailed scientific explanation.
The Traditional 510(k) is the most broadly applicable submission type.
Special 510(k)
A Special 510(k) is generally intended for certain modifications to a manufacturer’s own legally marketed device.
It may be appropriate when:
- The submitter is authorized to market the existing device;
- The proposed change does not affect the device’s intended use;
- The methods used to evaluate the change are well established; and
- The results can be reviewed through summary information or a risk-based format.
Not every modification qualifies for a Special 510(k). Changes involving complex testing, new clinical questions, or evaluation methods that are not well established may require a Traditional 510(k).
Abbreviated 510(k)
An Abbreviated 510(k) relies on FDA guidance documents, special controls, and FDA-recognized consensus standards to facilitate review.
The term “abbreviated” does not mean that the manufacturer can omit evidence needed to establish substantial equivalence. The manufacturer must still provide the information required by 21 CFR 807.87 and demonstrate that the device complies with applicable requirements.
Summary reports and declarations of conformity may be used when appropriate, but the submission must explain how the guidance, special controls, or standards apply to the device.
What are the requirements for a 510(k)?
There is no universal test package that applies to every 510(k).
The submission requirements depend on the device’s:
- Classification;
- Product code;
- Regulation number;
- Intended use;
- Indications for use;
- Technological characteristics;
- Risk profile;
- Patient-contact characteristics;
- Sterility status;
- Software functions;
- Connectivity;
- Use environment;
- Applicable special controls;
- Device-specific FDA guidance;
- Applicable consensus standards; and
- Differences from the predicate device.
A complete submission must provide sufficient administrative, descriptive, labeling, comparison, and performance information for FDA to evaluate substantial equivalence.
In practice, that means the manufacturer must first identify the regulatory and scientific questions created by the device and then generate evidence that answers those questions.
What documents are included in a 510(k)?
Most 510(k)s are now prepared in FDA’s Electronic Submission Template and Resource, or eSTAR. The template uses the manufacturer’s responses to identify the sections and attachments applicable to the device.
Not every document below is required for every submission. However, the following sections represent a comprehensive master list of common 510(k) content.
Administrative and submission information
Administrative content may include:
- Submission type;
- Applicant and correspondent information;
- Device trade name and common name;
- Establishment information, when applicable;
- User-fee information;
- Product code;
- Regulation number;
- Regulatory class;
- Review panel;
- Prior submission information;
- Letters of authorization;
- Right-of-reference documentation;
- Required certifications;
- Truthful and Accurate Statement;
- Class III Certification and Summary, when applicable;
- Financial certification or disclosure information for clinical investigators;
- Statements concerning prior FDA interactions; and
- Other information requested through eSTAR.
Administrative sections should be completed with the same attention as technical sections. Inconsistent device names, submission numbers, contacts, or product codes can delay processing or create confusion during review.
Indications for Use statement
The Indications for Use statement defines the disease or condition, patient population, anatomical site, intended user, use environment, or other parameters for which the device is intended.
This statement is fundamental to the substantial-equivalence determination because the new device must have the same intended use as the predicate.
The Indications for Use statement should be consistent with:
- Proposed labeling;
- Device description;
- Design inputs;
- Risk-management documentation;
- Verification and validation testing;
- Clinical evidence;
- Predicate comparison; and
- Proposed promotional claims.
Even seemingly minor wording changes can have significant regulatory consequences. Broader claims, new patient populations, different users, or new use environments may affect device classification, predicate suitability, or testing requirements.
510(k) Summary or 510(k) Statement
A 510(k) must include either a 510(k) Summary or a 510(k) Statement.
Most manufacturers provide a 510(k) Summary. Following clearance, the Summary generally becomes publicly available and includes:
- Submitter information;
- Device identification;
- Predicate information;
- Device description;
- Intended use;
- Technological characteristics;
- Performance data; and
- The substantial-equivalence conclusion.
Because the 510(k) Summary becomes part of the public clearance record, it should be accurate, appropriately detailed, and fully aligned with the rest of the submission.
Device description
The device description should allow the FDA reviewer to understand what the device is, how it functions, and how it is used.
Depending on the product, the description may include:
- Device components;
- Accessories;
- Models and configurations;
- Operating principles;
- Mechanism of action;
- Key design features;
- Materials;
- Patient-contacting components;
- Energy source or energy delivery;
- Software architecture;
- Hardware architecture;
- Wireless or network connectivity;
- User interface;
- Packaging;
- Sterilization status;
- Single-use or reusable status;
- Reprocessing methods;
- Shelf life;
- Expected service life;
- Photographs;
- Diagrams;
- Engineering drawings;
- System schematics; and
- Clinical or user workflow diagrams.
The description should distinguish between:
- The subject device;
- Included accessories;
- Optional accessories;
- Compatible products;
- Products referenced for context; and
- Products outside the scope of the submission.
A common source of FDA questions is an incomplete description that does not clearly identify every configuration or accessory intended to be marketed under the clearance.
Predicate-device documentation
Predicate information commonly includes:
- Predicate device name;
- Manufacturer;
- 510(k) number or other legal marketing basis;
- Product code;
- Regulation number;
- Regulatory classification;
- Indications for use;
- Device description;
- Technological characteristics;
- Explanation of why the device is an appropriate predicate; and
- Relevant publicly available FDA documentation.
The submission should demonstrate that the predicate is legally marketed and remains suitable for the intended comparison.
Substantial-equivalence comparison
The comparison usually includes a detailed table addressing characteristics such as:
- Intended use;
- Indications for use;
- Target patient population;
- Intended user;
- Use environment;
- Anatomical site;
- Operating principle;
- Mechanism of action;
- Design;
- Dimensions;
- Materials;
- Patient contact;
- Energy source;
- Performance specifications;
- Software functions;
- Connectivity;
- Sterility;
- Packaging;
- Shelf life;
- Reprocessing;
- Biocompatibility;
- Electrical characteristics; and
- Accessories.
A comparison table is not sufficient by itself. Each difference should be evaluated to determine:
- Whether it raises a different question of safety or effectiveness;
- Which hazards or performance concerns are associated with it;
- Whether additional testing is required; and
- How the evidence supports the substantial-equivalence conclusion.
Bench and performance testing
Bench testing is often the primary source of performance evidence in a 510(k).
Testing may include:
- Functional performance;
- Mechanical performance;
- Dimensional verification;
- Accuracy;
- Precision;
- Reliability;
- Durability;
- Fatigue;
- Tensile testing;
- Compression testing;
- Torque testing;
- Burst testing;
- Flow testing;
- Simulated-use testing;
- Environmental testing;
- Transportation testing;
- Alarm testing;
- Sensor performance;
- Energy-output testing;
- Image-quality testing;
- Cleaning and disinfection validation;
- Reprocessing validation;
- Compatibility testing; and
- Accessory testing.
Each test report should clearly identify:
- The test objective;
- Test article;
- Device model and configuration;
- Software version, when applicable;
- Sample size;
- Sample-selection rationale;
- Acceptance criteria;
- Test method;
- Standards used;
- Deviations;
- Results;
- Statistical methods;
- Failures or anomalies;
- Conclusions; and
- Relationship of the results to substantial equivalence.
Acceptance criteria should be predefined and linked to an appropriate scientific basis, such as design inputs, risk controls, standards, predicate performance, clinical requirements, or other justified benchmarks.
Biocompatibility documentation
Biocompatibility information may be required for devices with direct or indirect patient contact.
The evaluation generally considers:
- Nature of body contact;
- Contact duration;
- Patient-contacting materials;
- Manufacturing processes;
- Material additives and processing aids;
- Chemical characterization;
- Existing toxicological information;
- Biological risks;
- Applicable biological endpoints;
- Biocompatibility test results;
- Toxicological risk assessment;
- Impact of sterilization;
- Impact of cleaning or reprocessing;
- Material changes; and
- Supplier changes.
The evaluation should address the finished device in its final manufactured and sterilized form, as applicable.
Simply identifying a material as commonly used may not be sufficient when processing, colorants, adhesives, sterilization, or other factors could affect biological safety.
Sterilization documentation
For sterile devices, the submission may need to address:
- Sterilization method;
- Sterility assurance level;
- Sterilization validation;
- Pyrogenicity;
- Endotoxin limits;
- Packaging validation;
- Sterile-barrier integrity;
- Residual sterilant levels;
- Bioburden;
- Dose establishment or cycle development;
- Maximum processing exposure; and
- Reprocessing or resterilization limitations.
The level of detail required may depend on whether the sterilization method is established or novel.
Shelf-life and packaging documentation
Shelf-life evidence may include:
- Package integrity;
- Seal strength;
- Distribution simulation;
- Environmental conditioning;
- Accelerated aging;
- Real-time aging;
- Functional performance after aging;
- Sterility maintenance;
- Material stability;
- Battery stability;
- Reagent stability; and
- Label durability.
The claimed expiration date should be supported by an appropriate aging strategy and by testing the attributes that could change over time.
A shelf-life section should explain not only how long the device will remain packaged, but also why aging does not adversely affect the safety, performance, sterility, or usability of the finished device.
Electrical safety and electromagnetic compatibility
Electrically powered devices may require documentation related to:
- Basic electrical safety;
- Essential performance;
- Electromagnetic emissions;
- Electromagnetic immunity;
- Wireless coexistence;
- Electrical isolation;
- Battery safety;
- Home-use conditions;
- Environmental conditions; and
- Particular standards applicable to the device type.
When recognized standards are used, the manufacturer should identify the edition tested, any deviations, and whether the testing applies to every proposed device configuration.
Software documentation
For devices containing software, the submission may include:
- Software description;
- Software function;
- Software architecture;
- Documentation-level rationale, as applicable;
- Software requirements;
- System and software design information;
- Risk-management documentation;
- Hazard analysis;
- Requirements traceability;
- Verification and validation;
- Unit testing;
- Integration testing;
- System testing;
- Unresolved anomaly list;
- Version history;
- Revision-level history;
- Off-the-shelf software information;
- Software configuration management; and
- Maintenance planning.
The documentation should demonstrate that the software performs as intended, that requirements have been verified, and that software-related risks have been appropriately controlled.
Software version numbers and functions must remain consistent across the device description, test reports, cybersecurity documentation, labeling, and 510(k) Summary.
Cybersecurity documentation
Cybersecurity documentation may be required when a device contains software and has connectivity or other characteristics that could introduce cybersecurity risks.
Depending on the device, the submission may need to include:
- Cybersecurity risk-management report;
- Threat modeling;
- Security architecture;
- Security requirements;
- Security traceability;
- Vulnerability testing;
- Penetration testing;
- Software Bill of Materials;
- Coordinated Vulnerability Disclosure process;
- Post-market cybersecurity management plan;
- Patch and update procedures;
- Authentication and authorization controls;
- Data-protection measures;
- Logging and monitoring;
- Secure update mechanisms; and
- Cybersecurity labeling.
Cybersecurity should be integrated with the overall device risk-management process rather than treated as a separate technology exercise.
Human-factors and usability documentation
Human-factors or usability engineering documentation may be required when user interactions could cause or contribute to serious harm.
Documentation may include:
- Intended-user profiles;
- Use environments;
- Task analysis;
- Use-related risk analysis;
- Identification of critical tasks;
- Formative evaluations;
- User-interface design changes;
- Human-factors validation protocol;
- Validation results;
- Training evaluation; and
- Label-comprehension testing.
Validation should represent the intended users, intended environments, and critical tasks associated with the final user interface.
FDA updated the eSTAR program in June 2026 to incorporate content from its current human-factors guidance into updated eSTAR versions. Manufacturers should therefore use the current template and review the applicable human-factors expectations for their submission.
Labeling
Proposed labeling may include:
- Package labels;
- Device labels;
- Instructions for use;
- User manuals;
- Operator manuals;
- Patient labeling;
- Quick-reference guides;
- Installation instructions;
- Reprocessing instructions;
- Maintenance instructions;
- Training materials; and
- Other materials needed to support safe and effective use.
Labeling must be consistent with:
- Indications for use;
- Validated performance;
- Intended users;
- Use environments;
- Warnings;
- Contraindications;
- Precautions;
- Residual risks;
- Reprocessing validation;
- Shelf life; and
- The substantial-equivalence argument.
Claims should not exceed the scope of the performance evidence.
Clinical evidence
Many 510(k)s are supported primarily by nonclinical evidence. Clinical data may be required when bench, analytical, animal, or other nonclinical testing cannot adequately resolve a safety or effectiveness question.
Clinical documentation may include:
- Clinical protocol;
- Statistical analysis plan;
- Investigator information;
- Institutional Review Board information;
- Informed-consent documentation;
- Investigational Device Exemption information;
- Clinical study report;
- Statistical outputs;
- Adverse-event data;
- Protocol deviations;
- Financial disclosure information;
- Compliance statements; and
- Information supporting the relevance of studies conducted outside the United States.
Clinical evidence should be designed to address the specific unresolved regulatory question. A study does not strengthen a submission merely because it is clinical; it must support the intended use, claims, and substantial-equivalence analysis.
Animal testing
Animal testing may be appropriate when bench testing does not adequately represent biological response, anatomical interaction, healing, device handling, or in vivo performance.
Documentation may include:
- Study rationale;
- Animal-model justification;
- Protocol;
- Sample size;
- Study endpoints;
- Histopathology;
- Imaging;
- Performance observations;
- Adverse findings;
- Good Laboratory Practice information; and
- Final report.
Risk-management documentation
The complete risk-management file is not necessarily submitted in every 510(k), but risk-based evidence is central to a strong submission.
Relevant documentation may include:
- Risk-management plan;
- Hazard analysis;
- Design Failure Modes and Effects Analysis;
- Use-related risk analysis;
- Software risk analysis;
- Cybersecurity risk analysis;
- Risk-control verification;
- Residual-risk evaluation;
- Benefit-risk assessment; and
- Production and post-production planning.
The submission should show alignment between:
- Identified hazards;
- Risk-control measures;
- Design requirements;
- Verification and validation testing;
- Acceptance criteria;
- Labeling; and
- Residual-risk communication.
Standards documentation
When FDA-recognized consensus standards are used, the submission may include:
- List of standards;
- Recognition numbers;
- Standard editions;
- Declarations of conformity;
- Test-laboratory information;
- Summary test reports;
- Explanation of partial conformity;
- Deviations from the standard; and
- Justification for alternative methods.
Use of a recognized standard does not automatically establish substantial equivalence. The manufacturer must explain how the standard applies to the device and what aspects of safety or performance it supports.
What is the structure of a 510(k)?
Most 510(k) submissions must be prepared and submitted using FDA’s Electronic Submission Template and Resource, or eSTAR.
eSTAR is an interactive electronic template that guides the applicant through submission preparation, identifies applicable content, and provides a standardized structure aligned with FDA’s internal review process. FDA states that all 510(k) and De Novo submissions to CDRH or CBER must use eSTAR unless an exemption applies.
The precise structure depends on the device and the responses entered in the template. A typical 510(k) includes content addressing:
- Submission identification;
- Applicant and correspondent information;
- Device identification and classification;
- Regulatory history;
- Indications for Use;
- 510(k) Summary or Statement;
- Device description;
- Predicate identification;
- Substantial-equivalence comparison;
- Labeling;
- Applicable standards and guidance;
- Performance testing;
- Biocompatibility;
- Sterility;
- Shelf life and packaging;
- Electrical safety and electromagnetic compatibility;
- Software;
- Cybersecurity;
- Human factors and usability;
- Animal studies;
- Clinical studies;
- Required certifications and statements; and
- Supporting attachments.
The currently implemented eSTAR version should be used. FDA periodically revises the template to reflect new policies, regulations, and guidance. Use of an older major version can lead to requests for information related to requirements added in the updated template.
What is the 510(k) development process?
A successful 510(k) usually progresses through a series of connected regulatory, technical, and writing activities.
1. Confirm that the product is a medical device
The first step is to determine whether the product meets the statutory definition of a medical device and which FDA center has jurisdiction.
Products incorporating device, drug, or biological functions may require additional jurisdictional analysis.
2. Determine the device classification
The manufacturer should identify the:
- Device type;
- Classification;
- Product code;
- Regulation number;
- Review panel;
- 510(k)-exempt status;
- Limitations of exemption;
- Special controls;
- Device-specific guidance; and
- Relevant standards.
The classification strategy affects nearly every later decision, including predicate selection, testing, labeling, and submission content.
3. Confirm the appropriate premarket pathway
The manufacturer should determine whether the appropriate pathway is:
- 510(k);
- De Novo;
- PMA;
- Humanitarian Device Exemption;
- Exempt status; or
- Another specialized pathway.
A 510(k) may not be viable when there is no appropriate legally marketed predicate or when the device raises different questions of safety or effectiveness.
4. Define the intended use and indications for use
The intended use should be established early because it drives:
- Device classification;
- Predicate selection;
- Risk management;
- Testing;
- Clinical strategy;
- Human-factors strategy;
- Labeling; and
- Substantial equivalence.
Changing the indications late in development can invalidate the predicate strategy or create a need for additional testing.
5. Identify and evaluate potential predicates
Potential predicates should be systematically compared with the new device.
A documented predicate assessment should evaluate:
- Intended use;
- Indications;
- Technological characteristics;
- Relevant differences;
- Publicly available performance information;
- Known safety concerns; and
- Overall suitability for substantial equivalence.
6. Identify applicable FDA requirements
The regulatory strategy should map:
- eSTAR sections;
- Special controls;
- FDA guidance;
- Recognized standards;
- Test requirements;
- Clinical-evidence expectations;
- Cybersecurity requirements;
- Human-factors requirements;
- Labeling requirements; and
- Quality-system dependencies.
7. Conduct a submission gap assessment
A gap assessment compares available development documentation with the anticipated FDA submission requirements.
Common gaps include:
- Unsupported indications;
- Incomplete device descriptions;
- Weak predicate comparisons;
- Missing test protocols;
- Acceptance criteria established after testing;
- Inadequate sample-size rationales;
- Incomplete software traceability;
- Missing cybersecurity deliverables;
- Unsupported shelf life;
- Inconsistent labeling;
- Unresolved test anomalies; and
- Test reports that do not address device differences.
Criterion Edge can conduct a targeted 510(k) gap assessment or develop a complete content plan that identifies the required submission sections, available source documents, missing information, responsible subject-matter experts, and anticipated authoring needs.
8. Engage FDA when appropriate
A Pre-Submission, or Pre-Sub, may be valuable when the manufacturer seeks FDA feedback on:
- Predicate strategy;
- Proposed indications;
- Test methods;
- Acceptance criteria;
- Clinical-study design;
- Sample size;
- Software documentation;
- Cybersecurity strategy;
- Human-factors validation;
- Novel technological characteristics; or
- Other areas of regulatory uncertainty.
FDA feedback provided through the Q-Submission process is generally nonbinding, but early interaction can reduce uncertainty and prevent major strategic misalignment.
9. Generate and finalize performance evidence
Testing should be performed using approved protocols with predefined acceptance criteria.
Final reports should:
- Identify the final device configuration;
- Describe the test method;
- Explain sample selection;
- Report all relevant results;
- Address deviations and anomalies;
- Provide scientifically supported conclusions; and
- Explain how the evidence supports safety, effectiveness, and substantial equivalence.
10. Develop the substantial-equivalence narrative
The submission should explain:
- Why the predicate is legally marketed and appropriate;
- Why the intended uses are the same;
- Which technological characteristics are shared;
- Which characteristics differ;
- Why the differences do not raise different questions of safety or effectiveness;
- Which data address each difference; and
- Why the new device is at least as safe and effective as the predicate.
This narrative should be developed across the entire submission rather than limited to one table.
11. Complete a cross-functional consistency review
Before submission, the complete package should be reviewed for alignment across:
- Indications for Use;
- Device description;
- Predicate comparison;
- Risk management;
- Test reports;
- Software documentation;
- Cybersecurity documentation;
- Human-factors evidence;
- Labeling;
- Model and configuration lists;
- 510(k) Summary; and
- eSTAR responses.
Conflicting terminology, specifications, versions, or claims can create unnecessary FDA questions and reduce reviewer confidence.
12. Complete eSTAR and submit the 510(k)
The manufacturer completes the applicable eSTAR sections, attaches the supporting documents, pays the required user fee, and submits the package through the appropriate FDA electronic process.
The CDRH Customer Collaboration Portal may be used to transmit and track applicable medical device premarket submissions.
What happens after a 510(k) is submitted?
After FDA receives the eSTAR submission, the review process generally includes administrative processing, substantive review, communication with the manufacturer, and a final decision.
Administrative Processing and eSTAR Verification
Before submission, eSTAR checks whether the required fields have been completed. The template must display an “eSTAR COMPLETE” status before the CDRH Portal will accept the submission.
FDA does not anticipate conducting a traditional Refuse to Accept review for a properly prepared eSTAR submission. However, FDA may verify the accuracy of the responses entered in eSTAR.
If inaccurate responses caused required questions or sections to be omitted, FDA may place the submission on an early review hold and request the missing information.
Administrative issues, such as failure to pay the applicable user fee, may also prevent the submission from progressing.
Substantive Review
During substantive review, FDA evaluates the scientific, technical, clinical, and regulatory content of the submission.
The reviewer may assess:
- Predicate suitability;
- Indications for use;
- Technological differences;
- Performance evidence;
- Software;
- Cybersecurity;
- Human factors;
- Biocompatibility;
- Sterility;
- Labeling; and
- Other device-specific considerations.
Interactive Review
FDA may use interactive review when limited questions can be resolved through focused communication without placing the submission on formal hold.
Because response periods may be short, manufacturers should ensure that the appropriate regulatory and technical subject-matter experts are available during active review.
Additional Information Request
When more substantial information is needed, FDA may issue a formal Additional Information request and place the submission on hold.
The manufacturer’s response should:
- Address each FDA question directly;
- Follow FDA’s numbering and organization;
- Clearly identify revised documents;
- Provide new testing or analysis when required;
- Explain all changes to the submission; and
- Update affected sections consistently.
FDA Decision
FDA may issue either:
- A Substantially Equivalent decision; or
- A Not Substantially Equivalent decision.
A Substantially Equivalent decision allows the device to be commercially distributed after the manufacturer satisfies the other applicable regulatory requirements.
A Not Substantially Equivalent decision may lead the manufacturer to conduct additional testing, submit a new 510(k), or consider another regulatory pathway, such as De Novo classification or PMA.
How long does a 510(k) take?
FDA describes a 90-day review period for 510(k)s, but this does not necessarily mean 90 calendar days from submission to clearance. FDA review time may stop while the submission is on hold awaiting an Additional Information response.
The complete project timeline may include:
- Regulatory strategy;
- Predicate research;
- FDA Pre-Submission interaction;
- Test-method development;
- Prototype availability;
- Verification and validation;
- Biocompatibility testing;
- Sterilization validation;
- Packaging testing;
- Shelf-life testing;
- Software documentation;
- Cybersecurity testing;
- Human-factors validation;
- Clinical studies;
- Submission authoring;
- Cross-functional review;
- FDA review; and
- Additional Information response development.
For many devices, evidence generation takes considerably longer than submission assembly or FDA review.
Factors that can affect the timeline include:
- Device complexity;
- Novelty;
- Availability of a suitable predicate;
- Number of device models and configurations;
- Testing failures;
- Need for clinical evidence;
- Software complexity;
- Cybersecurity requirements;
- Availability of source documentation;
- Internal review cycles;
- Quality of the original submission; and
- Number and complexity of FDA questions.
What are the most common causes of 510(k) delays?
Common causes include:
- Selecting a weak or inappropriate predicate;
- Defining indications that are broader than the evidence supports;
- Failing to identify applicable special controls;
- Using outdated FDA guidance or standards;
- Providing an incomplete device description;
- Omitting relevant differences from the predicate comparison;
- Submitting test summaries without adequate methods or results;
- Using unsupported acceptance criteria;
- Failing to justify sample sizes;
- Providing inconsistent specifications across documents;
- Testing a configuration that differs from the proposed commercial device;
- Incomplete biocompatibility evaluation;
- Inadequate software documentation;
- Missing cybersecurity deliverables;
- Labeling that exceeds the validated claims;
- Incomplete human-factors documentation;
- Unsupported shelf-life claims;
- Failure to address test deviations or anomalies;
- Weak traceability between risks, requirements, testing, and labeling; and
- Poorly organized responses to FDA questions.
Many of these problems arise because documents are developed independently by different functions. A test report may be technically correct while still conflicting with the device description, labeling, predicate table, or risk analysis.
Why is cross-document consistency important?
A 510(k) is assembled from information generated by regulatory, engineering, quality, clinical, software, cybersecurity, manufacturing, testing laboratories, and external consultants.
FDA should see one clearly defined device supported by one consistent body of evidence.
For example:
- Model numbers in the labeling should match the device description.
- Indications for use should match the validated users and environments.
- The technological-characteristics table should describe the tested device.
- Test reports should use the same specifications claimed in the submission.
- Warnings should reflect residual risks.
- The 510(k) Summary should match the detailed submission.
- Software versions should be consistent across all documents.
- The shelf-life claim should match the aging evidence.
- Sterility claims should match the validated configuration.
- Accessories should be clearly identified as included, compatible, or outside the submission.
Criterion Edge reviews submissions as integrated regulatory packages rather than collections of isolated documents. Our writers examine alignment across the device description, predicate comparison, risk documentation, performance evidence, labeling, and summary materials to identify inconsistencies before they become FDA questions.
Does a 510(k) require a clinical trial?
Not necessarily.
Many 510(k)s are supported by bench, analytical, software, electrical, biocompatibility, animal, or simulated-use evidence without a clinical study.
Clinical data may be needed when:
- Nonclinical testing cannot adequately address a safety or effectiveness question;
- The device has novel technological characteristics;
- The proposed indications differ meaningfully from available predicates;
- Clinical performance is essential to the device’s function;
- Device-specific guidance or special controls call for clinical evidence;
- FDA identifies an unresolved clinical question; or
- A proposed claim cannot be supported through nonclinical testing alone.
The clinical strategy should be designed around the unresolved evidentiary question. Conducting a broad study without a clear regulatory purpose can add cost without resolving the issue FDA needs to evaluate.
What happens after 510(k) clearance?
510(k) clearance is not the end of the manufacturer’s regulatory responsibilities.
Before and after commercialization, the manufacturer may need to address:
- Establishment registration;
- Device listing;
- Quality Management System Regulation compliance;
- Labeling controls;
- Medical Device Reporting;
- Complaint handling;
- Corrections and removals;
- Unique Device Identification;
- Post-market surveillance;
- Device tracking, when applicable;
- Radiation-control requirements;
- Cybersecurity monitoring;
- Recall procedures;
- Import requirements; and
- Control of promotional claims.
The manufacturer must also evaluate future device changes to determine whether a new 510(k) is required. FDA identifies modifications that could significantly affect safety or effectiveness and major changes to intended use as triggers for a new submission.
How can manufacturers improve 510(k) readiness?
The most effective 510(k) programs begin during product development rather than after testing is complete.
Practical ways to improve submission readiness include:
- Establish the regulatory strategy early.
- Define the indications before verification and validation.
- Confirm predicate suitability before finalizing the test program.
- Create a guidance-and-standards matrix.
- Map device differences to specific risks and evidence.
- Link acceptance criteria to design inputs and risk controls.
- Maintain consistent device terminology across functions.
- Draft submission sections while testing is underway.
- Conduct a formal documentation gap assessment.
- Perform an RTA-readiness review.
- Complete a cross-functional consistency check.
- Prepare technical experts for FDA questions.
- Maintain a structured record of FDA correspondence and commitments.
A structured process reduces the risk that the 510(k) becomes a last-minute compilation of disconnected technical reports.
Why Choose Criterion Edge for 510(k) Support?
Criterion Edge provides specialized regulatory and medical writing support for medical device manufacturers preparing complex U.S. submissions.
Our writers do more than compile documents. We work across regulatory, engineering, quality, clinical, software, cybersecurity, human factors, and manufacturing functions to turn fragmented development records into one coherent submission.
Our support is particularly valuable when:
- Technical documentation has been generated by multiple functions or vendors;
- Device descriptions, testing, risk documentation, and labeling are not fully aligned;
- Internal teams have limited bandwidth to coordinate and draft the submission;
- Complex software, cybersecurity, usability, or clinical evidence must be integrated;
- A submission requires independent review before filing;
- FDA has issued an RTA or Additional Information request; or
- The manufacturer needs experienced support without increasing permanent internal headcount.
Criterion Edge can support selected sections, supplement an internal regulatory team, provide independent quality control, or take a broader lead-authoring role across the submission.
Criterion Edge experience
Criterion Edge supports medical device companies across the product-development and regulatory-submission lifecycle, including devices incorporating complex hardware, software, connectivity, imaging, diagnostic, monitoring, and patient-contacting technologies.
Our medical device writers have experience developing and reviewing documentation supporting:
- Traditional 510(k) submissions;
- Special 510(k) submissions;
- FDA Pre-Submission packages;
- Predicate and substantial-equivalence assessments;
- Device descriptions and technical summaries;
- Performance-testing documentation;
- Software documentation;
- Cybersecurity documentation;
- Biocompatibility summaries;
- Sterilization and packaging summaries;
- Shelf-life documentation;
- Human-factors and usability documentation;
- Clinical and nonclinical evidence summaries;
- Indications for Use and labeling alignment;
- FDA Additional Information responses;
- Submission remediation and gap assessments;
- Change assessments for modified devices; and
- Global medical device regulatory documentation.
Many submission delays are not caused by a complete lack of evidence. They are caused by gaps in how the evidence is organized, explained, justified, or connected to the proposed indications and predicate comparison.
Our writers help close those gaps by developing a clear regulatory story that explains:
- What the device is;
- How it is intended to be used;
- How it compares with the predicate;
- Which characteristics differ;
- How those differences were evaluated; and
- Why the evidence supports substantial equivalence.
Senior-led regulatory writing
Criterion Edge projects are supported by experienced medical device writers who understand both the technical content and the regulatory purpose of each submission section.
Our senior-led model supports:
- Early identification of regulatory and documentation risks;
- Efficient coordination with subject-matter experts;
- Stronger scientific and regulatory rationale;
- Consistent interpretation of source records;
- Clear resolution of conflicting technical information;
- Fewer unnecessary review cycles; and
- A consistent voice across the submission.
Our writers do not simply transfer text from technical reports into the eSTAR. They evaluate how the information supports the regulatory argument and identify areas where the source documentation is incomplete, inconsistent, or insufficiently explained.
One consistent regulatory story
A 510(k) may include documents prepared by different departments, laboratories, consultants, and development partners. Without centralized authoring and review, inconsistencies can appear in:
- Model numbers;
- Device configurations;
- Software versions;
- Specifications;
- Indications;
- Test articles;
- Accessories;
- Performance claims;
- Sterility status;
- Shelf-life claims; and
- Labeling.
Criterion Edge reviews the submission as an integrated package.
We evaluate alignment across:
- Indications for Use;
- Device description;
- Predicate comparison;
- Technological characteristics;
- Risk-management documentation;
- Verification and validation reports;
- Software documentation;
- Cybersecurity documentation;
- Human-factors evidence;
- Biocompatibility information;
- Sterilization information;
- Shelf-life and packaging claims;
- Labeling; and
- The 510(k) Summary.
This cross-document review helps ensure that FDA sees one clearly defined device supported by one consistent evidence package.
Submission-focused technical writing
Our writers translate technical source material into clear, concise, and reviewer-focused regulatory content.
We work from:
- Engineering reports;
- Risk-management files;
- Software records;
- Cybersecurity records;
- Clinical documentation;
- Standards assessments;
- Verification and validation reports;
- Laboratory reports;
- Quality records; and
- Proposed labeling.
Our writing approach emphasizes:
- Clear identification of the regulatory question;
- Direct explanation of how the evidence addresses that question;
- Transparent discussion of device differences;
- Appropriate scientific justification;
- Traceability to supporting documents;
- Consistent terminology;
- Controlled and supportable claims; and
- Efficient presentation of complex information.
The goal is not to make the submission longer. It is to make the evidence easier for FDA to follow and evaluate.
Independent quality control
Criterion Edge uses defined quality-control processes to evaluate regulatory, scientific, and document-level accuracy.
Depending on project scope, QC may include:
- Verification against source documents;
- Review of numerical data and specifications;
- Cross-checking model names and software versions;
- Confirmation of references and standards;
- Comparison of claims against test results;
- Review of tables and attachments;
- Assessment of cross-document consistency;
- Review for FDA terminology and submission conventions; and
- Confirmation that comments and corrections have been resolved.
Independent QC can be provided for submissions authored by Criterion Edge or for submissions prepared by the manufacturer or another vendor.
Flexible and scalable support
Not every manufacturer needs the same level of assistance.
Criterion Edge can serve as:
- The lead author coordinating and drafting the full submission;
- An extension of an internal regulatory team;
- A section-level writer for selected technical content;
- An independent reviewer or QC resource;
- A remediation partner following an RTA or Additional Information request; or
- A flexible writing resource during periods of high submission volume.
This model allows manufacturers to scale support according to project complexity, internal expertise, timeline, and budget.
Collaborative project execution
Our writers integrate with the client’s project team and established systems.
Depending on the engagement, Criterion Edge can:
- Participate in regulatory strategy and authoring meetings;
- Develop content plans and submission trackers;
- Maintain document inventories;
- Coordinate inputs from subject-matter experts;
- Identify missing or conflicting source information;
- Draft content in the client’s templates and systems;
- Support review-comment resolution;
- Maintain terminology and style conventions;
- Prepare content for eSTAR integration; and
- Support responses during active FDA review.
We emphasize clear ownership, transparent communication, and practical document planning so that the team understands what is needed, who is responsible, and how each deliverable supports the submission.
Support for complex technical content
Some 510(k) sections require specialized coordination because the evidence is technically dense, distributed across multiple records, or closely tied to evolving FDA expectations.
Criterion Edge can help integrate documentation related to:
- Software verification and validation;
- Cybersecurity risk management;
- Software Bills of Materials;
- Human factors and critical-task validation;
- Biocompatibility and toxicological risk;
- Sterilization and packaging validation;
- Shelf-life evidence;
- Electrical safety;
- Electromagnetic compatibility;
- Wireless coexistence;
- Artificial intelligence and machine learning;
- Clinical performance;
- Diagnostic accuracy;
- Imaging performance;
- Reprocessing and reusable devices; and
- Combination-product considerations.
Our role is to connect these technical areas to the device’s intended use, risks, technological differences, performance requirements, and overall substantial-equivalence argument.
Support after the initial submission
Criterion Edge can remain involved after the 510(k) is submitted.
Post-submission support may include:
- Review and interpretation of FDA questions;
- Development of Additional Information responses;
- Coordination of revised technical content;
- Updates to predicate comparison tables;
- Updates to labeling;
- Integration of new testing;
- Consistency review of the complete response package;
- Support for interactive-review communications; and
- Documentation of commitments and follow-up actions.
Because our writers understand the original submission narrative, they can help ensure that later responses remain aligned with the evidence and do not create new inconsistencies.
The Criterion Edge difference
Senior-level expertise
Projects are supported by experienced medical device writers who understand regulatory strategy, scientific evidence, and FDA submission expectations.
Integrated authoring
We connect the device description, risk analysis, testing, labeling, and predicate comparison into one coherent submission narrative.
Independent quality control
Our defined QC processes help identify inconsistencies, unsupported claims, and document-level errors before submission.
Flexible engagement models
We can lead the full writing effort, support selected sections, supplement an internal team, or provide independent review.
Clear project execution
We establish content plans, responsibilities, review workflows, and document trackers that make complex submissions easier to manage.
Reviewer-focused documentation
We develop content for the FDA reviewer, presenting the evidence so that the regulatory rationale and substantial-equivalence conclusion are clear.
Frequently Asked Questions About 510(k) Submissions
Is a 510(k) an FDA approval?
No. A successful 510(k) results in FDA clearance, not approval.
FDA approval generally refers to devices reviewed through the PMA pathway. A manufacturer should not promote a 510(k)-cleared device as “FDA approved.”
What does 510(k) stand for?
The name comes from section 510(k) of the Federal Food, Drug, and Cosmetic Act, which established the premarket-notification requirement.
Does every medical device need a 510(k)?
No. Some devices are exempt from premarket notification, some may be eligible for De Novo classification, and higher-risk devices may require PMA approval.
The correct pathway depends on the device’s classification, intended use, risks, technological characteristics, and availability of an appropriate predicate.
Are all Class II devices subject to 510(k)?
No. Most Class II devices require a 510(k), but some are exempt.
The applicable classification regulation, product code, special controls, and limitations of exemption should be reviewed before concluding that a device may be marketed without premarket notification.
Can a Class I device require a 510(k)?
Yes. Although many Class I devices are exempt, some Class I device types remain subject to 510(k) requirements.
Can a Class III device use the 510(k) pathway?
Certain Class III devices may remain eligible for 510(k) review, particularly when FDA has not issued a regulation requiring PMA approval for that device type.
Additional Class III certification and summary requirements may apply.
What is a predicate device?
A predicate is a legally marketed device used as the basis for demonstrating substantial equivalence.
It may be a device previously cleared through the 510(k) pathway, a qualifying preamendments device, a device reclassified into Class I or II, or a device authorized through De Novo classification that is eligible to serve as a predicate.
Does the predicate need to be made by the same manufacturer?
No. A manufacturer may generally use another company’s legally marketed device as a predicate.
The manufacturer must have enough publicly available information and device-specific evidence to support the comparison.
Can an older device be used as a predicate?
Potentially. There is no universal expiration date for a predicate device.
However, the manufacturer should consider whether the device remains legally marketed, whether it reflects current safety and performance expectations, and whether a more appropriate predicate is available.
Does the new device need to be identical to the predicate?
No. Differences are allowed when they do not raise different questions of safety or effectiveness and the submitted evidence demonstrates that the new device is at least as safe and effective as the predicate.
Can a recalled device be used as a predicate?
The existence of a recall does not automatically determine predicate eligibility, but it may create significant regulatory and scientific concerns.
The recall classification, reason, legal marketing status, safety issue, and relevance to the new device should be carefully evaluated.
What is the difference between a predicate and a reference device?
The predicate supports the overall substantial-equivalence determination.
A reference device may provide technical or scientific information relevant to a particular characteristic or test method but does not necessarily provide the primary basis for substantial equivalence.
What is the difference between a Traditional and Special 510(k)?
A Traditional 510(k) may be used for any eligible 510(k) device.
A Special 510(k) is generally used for certain modifications made by a manufacturer to its own legally marketed device when the evaluation methods are well established and the change can be reviewed using summary or risk-based information.
Is an Abbreviated 510(k) a shorter submission?
Not necessarily.
The Abbreviated 510(k) relies on guidance documents, special controls, and recognized standards to facilitate review, but the manufacturer must still provide enough information to meet regulatory requirements and establish substantial equivalence.
Is eSTAR mandatory?
Yes, for most 510(k) submissions to CDRH or CBER unless an exemption applies. FDA has required eSTAR for most 510(k)s since October 1, 2023.
Should the latest eSTAR template be used?
Manufacturers should use the currently implemented eSTAR version whenever possible.
FDA periodically updates eSTAR to incorporate new regulations, policies, and guidance. Use of an older major version may result in Additional Information requests related to content added to the newer template.
Is there an RTA Review for an eSTAR 510(k)?
FDA does not anticipate conducting a traditional Refuse to Accept review for a properly completed eSTAR submission.
eSTAR includes built-in completeness checks, and the CDRH Portal will not accept the submission unless the template indicates that it is complete.
FDA may nevertheless verify the accuracy of the information entered. If inaccurate answers caused applicable sections to be omitted, FDA may place the submission on an early review hold and request the missing information.
Does an “eSTAR COMPLETE” status mean the device will be cleared?
No.
The “eSTAR COMPLETE” status confirms that the required template fields have been completed. It does not mean that the scientific evidence is adequate or that FDA has determined the device to be substantially equivalent.
FDA may still identify substantive deficiencies and request additional information during its review.
How long does FDA review take?
FDA commonly describes the 510(k) review period as 90 FDA days.
Time during which the submission is on hold awaiting a response to an Additional Information request is not counted as active FDA review time, so total calendar time may be longer.
How long does it take to prepare a 510(k)?
Preparation may take several months or longer, depending on:
- Device complexity;
- Testing requirements;
- Software and cybersecurity content;
- Human-factors requirements;
- Need for clinical evidence;
- Predicate strategy;
- Availability of complete source documentation; and
- Internal review timelines.
Evidence generation is usually the longest part of the project.
Can FDA ask for information not specifically listed in eSTAR?
Yes.
eSTAR helps organize the submission and identify generally applicable content, but FDA may request additional information needed to determine substantial equivalence for the specific device.
Can a device be marketed as soon as the 510(k) is submitted?
No.
A device subject to 510(k) requirements may not be commercially distributed until FDA has issued an SE decision and the manufacturer has met other applicable regulatory requirements.
Are design-control records submitted in the 510(k)?
The complete design and development file is not ordinarily included.
However, design-control records provide the foundation for the device description, specifications, risk analysis, verification and validation, software documentation, and labeling included in the submission.
Manufacturers must maintain applicable quality-system documentation for FDA inspection.
Is ISO 13485 certification required for 510(k) clearance?
FDA does not generally require an ISO 13485 certificate as a prerequisite for submitting or clearing a 510(k).
However, the manufacturer must comply with applicable FDA quality-system requirements.
Do foreign manufacturers need to submit a 510(k)?
Yes, when their device is subject to 510(k) requirements and will be introduced into U.S. commercial distribution.
Foreign manufacturers must also address applicable establishment registration, device listing, U.S. agent, import, labeling, and quality-system requirements.
Is cybersecurity documentation required for every connected device?
The specific content depends on the device’s software, connectivity, intended use, and cybersecurity risks.
Qualifying cyber devices are subject to statutory cybersecurity requirements. Other software-containing devices may still require cybersecurity documentation as part of software validation and risk management.
Does every software device require clinical data?
No.
Some software devices can be supported through analytical validation, software verification and validation, usability evidence, and other nonclinical testing.
Clinical validation may be required when the software’s intended medical purpose or performance claims cannot be adequately supported without clinical evidence.
Can published literature be used in a 510(k)?
Yes.
Published literature may support:
- Scientific background;
- Test methods;
- Clinical context;
- Known risks;
- Performance expectations; or
- Supplemental evidence.
However, literature may not replace device-specific testing when FDA expects performance data generated using the final finished device.
Are competitor test reports required?
No.
Manufacturers generally test their own devices. Publicly available information about the predicate supports the comparison, but the new device must have adequate evidence demonstrating its own performance.
What happens if FDA finds the device not substantially equivalent?
FDA may issue an NSE decision when:
- There is no appropriate predicate;
- The intended use differs;
- Technological differences raise different questions of safety or effectiveness; or
- The submitted evidence is insufficient.
The manufacturer may then consider additional testing, a revised 510(k), De Novo classification, reclassification, or PMA, depending on the reason for the decision.
When is a new 510(k) required for a device modification?
A new 510(k) is required when a change could significantly affect device safety or effectiveness or represents a major change or modification in intended use.
Manufacturers should evaluate labeling, technology, engineering, materials, performance, software, and manufacturing changes individually and collectively and document the conclusion.
Does FDA inspect the manufacturing facility before 510(k) clearance?
FDA does not typically conduct routine pre-clearance inspections for 510(k)s.
The manufacturer remains subject to applicable quality-system requirements and may be inspected after clearance.
What is one of the most common 510(k) mistakes?
One of the most common strategic mistakes is beginning submission development only after product testing is complete.
When predicate selection, indications, risk management, testing, and labeling are developed independently, the resulting evidence may not support a coherent substantial-equivalence argument.
Early regulatory and documentation planning helps ensure that the development program generates the evidence the submission will need.
When should a manufacturer hire a 510(k) writing partner?
External writing support may be valuable when:
- Internal regulatory resources are limited;
- Multiple functions or vendors have generated inconsistent records;
- The submission includes complex software or cybersecurity documentation;
- The predicate strategy is difficult;
- Testing is complete but the regulatory narrative is unclear;
- The manufacturer needs independent QC;
- FDA has issued an RTA or Additional Information request;
- The submission is behind schedule;
- The manufacturer is entering the U.S. market for the first time; or
- The company needs a repeatable submission process across a device portfolio.
An experienced regulatory writing partner can coordinate technical inputs, identify gaps, and ensure that the submission presents a consistent, reviewer-focused argument.
Preparing a 510(k) Submission?
A successful 510(k) depends on more than completing the eSTAR template.
It requires:
- An appropriate predicate strategy;
- A clearly defined intended use;
- Supportable indications;
- Device-specific performance evidence;
- Transparent evaluation of technological differences;
- Alignment between risks, testing, and labeling; and
- Consistency across the complete regulatory package.
Criterion Edge helps manufacturers identify documentation gaps, coordinate technical inputs, develop clear substantial-equivalence narratives, and prepare submission content designed for efficient FDA review.
Whether your company is preparing its first U.S. medical device submission, modifying an existing cleared device, responding to FDA questions, or managing multiple submissions across a product portfolio, Criterion Edge can provide the senior-level writing, cross-functional coordination, and independent quality support needed to move the project forward.
