FDA intelligence
Guidance, policy, pathways, and product impact in the United States.
Explore this topicGet startedIntelligence & resources
Help every professional move from an authority update to a product-level decision with the source, context, and next action close at hand.

Intelligence domains
Guidance, policy, pathways, and product impact in the United States.
Explore this topicGet startedEU regulations, guidance, notified-body expectations, and lifecycle change.
Explore this topicGet startedClassification, evidence, quality, software, and post-market expectations.
Explore this topicGet startedDevelopment, CMC, clinical, submission, and lifecycle intelligence.
Explore this topicGet startedSpecialized evidence, manufacturing, follow-up, and jurisdictional expectations.
Explore this topicGet startedPrimary mode of action, constituent parts, agency coordination, and integrated evidence.
Explore this topicGet startedMedical device regulatory basics
General education for founders, Regulatory Affairs (RA), Quality Assurance (QA), manufacturers, and consultants. Requirements depend on the device and jurisdiction. Published by eeRegOS. Updated ; qualified regulatory review is recommended before applying this information to a product.
Regulatory text: 21 CFR Part 807, Subpart E — Premarket Notification and 21 CFR Part 820 — QMSR. Regulations establish applicable requirements; agency guidance and educational summaries explain context and may include nonbinding recommendations.
Medical device regulatory compliance means meeting the applicable obligations for developing, manufacturing, marketing, and monitoring a device. In the United States, these can include classification, premarket review, quality systems, labeling, registration, listing, and post-market reporting. The obligations vary; some devices are exempt from particular requirements. FDA overview of device regulation.
A 510(k) is a premarket notification demonstrating substantial equivalence to a legally marketed predicate device. FDA evaluates intended use, technological characteristics, and supporting evidence. A successful 510(k) results in clearance. Device-specific exemptions and limitations matter. FDA explanation of premarket notification.
| Pathway | General basis | FDA outcome |
|---|---|---|
| 510(k) | Substantial equivalence to a legally marketed predicate, where applicable. | Clearance |
| De Novo | Novel device without a predicate, where general controls or general and special controls can provide reasonable assurance of safety and effectiveness. | Classification into Class I or II |
| PMA | Safety and effectiveness evidence for Class III devices subject to premarket approval. | Approval |
These pathways are not interchangeable; this is not an exhaustive list. FDA comparison of device review pathways.
A predicate is a legally marketed device used as the comparator for a 510(k) substantial-equivalence assessment. A matching product code or similar name alone does not establish suitability. Review intended use, technological characteristics, legal marketing status, and supporting evidence. FDA predicate and substantial-equivalence definitions.
Design controls are documented processes for translating user needs into design requirements, reviewing development, verifying outputs, validating intended use, transferring design to production, and managing changes. Applicability must be checked against the current quality-system requirements. Under QMSR, design and development requirements are addressed through incorporated ISO 13485 provisions and FDA-specific requirements. FDA QMSR questions and answers.
ISO 13485:2016 specifies quality management system requirements for organizations involved in medical devices and related services. Certification alone does not establish compliance with every applicable FDA obligation. ISO 13485:2016 standard overview.
The Quality Management System Regulation (QMSR) is FDA's revised 21 CFR Part 820. It became effective February 2, 2026, incorporating ISO 13485:2016 by reference alongside FDA-specific provisions. Use the current requirements when assessing quality-system readiness. FDA QMSR FAQ and effective date.
A readiness assessment is a structured review of available evidence against the requirements relevant to a product and proposed pathway. Teams identify gaps, assign owners, and record unresolved assumptions. A software readiness score is a planning aid; it does not establish regulatory compliance or predict an FDA decision.
AI can help organize source material, research pathways, compare candidate predicates, highlight evidence gaps, and prepare drafts for review. eeRegOS supports these workflows through regulatory AI assistance, pathway analysis, predicate search, readiness assessments, document workflows, and expert review. Features depend on available sources, project evidence, configuration, and subscription.
Explore eeRegOS regulatory workflows or compare subscription plans.
AI output can be incomplete, outdated, or incorrect. Citations must be checked for relevance and currency. Qualified professionals should review product-specific conclusions, evidence, and drafts. eeRegOS does not guarantee clearance, approval, compliance, or submission success, and regulatory decisions remain with the responsible team and authorities.
Built around your team
eeRegOS supports judgment instead of replacing it—giving each person shared context, traceable evidence, and a clear path to the next decision.
See portfolio risk, evidence, and decisions without chasing updates across systems.
Move from research to documented recommendations with sources and context intact.
Coordinate gaps, reviews, tasks, and submission evidence through accountable workflows.
Understand the next regulatory decision and bring the right experts in at the right time.
From update to action
See which products are affected, why the change matters, and what your team should do next.