FDA Cleared vs Approved

In FDA parlance, the verbs matter. A medical device is “cleared” when FDA issues a substantial equivalence decision under the 510(k) pathway. A device is “approved” when FDA grants a Premarket Approval (PMA) application, typically for Class III, highest‑risk devices. Medicines are also “approved,” via new drug applications (NDAs) or biologics license applications (BLAs).

A third, distinct device outcome is “granted” for De Novo classification requests. De Novo is reserved for first‑of‑a‑kind, low‑to‑moderate‑risk devices that lack a suitable predicate. A granted De Novo order both classifies the device type and can create a predicate for subsequent 510(k)s. It is not a clearance and not an approval.

Behind the verbs are different evidence thresholds. Substantial equivalence focuses on intended use, technological characteristics, and performance comparisons to a predicate. PMA, NDA, and BLA approvals hinge on demonstrations of safety and effectiveness supported by robust data packages, often including pivotal clinical evidence and comprehensive manufacturing controls.

Terminology is not a semantic nicety. Calling a 510(k)-cleared device “FDA approved” can mislead users about evidentiary rigor and postmarket controls. It can also constitute misbranding, with real enforcement risk. Calibrate claims to the actual pathway outcome, and align your labeling and promotion to the reviewed indications and risk controls described in 510(k) vs PMA and the stages in medical device development phases.

The Federal Food, Drug, and Cosmetic Act (FD&C Act) provides the statutory foundation for all three outcomes. For medical devices, the 510(k) framework implements the substantial equivalence standard, while PMA sets a high evidentiary bar commensurate with Class III risk. De Novo classification supplies a risk-based on‑ramp where no predicate exists but special controls can provide reasonable assurance of safety and effectiveness.

FDA implements these authorities through Title 21 of the Code of Federal Regulations. 510(k) submissions are processed under 21 CFR Part 807 Subpart E, and PMA applications are governed by 21 CFR Part 814. De Novo requests are resolved through risk classification decisions that establish or refine special controls. The regulatory text shapes content requirements, review mechanics, and decision outputs.

Medicines follow distinct rules. NDAs (21 CFR Part 314) and BLAs (21 CFR Part 601) must demonstrate safety and effectiveness through substantial evidence from adequate and well‑controlled investigations. Chemistry, manufacturing, and controls (CMC) are scrutinized to ensure consistent product quality, and labeling negotiations circumscribe all future promotion.

These frameworks are complementary but not interchangeable. A device team’s choice among 510(k), De Novo, and PMA should be grounded in claim strategy, technological novelty, and achievable evidence. That analysis starts with risk class and intended use, as structured in medical device classification.

Different regulatory verbs correspond to different pathways and evidence models. Clearance hinges on substantial equivalence to a predicate, often relying on bench performance and, where relevant, clinical comparisons. De Novo classification asks whether special controls can mitigate risk for a novel, low‑to‑moderate‑risk technology. PMA approval demands comprehensive preclinical and clinical support and verifies manufacturing readiness. For medicines, NDA and BLA approvals require substantial evidence and rigorous CMC.

Understanding these distinctions helps teams scope development plans, timelines, and budgets. It also prevents labeling and promotion errors. For devices, predicate scope sets a ceiling for indications and claims. For PMA devices and medicines, the negotiated label governs on‑label promotion and postmarket obligations. The table below contrasts pathways, regulatory outcomes, and typical evidence patterns to anchor cross‑functional planning and leadership expectations.

Alignment on the correct outcome term should be codified in quality procedures and marketing review workflows. For early planning and submission-readiness checklists tailored to your intended device pathway, see 510(k) clearance readiness.

A 510(k) asks whether your device has the same intended use and similar technological characteristics as a predicate, or whether differences are acceptable and do not raise new questions of safety and effectiveness. Evidence must systematically address indications, technology, and performance against clinically relevant acceptance criteria.

Predicate selection is strategic. A broader intended use and contemporary performance profile can simplify the narrative, but borrowed claims still require your own data. Comparative testing should be methodologically sound, traceable to recognized standards, and justified through risk analysis rather than convenience. Sampling plans, equivalence margins, and worst‑case configurations should reflect clinical relevance.

Public databases are powerful. Mining the FDA 510(k) database clarifies historical claim language, test methods, and performance benchmarks. The predicate device concept interacts with special controls and recognized standards, and accredited testing under voluntary programs can streamline review by demonstrating conformance with rigor.

Operationally, build a submission around a crisp indication for use statement, a clear technological comparison table, and well‑organized performance reports. Use traceable rationales for acceptance criteria, and tie them to clinical risk. If limited clinical data are necessary, explain study design, endpoints, and statistical analysis in dialogue with FDA during pre‑submission interactions.

De Novo classification fills the gap for novel technologies that are low to moderate risk but lack a predicate. The key regulatory question becomes whether general and special controls can provide reasonable assurance of safety and effectiveness. If the answer is yes, FDA issues a De Novo order granting a new classification regulation or product code with defined special controls.

A granted De Novo can unlock a new device family. Once established, subsequent devices with the same intended use and similar technology can pursue 510(k) clearance by claiming substantial equivalence to the newly created predicate. This progression rewards early movers who craft risk controls and performance specifications that the market can adopt.

Evidence packages for De Novo hinge on thorough risk analysis, performance testing against clinically justified specifications, and proposals for special controls that manage identified hazards. Depending on novelty and risk, limited clinical evidence may be warranted to address specific questions not resolvable by bench testing.

Plan De Novo submissions with the same operational discipline as PMA light: coherent claims, transparent methods, and fully traceable documentation. Early FDA touchpoints, including Q‑Sub meetings, can de‑risk the strategy and align expectations on the sufficiency of special controls and test matrices. For the core definition and how De Novo interacts with 510(k) and PMA, see De Novo.

PMA approval is reserved for high‑risk devices for which reasonable assurance of safety and effectiveness requires robust clinical evidence. Pivotal studies are often randomized and controlled, powered to clinically meaningful endpoints, and supported by rigorous preclinical testing. Human factors validation, cybersecurity assurances for connected systems, and software lifecycle controls are integral for digital and software‑intensive devices.

Manufacturing readiness is not an afterthought. FDA assesses design controls, process validation, supplier management, and complaint handling. Pre‑approval inspections may verify production controls, CAPA maturity, and change control discipline. Aligning your quality system with 21 CFR Part 820 and harmonized expectations with ISO 13485 reduces findings and post‑approval remediation.

Labeling negotiations at the end of review define the approved indications and claims, and many PMA devices carry conditions of approval or post‑approval study commitments. Proactive signal detection, rapid field action decision‑making, and robust postmarket surveillance practices protect patients and brand credibility.

Inspection and evidence planning benefit from early, structured FDA engagement on endpoints and statistical analysis plans. Teams should formalize an inspection‑readiness playbook, including mock interviews, data integrity checks, and document retrieval drills. For alignment with global quality expectations, see QMSR vs ISO 13485, and for device CGMP foundations, see 21 CFR 820.

For medicines, “FDA approved” signifies that the product met statutory standards for safety and effectiveness based on substantial evidence from adequate and well‑controlled studies, supported by comprehensive CMC. FDA evaluates benefit–risk in the context of the proposed indications, dosing, and patient population, then negotiates labeling that governs the promotional universe.

Drug and biologics reviews are modular and data‑dense. Clinical efficacy and safety, pharmacokinetics and pharmacodynamics, and exposure–response relationships are integrated with manufacturing controls, stability, and specifications to ensure consistent quality. Risk management plans, pharmacovigilance, and, where applicable, postmarketing requirements or commitments complete the framework.

Terminology discipline still matters. Drugs and biologics are never “cleared,” and using device verbs in therapeutic promotions can mislead stakeholders. Conversely, device sponsors should avoid importing drug‑style efficacy claims without evidence commensurate to their pathway and labeling.

Many innovations straddle categories as combination products. In those cases, FDA assigns a lead center and applies the primary mode of action to determine the governing pathway. Understanding how device and drug rules intersect prevents misaligned claims and development inefficiencies. For the regulatory construct that unifies such products, see 21 CFR Part 4 (Combination Products).

The FD&C Act prohibits misbranding, which includes false or misleading statements about regulatory status. A cleared device marketed as “FDA approved” can be misbranded even if it performs well clinically. FDA routinely cites such errors in enforcement actions, requiring corrective communications, labeling updates, and, in some cases, market actions.

Promotional claims must stay within the boundaries of the reviewed indications and the evidence base. Device teams should tether claims to the cleared or approved labeling, risk controls, and performance limitations. For drugs and biologics, approved labeling governs on‑label promotion, and off‑label promotion risks enforcement regardless of clinical plausibility.

Operationally, integrate medical, regulatory, and quality review of all external content. Maintain traceability from claims to submission sections, test reports, and recognized standards. Train commercial teams on the exact verb they may use—cleared, granted, or approved—and the claims this status permits. Audit websites, packaging, and sales materials periodically to catch drift.

When errors occur, act quickly. Withdraw or correct problematic content, document the rationale, and, where necessary, communicate with FDA. Effective corrective and preventive action reduces recurrence and protects patients and brand equity. For understanding enforcement consequences and structured field actions, see recall classification (FDA).

Outside the United States, parallel systems use different verbs and artifacts. In the European Union, medical devices obtain CE marking under the MDR, not “approval” or “clearance.” Canada, Australia, Japan, and other jurisdictions apply classification-based reviews anchored to local statutes and guidance. Translating U.S. outcomes into global claims requires careful mapping to each market’s nomenclature and evidence expectations.

Global regulators converge on principles but diverge in execution. Clinical evidence sufficiency, software lifecycle expectations, human factors, and cybersecurity are increasingly harmonized in substance yet expressed through region‑specific documents. Sponsors should design global evidence plans that satisfy the strictest plausible standards and then tailor submissions to local procedural requirements.

Device verbs do not port directly to medicines. While “approval” is common for drugs worldwide, devices often follow conformity assessment and quality system certification models. Teams should maintain a crosswalk of intended claims, evidence, and regulatory outputs to avoid accidental overstatement when reusing content across markets.

U.S. claims discipline provides a strong spine for global dossiers when combined with precise translations of scope, indications, and performance. Cross‑functional governance that includes regional regulatory leads prevents drift and ensures that each market receives materials aligned to its legal vocabulary and review culture.

Execution starts with a claim strategy matched to risk and evidence feasibility. Map the intended use, user population, and technological characteristics to the likely U.S. pathway. Build an evidence plan that scales from bench to clinical as needed. Use structured pre‑submission engagement to pressure‑test endpoints, acceptance criteria, and cybersecurity posture, and align early on labeling contours and postmarket expectations.

Institutionalize verb discipline across labeling, digital properties, sales training, and media monitoring. Operationalize a single source of truth that links every external claim to dossier sections, test reports, and recognized standards. Maintain inspection readiness through controlled procedures, data integrity by design, and crisp document retrieval. For quality management infrastructure that underpins this discipline, see QMS.

Surround the submission with lifecycle controls. Manage design changes, complaint trending, and signal detection with audit trails and automated workflows. For devices, ensure that human factors, software documentation, and cybersecurity artifacts are version‑controlled and traceable to risks and mitigations. When issues arise, orchestrate timely field actions and corrective communications that speak precisely to the reviewed label.