AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K262015 · Sep 29, 2026
Elucid FFR-IQ (B.1)
Elucid Bioimaging, Inc.
Retrospective clinical medical records (paired CCTA and invasive FFR)
The ELUCIDATE study utilized retrospective clinical data from 11 sites to validate the performance of the Elucid FFR-IQ device against invasive FFR measurements, reflecting real-world clinical conditions and patient populations.
ELUCIDATE (NCT06018194); Retrospective, multicenter study; Follow-up/Duration: Invasive FFR performed within 60 days of CCTA; Study Period: Data collected from 2012 onwards
Clinically stable patients with suspected coronary artery disease requiring CCTA and invasive FFR; Sample Size: 491 vessels across 347 patients; Number of Sites: 11 (9 US, 2 OUS)
Invasive FFR
Sensitivity and specificity of FFR-IQ compared to invasive FFR
ELUCIDATE (NCT06018194): 491 vessels across 347 patients
—
Indications for Use
Elucid FFR-IQ is a coronary physiological simulation software for the clinical quantitative and qualitative analysis of previously acquired Computed Tomography DICOM data for clinically stable patients with known or suspected coronary artery disease. It provides FFR-CT (CT-derived FFR) values estimated from coronary CTA images using AI-enabled algorithms. FFR-IQ is intended to support the functional evaluation of coronary artery disease. The FFR-IQ results are provided to support qualified clinicians to aid in the evaluation and assessment of coronary arteries. FFR-IQ results are intended to be used by qualified clinicians in conjunction with the patient's clinical history, symptoms, and other diagnostic tests, as well as the clinician's professional judgment.
Device Story
Elucid FFR-IQ is a SaaS-based coronary physiological simulation software. It takes previously acquired coronary CTA DICOM images as input. The device uses deep learning neural networks to integrate coronary anatomy and biology (plaque composition/amount) to estimate FFR-CT values along the coronary tree. It utilizes 3D segmentation results from the Plaque-IQ algorithm. The device is used in healthcare facilities, hospitals, or physician offices. Qualified clinicians access the output—graphics and text results—via an internet-connected device. The output supports clinical decision-making by providing non-invasive functional evaluation of coronary artery disease, aiding in the assessment of coronary arteries in conjunction with patient history, symptoms, and other diagnostic tests.
Clinical Evidence
Clinical validation was performed via the ELUCIDATE retrospective, multicenter study (NCT06018194) involving 491 vessels across 347 patients. The study compared FFR-IQ simulated values against invasive FFR (ground truth). Overall results: Sensitivity 92.2% [87.5, 96.5], Specificity 93.1% [90.2, 95.6], PPV 84.4%, NPV 96.7%. US cohort (N=257) showed Sensitivity 90.9% and Specificity 89.2%. The study population was enriched for borderline disease (FFR 0.75-0.85). No adverse events were observed due to the retrospective study design.
Technological Characteristics
Software-as-a-Service (SaaS) coronary vascular physiologic simulation software. Utilizes deep learning neural networks for 3D segmentation and FFR-CT estimation. Requires input from previously acquired CCTA (K241524). Connectivity: Internet-based access for end-users. Complies with ISO 14971 for risk management and FDA software/cybersecurity guidance.
Indications for Use
Indicated for clinically stable adult patients (22 years and older) with known or suspected coronary artery disease requiring functional evaluation of coronary arteries via analysis of previously acquired coronary CTA images.
Regulatory Classification
Identification
A coronary vascular physiologic simulation software device is a prescription device that provides simulated functional assessment of blood flow in the coronary vascular system using data extracted from medical device imaging to solve algorithms and yield simulated metrics of physiologic information (e.g., blood flow, coronary flow reserve, fractional flow reserve, myocardial perfusion). A coronary vascular physiologic simulation software device is intended to generate results for use and review by a qualified clinician.
Special Controls
*Classification.* Class II (special controls). The special controls for this device are:(1) Adequate software verification and validation based on comprehensive hazard analysis, with identification of appropriate mitigations, must be performed, including:
(i) Full characterization of the technical parameters of the software, including:
(A) Any proprietary algorithm(s) used to model the vascular anatomy; and
(B) Adequate description of the expected impact of all applicable image acquisition hardware features and characteristics on performance and any associated minimum specifications;
(ii) Adequate consideration of privacy and security issues in the system design; and
(iii) Adequate mitigation of the impact of failure of any subsystem components (
*e.g.,* signal detection and analysis, data storage, system communications and cybersecurity) with respect to incorrect patient reports and operator failures.(2) Adequate non-clinical performance testing must be provided to demonstrate the validity of computational modeling methods for flow measurement; and
(3) Clinical data supporting the proposed intended use must be provided, including the following:
(i) Output measure(s) must be compared to a clinically acceptable method and must adequately represent the simulated measure(s) the device provides in an accurate and reproducible manner;
(ii) Clinical utility of the device measurement accuracy must be demonstrated by comparison to that of other available diagnostic tests (
*e.g.,* from literature analysis);(iii) Statistical performance of the device within clinical risk strata (
*e.g.,* age, relevant comorbidities, disease stability) must be reported;(iv) The dataset must be adequately representative of the intended use population for the device (
*e.g.,* patients, range of vessel sizes, imaging device models). Any selection criteria or limitations of the samples must be fully described and justified;(v) Statistical methods must consider the predefined endpoints:
(A) Estimates of probabilities of incorrect results must be provided for each endpoint,
(B) Where multiple samples from the same patient are used, statistical analysis must not assume statistical independence without adequate justification, and
(C) The report must provide appropriate confidence intervals for each performance metric;
(vi) Sensitivity and specificity must be characterized across the range of available measurements;
(vii) Agreement of the simulated measure(s) with clinically acceptable measure(s) must be assessed across the full range of measurements;
(viii) Comparison of the measurement performance must be provided across the range of intended image acquisition hardware; and
(ix) If the device uses a cutoff threshold or operates across a spectrum of disease, it must be established prior to validation, and it must be justified as to how it was determined and clinically validated;
(4) Adequate validation must be performed and controls implemented to characterize and ensure consistency (
*i.e.,* repeatability and reproducibility) of measurement outputs:(i) Acceptable incoming image quality control measures and the resulting image rejection rate for the clinical data must be specified, and
(ii) Data must be provided within the clinical validation study or using equivalent datasets demonstrating the consistency (
*i.e.,* repeatability and reproducibility) of the output that is representative of the range of data quality likely to be encountered in the intended use population and relevant use conditions in the intended use environment;(A) Testing must be performed using multiple operators meeting planned qualification criteria and using the procedure that will be implemented in the production use of the device, and
(B) The factors (
*e.g.,* medical imaging dataset, operator) must be identified regarding which were held constant and which were varied during the evaluation, and a description must be provided for the computations and statistical analyses used to evaluate the data;(5) Human factors evaluation and validation must be provided to demonstrate adequate performance of the user interface to allow for users to accurately measure intended parameters, particularly where parameter settings that have impact on measurements require significant user intervention; and
(6) Device labeling must be provided that adequately describes the following:
(i) The device's intended use, including the type of imaging data used, what the device measures and outputs to the user, whether the measure is qualitative or quantitative, the clinical indications for which it is to be used, and the specific population for which the device use is intended;
(ii) Appropriate warnings specifying the intended patient population, identifying anatomy and image acquisition factors that may impact measurement results, and providing cautionary guidance for interpretation of the provided measurements;
(iii) Key assumptions made in the calculation and determination of simulated measurements;
(iv) The measurement performance of the device for all presented parameters, with appropriate confidence intervals, and the supporting evidence for this performance. Per-vessel clinical performance, including where applicable localized performance according to vessel and segment, must be included as well as a characterization of the measurement error across the expected range of measurement for key parameters based on the clinical data;
(v) A detailed description of the patients studied in the clinical validation (
*e.g.,* age, gender, race or ethnicity, clinical stability, current treatment regimen) as well as procedural details of the clinical study (*e.g.,* scanner representation, calcium scores, use of beta-blockers or nitrates); and(vi) Where significant human interface is necessary for accurate analysis, adequately detailed description of the analysis procedure using the device and any data features that could affect accuracy of results.
In combination with the general controls of the FD&C Act. the Coronary Physiologic Simulation Software Device is subject to the following special controls:
{0}
FDA U.S. FOOD & DRUG
ADMINISTRATION
September 29, 2026
Elucid Bioimaging, Inc.
Windi Hary
Chief Quality and Regulatory Officer
399 Boylston St., Suite 400
Boston, Massachusetts 02116
Re: K262015
Trade/Device Name: Elucid FFR-IQ (B.1)
Regulation Number: 21 CFR 870.1415
Regulation Name: Coronary Vascular Physiologic Simulation Software Device
Regulatory Class: Class II
Product Code: PJA
Dated: August 28, 2026
Received: August 31, 2026
Dear Windi Hary:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K262015 - Windi Hary
Page 2
Before making any change significantly affecting the safety or effectiveness of the device, you must submit a new premarket notification in accordance with 21 CFR 807.81. Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
{2}
K262015 - Windi Hary
Page 3
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
STEPHEN C. BROWNING -S
CDR Stephen Browning
Assistant Director
Division of Cardiac Electrophysiology,
Diagnostics, and Monitoring Devices
Office of Cardiovascular Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K262015 | ? |
| Please provide the device trade name(s). | | ? |
| Elucid FFR-IQ (B.1) | | |
| Please provide your Indications for Use below. | | ? |
| Elucid FFR-IQ is a coronary physiological simulation software for the clinical quantitative and qualitative analysis of previously acquired Computed Tomography DICOM data for clinically stable patients with suspected coronary artery disease. It provides FFR-CT (CT-derived FFR) values computed from coronary CTA images using AI-enabled algorithms. FFR-IQ is intended to support the functional evaluation of coronary artery disease.The FFR-IQ results are provided to support qualified clinicians to aid in the evaluation and assessment of coronary arteries. FFR-IQ results are intended to be used by qualified clinicians in conjunction with the with the patient's clinical history, symptoms, and other diagnostic tests, as well as the clinician's professional judgment. | | |
| Please select the types of uses. | Prescription Use (21 CFR 801 Subpart D)Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
| Please select the age group(s) for which the device(s) is to be used. | Neonates/Newborns (Birth to < 29 days old)Infants (29 days old to < 2 years old)Children (2 years old to < 12 years old)Adolescents (12 years old to < 22 years old)Adults (22 years old and greater) | ? |
Page 1 of 1
{4}
Elucid FFR-IQ Traditional 510(k)
510(k) Summary
# 510(k) Summary
## Submitter Information
| Submitter / Manufacturer Name | Elucid Bioimaging, Inc. 399 Boylston Street, Suite 400, Boston, MA 02116 |
| --- | --- |
| Primary Correspondent & Contact Information | Windi Hary Chief Regulatory and Quality Officer Email ID: windi.hary@elucid.com |
| Secondary Correspondent & Contact Information | Hiral Vora Lead Quality and Regulatory Affairs Specialist Email ID: hiral.vora@elucid.com |
| Date Prepared | September 29, 2026 |
## Device Identification
| Proprietary Name | Elucid FFR-IQ (B.1) |
| --- | --- |
| Device Classification Name | Coronary vascular physiologic simulation software device |
| Regulation Description | Coronary vascular physiologic simulation software device |
| Regulation Number | 870.1415 |
| Device Class | Class II |
| Product Code | PJA |
| Device Characteristics | Device is software as a service |
| Environment of Use | Healthcare Facility / Hospital / Physician Office |
## Predicate Device
| Proprietary Name | Heartflow FFRct |
| --- | --- |
| Device Classification Name | Coronary vascular physiologic simulation software device |
| Regulation Description | Coronary vascular physiologic simulation software device |
| 510(k) Number | DEN130045 |
| Regulation Number | 870.1415 |
| Device Class | Class II |
| Product Code | PJA |
| Device Characteristics | Device is software as a service |
| Environment of Use | Healthcare Facility / Hospital / Physician Office |
ELUCID BIOIMAGING, INC.
K262015
Page 1 of 5
{5}
Elucid FFR-IQ Traditional 510(k)
510(k) Summary
## Intended Use
Elucid FFR-IQ is a coronary physiological simulation software for the clinical quantitative and qualitative analysis of previously acquired Computed Tomography DICOM data for clinically stable patients with known or suspected coronary artery disease. It provides FFR-CT (CT-derived FFR) values estimated from coronary CTA images using AI-enabled algorithms. FFR-IQ is intended to support the functional evaluation of coronary artery disease.
The FFR-IQ results are provided to support qualified clinicians to aid in the evaluation and assessment of coronary arteries. FFR-IQ results are intended to be used by qualified clinicians in conjunction with the patient's clinical history, symptoms, and other diagnostic tests, as well as the clinician's professional judgment.
## Device Description
FFR-IQ is a BioIntegrated coronary physiological software for the clinical quantitative and qualitative analysis of previously acquired Computed Tomography DICOM data for clinically stable patients with known or suspected coronary artery disease. It integrates anatomy and biology (such as plaque composition and amount which impacts vasodilation) to estimate FFR-CT values from static coronary CTA images with extracted coronary tree structures using deep learning neural networks. Elucid's FFR-IQ analysis is intended to support the functional evaluation of Coronary Artery Disease. Using the 3D segmentation results of Plaque-IQ, an AI-enabled algorithm assesses FFR-CT (CT-derived FFR) values along the coronary tree.
Elucid's FFR-IQ is deployed and controlled by Elucid. FFR-IQ is AI-enabled.
## Summary of Technological Characteristics
| Comparison Criteria | Subject Device | Predicate Device | Comparison Assessment |
| --- | --- | --- | --- |
| | Elucid FFR-IQ (B.1) | HeartFlow FFRct v1.4 | - |
| 510(k) | K262015 | DEN130045 | - |
| Manufacturer | Elucid Bioimaging, Inc | HeartFlow, Inc. | - |
| Product Code | PJA | PJA | Same as predicate |
| Regulation | 870.1415 | 870.1415 | Same as predicate |
| Device Classification Name | Coronary vascular physiologic simulation software device | Coronary vascular physiologic simulation software device | Same as predicate |
| Device Class | II | II | Same as predicate |
| Input / Data Source | CT / K241524 (CT) | CT | Similar, however Elucid FFR-CT requires the output of K241524 as input |
| Output | Graphics and text results of noninvasively derived FFR-CT that can be | Graphics and text results of noninvasively derived FFR-CT that can be | Same as predicate |
ELUCID BIOIMAGING, INC.
K262015
Page 2 of 5
{6}
Elucid FFR-IQ Traditional 510(k)
510(k) Summary
| Comparison Criteria | Subject Device | Predicate Device | Comparison Assessment |
| --- | --- | --- | --- |
| | accessed by end users/physicians using a device with internet connectivity | accessed by end users/physicians using a device with internet connectivity | |
| Ground Truth for Model Training | Paired CT and invasive FFR data | Paired CT and invasive FFR data | Same |
## Summary of Nonclinical Performance Data
Software verification and validation testing was conducted and documentation provided as recommended in FDA guidance *Content of Premarket Submissions for Device Software Functions*.
Cybersecurity testing was conducted and documentation provided as recommended in FDA guidance document *Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions*.
Human Factors and Usability testing was conducted and documentation provided as recommended in FDA guidance document *Applying Human Factors and Usability Engineering to Medical Devices*.
Results of all current and previously referenced testing concludes the device is acceptable for use.
## Risk Management
Risk management was conducted and documentation provided as recommended in FDA guidance *Content of Premarket Submissions for Device Software Functions* and in accordance with *ISO 14971 Medical Devices – Applications of risk management to medical devices*.
ELUCID BIOIMAGING, INC.
K262015
Page 3 of 5
{7}
Elucid FFR-IQ Traditional 510(k)
510(k) Summary
## Summary of Clinical Validation
### Study Design
ELUCIDATE (NCT06018194) is a retrospective, multicenter study that included eleven study sites in the US (9) and OUS (2), representative of a generalized population and real-world use conditions.
Elucid designed this retrospective study to reflect expected commercial performance, rather than the performance of a prospective study where CT image acquisition and invasive FFR data collection protocols are rigorously supervised, controlled, and unlikely to represent real-world conditions.
The retrospective study design required paired CCTA and invasive FFR for validation purposes; however, the population receiving invasive FFR is necessarily narrower than the population receiving FFR-CT due to the referral pathway that produces both diagnostic tests on the same patient. Under AHA/ACC guidance (Lawton et al. 2021) invasive FFR is performed only when non-invasive assessment cannot resolve the clinical question, predominantly intermediate 40-69% diameter stenosis. The retrospective validation cohort requiring paired CCTA and invasive FFR is therefore drawn from that referred subset and is enriched for borderline disease and significantly weighted in the FFR gray zone of 0.75 - 0.85. The US dataset reflects this enriched population; therefore, the US dataset and subsequent performance reflect a more challenging intended use population than the broader population expected commercially.
Elucid enrolled data from an OUS site which previously collected the data prospectively to represent the portion of the population that is deferred from further invasive assessment. The prospective study protocol under which the data was originally acquired encouraged invasive FFR measurement in all territories regardless of disease state. Thus, clearly non-obstructive, non-ischemic vessels are supplemented where retrospective data is sparse. Differences in the prospective data collection (as defined by the collection protocol for that study) drive differences in the disease prevalence between the US and OUS sites, as well as between the retrospectively and prospectively collected data. To this end, the performance results are reported for the US cohort, the OUS cohort, and the overall validation cohort respectively.
Subjects ages 18 and over with clinically indicated CCTA and invasive FFR performed within 60 days of CCTA. Study design ensured blinding of FFR-CT processing to invasive FFR. The study analyzed 491 vessels across 347 patients.
Enrollment exclusion criteria for patients included:
- Prior coronary artery bypass graft (CABG) or percutaneous intervention (PCI)
- History of myocardial infarction prior to CCTA and/or invasive FFR
- Known complex congenital heart disease
- Existing pacemaker or internal defibrillator lead implantation
- Existing prosthetic heart valve
- Interval clinical myocardial infarction, diagnosis of decompensated heart failure, stroke, or coronary revascularization between CCTA and invasive FFR
ELUCID BIOIMAGING, INC.
K262015
Page 4 of 5
{8}
Elucid FFR-IQ Traditional 510(k)
510(k) Summary
Additional exclusion criteria related to data necessary for analysis included:
- Missing CCTA for analysis
- Missing invasive coronary angiography imaging or adequate description defining the position of the invasive FFR wire location
- Non-diagnostic CCTA or invasive FFR
- Poor CCTA image quality that does not meet Elucid image processing requirements for plaque and FFR-CT
- CCTA or invasive FFR performed prior to January 1, 2012
- Absence of study date for CCTA or invasive FFR
- Patients who had IFR or CFR, and not measured FFR
FFR-IQ was used to simulate FFR-CT from the subject's CT. The FFR-CT was then compared to the invasively collected FFR to assess the device performance.
## Primary Safety and Effectiveness Endpoints
The primary endpoints regarding this study were sensitivity and specificity to have the lower limits of their 95% CI to be > 75%. These performance goals were not necessarily determined to be sufficient for substantial equivalence, but the performance demonstrated by the results was.
## Study Results
The ELUCIDATE overall study results as well as the separate US cohort met the primary endpoints.
| Per vessel | US cohort results | Overall Results |
| --- | --- | --- |
| Sensitivity | 90.9 [85.1, 96.5] | 92.2 [87.5, 96.5] |
| Specificity | 89.2 [83.9, 93.7] | 93.1 [90.2, 95.6] |
| Unadjusted PPV | 84.1 [77.7, 90.5] | 84.4 [79.2, 89.3] |
| Unadjusted NPV | 94.0 [90.0, 97.6] | 96.7 [94.8, 98.5] |
| Bland-Altman LoA | 0.19 [-0.09 - 0.10] | 0.23 [-0.10 - 0.13] |
| Sample size | N = 257 | N = 491 |
| NXT Predicate results |
| --- |
| 84 [75, 89] |
| 86 [82, 89] |
| 61 [53, 69] |
| 95 [93, 97] |
| 0.30 [-0.12 - 0.18] |
| N = 484 |
Due to the retrospective nature of the study, there were no adverse events or complications observed in the study.
## Conclusion
While there are differences noted in the technological characteristics of the proposed device and the predicate device, namely that the predicate uses computational fluid dynamics and the subject device does not, the differences do not raise different questions of safety or effectiveness. Non-clinical verification and validation, along with clinical performance data, collectively support substantial equivalence of the subject device to the predicate.
ELUCID BIOIMAGING, INC.
K262015
Page 5 of 5
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Guidance alerts
New and changed FDA guidance documents, emailed as a daily digest.
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the ? button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only Software as a Medical Device, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (Software as a Medical Device), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.