MedDeviceGuideMedDeviceGuide
Back

FDA AI-Enabled Device Predicate Mining for 510(k) and De Novo

Method for mining FDA AI-enabled device and 510(k) databases to identify predicates, compare technology, avoid weak arguments, and build a defensible predicate matrix.

Ran Chen
Ran Chen
Global MedTech Expert | 10× MedTech Global Access
Published 2026-05-05Last reviewed 2026-05-0514 min read

What This Article Covers / Does Not Cover

This article covers one specific task: how to use FDA's public AI-enabled medical device list, the 510(k) database, and publicly available summary documents to identify, evaluate, and defend a predicate device for an AI-enabled medical device seeking 510(k) clearance or De Novo classification. It includes a predicate mining workflow, a technological characteristic extraction table, a predicate strength scoring matrix, and common failure modes specific to AI-enabled devices.

This article does not cover the general 510(k) submission process, how to write a substantial equivalence argument from scratch, or how to prepare performance testing data. For the general 510(k) framework, see 510(k) Submission Guide. For predicate device selection fundamentals, see 510(k) Predicate Device Guide. For the broader AI/ML regulatory landscape, see AI/ML Medical Device Regulatory Guide.


Why AI-Enabled Device Predicate Mining Is Different

Approximately 97% of FDA-authorized AI-enabled medical devices have been cleared through the 510(k) pathway. Through the end of 2025, FDA's list contains over 1,450 cumulative authorized AI-enabled devices. In 2025 alone, 295 AI/ML-enabled devices received clearance, with 211 (71.5%) in radiology, 26 (8.8%) in cardiovascular, and 14 (4.7%) in neurology.

But AI-enabled devices present unique predicate challenges:

  1. Software opacity: Public 510(k) summary statements rarely describe AI architecture, model type, training data characteristics, or inference pipeline details.

  2. Rapid evolution: A predicate cleared two years ago may use fundamentally different technology than what is standard today.

  3. Mixed technology comparisons: FDA permits AI-enabled devices to be found substantially equivalent to non-AI-enabled predicates if no new questions of safety and effectiveness are raised (per FDA's draft AI-enabled device software functions guidance, January 2025).

  4. Sparse non-radiology predicates: Outside radiology, the predicate pool shrinks dramatically, forcing sponsors toward De Novo or toward weaker predicate arguments.


Step 1: Define Your Technological Characteristic Profile

Before searching for predicates, document your own device's technological characteristics in a structured format. FDA evaluates substantial equivalence along two axes: intended use and technological characteristics. The table below provides the characteristic categories most relevant to AI-enabled devices.

Technological Characteristic Extraction Table

Characteristic CategoryData to DocumentSource in Your Documentation
Intended use / indicationsSpecific clinical indication, patient population, clinical setting, user typeIFU, intended use statement
AI function typeDetection, triage, quantification, segmentation, diagnosis, treatment recommendation, workflow optimizationSoftware design specification
Input data modalityCT, MRI, X-ray, ultrasound, ECG, pathology slide, clinical text, physiological waveformSoftware requirements spec
Anatomy / physiologyOrgan system, anatomical region, physiological parameterDevice description
AI/ML approachDeep learning (CNN, transformer, etc.), classical ML, rule-based, hybridAlgorithm design document
Output typeBinary classification, multi-class, bounding box, segmentation mask, continuous score, text reportOutput specification
IntegrationStandalone SaMD, embedded in hardware, PACS-integrated, EHR-integrated, cloud-deployed, edge-deployedArchitecture document
Clinical workflow positionTriaging/screening, diagnostic aid, clinical decision support, second read, quality checkIntended use / clinical evaluation
Human oversightHuman-in-the-loop, human-over-the-loop, autonomousRisk management file
Training data characteristicsDataset size, demographics, multi-site vs single-site, ground truth methodAI/ML performance validation report
Performance metricsSensitivity, specificity, AUROC, Dice coefficient, PPV, NPV, F1 — with confidence intervalsClinical/performance validation
PCCP inclusionWhether a predetermined change control plan is includedPCCP document
Product codeFDA product code(s) applicableClassification determination
Review panelRadiology, Cardiovascular, Neurology, etc.Classification database

Recommended Reading
DHTs as Endpoints in Device Investigations: Investigational Device vs Measurement Tool
Clinical EvidenceDigital Health & AI2026-08-29 · 22 min read

Step 2: Mine the FDA AI-Enabled Device List

2.1 Access the List

FDA publishes the "Artificial Intelligence-Enabled Medical Devices" list on its website at fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-enabled-medical-devices. The list is downloadable in CSV, Excel, and XML formats. It contains:

  • Date of final decision

  • Submission number (e.g., K252379)

  • Device name

  • Company name

  • Panel (lead review division)

  • Primary product code

2.2 Filter Strategically

Apply filters in this order:

Filter PriorityFieldWhy
1Primary product codeNarrows to your device's regulatory family
2Panel (review division)Ensures same clinical domain
3Date of final decisionPrefer predicates cleared within the last 5 years
4Company nameSame-manufacturer predicates simplify comparison
5Device name keywordFunctional similarity screening

2.3 Record Candidate Predicates

For each candidate identified, create a predicate candidate card:

FieldYour DeviceCandidate Predicate
510(k) / De Novo number(to be assigned)K25XXXXX
Device name[Your device][Predicate device]
Company[Your company][Predicate company]
Product code[Your code(s)][Predicate code]
Panel[Your panel][Predicate panel]
Intended use[Yours][From public summary]
Clearance date[Date]
Still marketed?[To verify]

Step 3: Extract Technological Characteristics from Public Summaries

3.1 What Public Summaries Actually Contain

FDA's publicly available 510(k) summary statements (found in the 510(k) database) typically include:

  • Device description (sometimes detailed, sometimes vague)

  • Intended use statement

  • Comparison to predicate(s): intended use, technological characteristics

  • Summary of performance testing

  • Brief statement on software validation

  • Conclusion on substantial equivalence

3.2 What Public Summaries Almost Never Contain

Missing InformationImpact on Your SE Argument
AI model architecture detailsCannot verify algorithmic equivalence
Training dataset size/compositionCannot compare training rigor
Specific performance metrics with CIsCannot do quantitative comparison
Preprocessing pipeline detailsMay need to assume differences
Post-processing logicOften a source of hidden differences
Cybersecurity controlsIncreasingly scrutinized for AI devices
Cloud/edge deployment architectureRelevant for cybersecurity and performance

3.3 Technological Characteristic Comparison Matrix

Build this matrix for every candidate predicate. Use "Same," "Different," or "Unknown" for each row:

CharacteristicYour DevicePredicateAssessmentEvidence Source
Intended use[Yours][Theirs]Same/DifferentPublic summary
Input data modality[Yours][Theirs]Same/DifferentPublic summary
AI function type[Yours][Theirs/Unknown]Same/Different/UnknownPublic summary or inferred
Anatomy/physiology[Yours][Theirs]Same/DifferentPublic summary
Output type[Yours][Theirs/Unknown]Same/Different/UnknownPublic summary
Clinical workflow position[Yours][Theirs/Unknown]Same/Different/UnknownInferred from IFU
Human oversight model[Yours][Theirs/Unknown]Same/Different/UnknownOften not stated
Software architecture[Yours][Theirs/Unknown]Different/UnknownAlmost never stated
Performance level[Yours with CIs][Theirs/Unknown]Comparable/UnknownPublic summary if available

Step 4: Predicate Strength Scoring

Score each candidate predicate on a 1-5 scale across the following dimensions. A score below the threshold means the predicate is too weak to rely on as a primary predicate.

Predicate Strength Scoring Matrix

DimensionWeight5 (Strong)3 (Moderate)1 (Weak)
Intended use match30%Identical indications, population, settingOverlapping but narrower or broaderDifferent clinical indication or population
Technological similarity25%Same modality, function, output typeSame modality, different function or outputDifferent modality or fundamentally different technology
Product code match15%Same product codeRelated product code, same panelDifferent product code, different panel
Currency10%Cleared within 2 yearsCleared within 5 yearsCleared more than 5 years ago
Regulatory history10%Clean, no recalls or safety alertsMinor issues resolvedRecalls, warning letters, or withdrawal
Information availability10%Detailed public summary with performance dataBasic public summaryMinimal or no public information

Weighted score threshold: A weighted score below 3.0 indicates a weak predicate. Below 2.5, consider De Novo or a different predicate strategy.

Decision Tree: Primary Predicate vs. Multiple Predicates vs. De Novo

START: Is there a candidate with weighted score >= 3.5?
├── YES → Use as primary predicate
│   └── Are there gaps in technological characteristics?
│       ├── NO → Proceed with single-predicate SE argument
│       └── YES → Can gaps be addressed with additional reference devices?
│           ├── YES → Add secondary predicate(s) for specific features
│           └── NO → Address gaps with performance testing data
└── NO → Is there a candidate with weighted score 2.5-3.5?
    ├── YES → Can additional performance data bridge the gap?
    │   ├── YES → Strengthen SE argument with robust testing
    │   └── NO → Consider Pre-Submission meeting with FDA
    └── NO → Is there ANY candidate with score >= 2.0?
        ├── YES → De Novo may be more appropriate
        └── NO → De Novo pathway is likely required

Recommended Reading
Does This US IVD Study Need an IDE, an IND, or Neither?
IVD & DiagnosticsClinical Evidence2026-09-15 · 28 min read

Step 5: Avoid Weak Predicate Arguments

Common Failure Modes for AI-Enabled Device Predicates

Failure ModeWhat It Looks LikeWhy FDA Rejects ItHow to Fix It
Functional mismatchYour device detects lung nodules; predicate triages chest X-raysDifferent intended use despite same anatomyFind a predicate with matching AI function, or do De Novo
"AI as feature" argumentClaiming AI is just a different implementation of the same clinical functionIf AI introduces new analysis capability, it may raise new questions of safety/effectivenessDemonstrate that AI output is clinically equivalent to predicate's non-AI output
Stale predicatePredicate cleared in 2018 with outdated technologyFDA may question whether the predicate reflects current standard of careUse a more recent predicate or provide evidence that the older predicate is still clinically relevant
Unknown performance gapCannot determine predicate's sensitivity/specificity from public dataFDA may request additional clinical validationConduct clinical validation study; consider Pre-Submission
Cross-panel predicateYour device is Cardiovascular; predicate is RadiologyDifferent review panels, different clinical expertiseFind same-panel predicate or engage FDA early via Pre-Submission
Multiple predicate assemblyCobbling together 3+ predicates for different featuresSE argument becomes incoherent; each predicate must share the same intended useUse one primary predicate for intended use; reference devices for specific tech comparisons only
Non-AI to AI gapPredicate is non-AI; your device adds AI analysisFDA's January 2025 draft guidance permits this IF no new safety/effectiveness questionsProvide performance data showing AI output is equivalent or superior to predicate's manual process

Reviewer Objection Table

Reviewer ObjectionTypical FDA LanguageHow to Respond
Different intended use"The subject device's intended use is broader than the predicate"Narrow your indications or find a better-matched predicate
New questions of safety"The AI component introduces a new mechanism of analysis not present in the predicate"Provide clinical validation data, risk analysis, and performance comparison
Insufficient comparison"The technological characteristics comparison does not adequately address differences in the software algorithm"Supplement with detailed algorithm description, V&V data, and performance testing
Performance gap"The submitted performance data does not demonstrate comparable safety and effectiveness"Conduct additional clinical validation; consider De Novo

Step 6: Use Pre-Submission to De-Risk Predicate Strategy

FDA's Pre-Submission program (Q-Submission) allows you to get feedback on your predicate strategy before committing to a full 510(k) or De Novo submission. For AI-enabled devices, this is especially valuable when:

  1. Your best predicate scores between 2.5 and 3.5 on the strength matrix

  2. You are considering a non-AI to AI comparison

  3. You are outside radiology (where predicates are sparse)

  4. You plan to use multiple predicates

Pre-Submission Predicate Package Contents

DocumentPurpose
Proposed intended use statementFor FDA to confirm intended use alignment
Predicate identification tableShow candidate predicates with scoring rationale
Technological comparison matrixHighlight similarities and differences
Proposed performance testing planShow how you plan to address differences
Specific questions for FDANumbered, focused questions about predicate acceptability

Illustrative Pre-Submission question format:

"We have identified [K-number] as our primary predicate device. Our device shares the same intended use (detection of [condition] from [modality]), same input data type, and same clinical workflow position. The primary technological difference is [describe]. We plan to address this difference with [proposed testing]. Does FDA agree that this predicate and testing approach are appropriate for a 510(k) submission?"


Step 7: Document the Predicate Strategy in Your Submission

Evidence Traceability Table

Submission SectionPredicate-Related ContentEvidence Records
Device descriptionSide-by-side device description comparisonDevice description document, predicate public summary
Substantial equivalenceIntended use comparison, technological characteristics comparison, performance comparisonSE narrative, comparison tables
Software documentationSoftware architecture comparison (where available), V&V summaryIEC 62304 documentation, software description
Performance testingBench/clinical testing bridging technological differencesTest reports, statistical analysis
Clinical evaluationClinical validation study results vs. predicate performance (where available)Clinical evaluation report, validation study report
Labeling comparisonIFU comparison tableIFU/labeling documents

RACI for Predicate Mining Process

TaskRegulatory AffairsEngineering/ClinicalQualityManagement
Define technological profileCRIA
Search FDA AI device listRCII
Extract public summary dataRCII
Score candidate predicatesRCIA
Conduct Pre-Submission (if needed)RCIA
Build SE comparison tablesRCII
Review final predicate strategyCCCA

Recommended Reading
FDA eSTAR Electronic Submission Template: Complete Guide to 510(k) and De Novo Submissions
510(k)Regulatory2026-04-17 · 16 min read

Common Failure Modes and Remediation

Failure ModeRoot CauseRemediation
Predicate no longer marketedDid not verify market status before submissionCheck predicate company website, FDA registration listings, and distributor catalogs before committing to a predicate
Predicate recalled after selectionDid not monitor predicate regulatory status during submission preparationSet up FDA recall database alerts for selected predicates
Inadequate public informationChose predicate with minimal public summaryPrefer predicates with detailed public summaries; contact predicate manufacturer for additional information if appropriate
AI function differs from predicateAssumed AI analysis is interchangeable with non-AI analysisProvide clinical validation showing equivalence; consider De Novo if the AI function is fundamentally new
Product code mismatchDid not verify classification before selecting predicateUse FDA Product Classification Database to confirm product code assignment
Weak multiple-predicate argumentAssembled predicates that do not share intended useEnsure all predicates share the same intended use; use reference devices only for specific technological comparisons

Sources

  • FDA. "Artificial Intelligence-Enabled Medical Devices." Updated through December 2025. fda.gov/medical-devices/software-medical-device-samd/artificial-intelligence-enabled-medical-devices

  • FDA. "Artificial Intelligence-Enabled Device Software Functions: Lifecycle Considerations and Premarket Review Recommendations." Draft Guidance, January 2025.

  • Innolitics. "2025 Year in Review: AI/ML Medical Device 510(k) Clearances." innolitics.com/articles/year-in-review-ai-ml-medical-device-k-clearances/

  • IntuitionLabs. "FDA's AI Medical Device List: Stats, Trends & Regulation." Updated March 2026.

  • FDA. "The 510(k) Program: Evaluating Substantial Equivalence in Premarket Notifications." Guidance.

  • Complizen. "What Is Substantial Equivalence (SE) in FDA 510(k)? Definition & Criteria." 2025.