K251009 · Sora Neuroscience, Inc. · QIH · Jun 6, 2025 · Radiology
Device Facts
Record ID
K251009
Device Name
Cirrus Resting State fMRI Software
Applicant
Sora Neuroscience, Inc.
Product Code
QIH · Radiology
Decision Date
Jun 6, 2025
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device, Real-World Evidence, Pediatric
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K251009 · Jun 6, 2025
Cirrus Resting State fMRI Software
Sora Neuroscience, Inc.
Retrospective patient MRI datasets (brain tumor and epilepsy patients); Published clinical literature (Dierker et al., Mitchell et al., Park et al., Roland et al.)
Retrospective clinical patient data and published clinical literature were used to validate the accuracy of the device's generated resting state network (RSN) maps (SMN, LAN, and VIS) by comparing them to established clinical standards and task-based fMRI results.
Retrospective Validation of SMN and LAN Maps; Retrospective analysis of clinical patient MRI datasets; Follow-up/Duration: Not applicable
Brain tumor and epilepsy patients (ages 3 to 71 years)
Resting state network maps from published literature (Dierker et al., Mitchell et al., Park et al., Roland et al.)
Spatial correlation of SMN and LAN maps
Retrospective Validation of VIS Maps; Retrospective ROC analysis; Follow-up/Duration: Not applicable
26 brain tumor and epilepsy adult and pediatric patients; Sample Size: 26
Same-patient task-activated vision maps
Area under the ROC curve (AUC)
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Sensorimotor network (SMN) map
Nonadaptive machine-learning based resting state network membership scoring algorithm
—
Mean 0.826 spatial correlation with published literature maps
Training and optimization: 48 subjects (19M + 29F) from a US clinical research institute
—
Validation: 692 subjects (305M + 387F) from a second US clinical research institute; Retrospective validation: brain tumor and epilepsy patients (ages 3-71 years) compared to published literature
—
Language network (LAN) map
Nonadaptive machine-learning based resting state network membership scoring algorithm
—
Mean 0.793 spatial correlation with published literature maps
Training and optimization: 48 subjects (19M + 29F) from a US clinical research institute
—
Validation: 692 subjects (305M + 387F) from a second US clinical research institute; Retrospective validation: brain tumor and epilepsy patients (ages 3-71 years) compared to published literature
—
Vision network (VIS) map
Nonadaptive machine-learning based resting state network membership scoring algorithm
—
Mean area under the ROC curve of 0.84
Training and optimization: 48 subjects (19M + 29F) from a US clinical research institute
—
Validation: 692 subjects (305M + 387F) from a second US clinical research institute; Retrospective validation: 26 brain tumor and epilepsy patients (adult and pediatric) compared to task-activated vision maps
—
Indications for Use
Cirrus Resting State fMRI Software (Cirrus) is a software solution that performs magnetic resonance image processing including the processing of blood oxygen level dependent (BOLD) functional magnetic resonance imaging (fMRI) data, resting state fMRI analysis, and output generation. Cirrus generates task-analogous motor, language, and vision resting state fMRI correlation maps, in DICOM® format for visualization and analysis external to Cirrus. Cirrus maps have been found to vary in normal subjects tested by repeat MR acquisition under conditions where no functional mapping change was expected. Medical imaging processing systems intended for BOLD fMRI post-processing are adjunctive and not intended to replace direct functional mapping procedures. Typical users of Cirrus are medical professionals, including but not limited to surgeons, radiologists, and other clinicians.
Device Story
Cirrus is SaMD that processes patient brain MRI datasets (BOLD fMRI and structural MRI). It performs fMRI preprocessing, computes correlation matrices, and uses a nonadaptive machine-learning algorithm to generate resting state network (RSN) membership scores. Output consists of task-analogous motor, language, and vision correlation maps in DICOM format, accompanied by a quality report. Used in clinical settings by surgeons, radiologists, and clinicians to assist in preoperative functional mapping. Output maps are visualized externally to aid clinical decision-making regarding functional cortex localization. Benefits include providing non-invasive functional mapping data for patients with brain tumors or epilepsy, serving as an adjunct to standard task-based fMRI or intraoperative stimulation.
Clinical Evidence
Validation included retrospective analysis of patient MRI datasets (ages 3-71, brain tumor/epilepsy). SMN and LAN maps showed mean spatial correlations of 0.826 and 0.793 respectively compared to literature. VIS map validation via ROC analysis (n=26) yielded mean AUC of 0.84 vs task-activated maps. Cross-scanner validation (Siemens vs GE) confirmed within-subject similarity > cross-subject similarity (p<0.001). Training/testing used datasets (N=48 and N=692) of healthy adults.
Technological Characteristics
SaMD; processes BOLD fMRI and structural MRI. Nonadaptive ML-based RSN membership scoring algorithm. Outputs DICOM-formatted correlation maps. Complies with ISO 13485:2016, IEC-62304:2006+A1:2015, ISO 14971:2019, AAMI TIR57:2016/R2019, and NEMA PS 3.1-3.20 2024e (DICOM).
Indications for Use
Indicated for use by medical professionals (surgeons, radiologists, clinicians) to process BOLD fMRI and structural MRI data to generate task-analogous motor, language, and vision resting state correlation maps. Used for adult, adolescent, and child patients (ages 3 to 71 years) including those with brain tumors or epilepsy. Adjunctive use only; not to replace direct functional mapping procedures.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
Predicate Devices
Omniscient Neurotechnology Pty Ltd (o8t), Quicktome Software Suite (K222359)
Reference Devices
Dierker et al. (2017) Neuroimaging Clin N Am
Hacker et al. (2013) Neuroimage
Mitchell et al. (2013) Neurosurgery
Park et al. (2020) PLoS One
Roland et al. (2019) Neuroimage Clin
Submission Summary (Full Text)
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
June 6, 2025
Sora Neuroscience, Inc.
% John Smith
Partner
Hogan Lovells US LLP
Columbia Square
555 Thirteenth Street, NW
Washington, District of Columbia 20004
Re: K251009
Trade/Device Name: Cirrus Resting State fMRI Software
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: QIH
Dated: April 1, 2025
Received: April 1, 2025
Dear John Smith:
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}
K251009 - John Smith
Page 2
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 System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 systems (QS) regulation (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.
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-
{2}
K251009 - John Smith
Page 3
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,

Daniel M. Krainak, PhD
Assistant Director
DHT8C: Division of Radiological
Imaging and Radiation Therapy Devices
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
FORM FDA 3881 (8/23)
Page 1 of 1
PSC Publishing Services (301) 443-6740
EF
| DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration Indications for Use | Form Approved: OMB No. 0910-0120 Expiration Date: 07/31/2026 See PRA Statement below. |
| --- | --- |
| 510(k) Number (if known) K251009 | |
| Device Name Cirrus Resting State fMRI Software | |
| Indications for Use (Describe) Cirrus Resting State fMRI Software (Cirrus) is a software solution that performs magnetic resonance image processing including the processing of blood oxygen level dependent (BOLD) functional magnetic resonance imaging (fMRI) data, resting state fMRI analysis, and output generation. Cirrus generates task-analogous motor, language, and vision resting state fMRI correlation maps, in DICOM® format for visualization and analysis external to Cirrus. Cirrus maps have been found to vary in normal subjects tested by repeat MR acquisition under conditions where no functional mapping change was expected. Medical imaging processing systems intended for BOLD fMRI post-processing are adjunctive and not intended to replace direct functional mapping procedures. Typical users of Cirrus are medical professionals, including but not limited to surgeons, radiologists, and other clinicians. | |
| Type of Use (Select one or both, as applicable) ☑ Prescription Use (Part 21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | |
| CONTINUE ON A SEPARATE PAGE IF NEEDED. | |
| This section applies only to requirements of the Paperwork Reduction Act of 1995. *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.* | |
| The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to: Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff@fda.hhs.gov | |
| "An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number." | |
{4}
510(k) SUMMARY
Cirrus Resting State fMRI
(K251009)
**Submitter**
Sora Neuroscience, Inc.
4406 Beard Ave. S., Suite UL2
Minneapolis, MN 55410
+1 612-234-1766
Contact Person: Stephen Schaefer
Date Prepared: June 4, 2025
**Device**
**Name of Device:** Cirrus Resting State fMRI Software
**Common or Usual Name:** Functional MRI Post-Processing Software
**Classification Name:** Medical image management and processing system (21 CFR 892.2050)
**Regulatory Class:** Class II
**Product Code:** QIH
**Predicate Device**
Omniscient Neurotechnology Pty Ltd (o8t), Quicktome Software Suite, K222359.
**Device Description**
Cirrus Resting State fMRI Software (Cirrus) is software as a medical device (SaMD) that performs image processing, resting state functional magnetic resonance imaging analysis, and output generation. Cirrus is launched by a host computing system external of Cirrus.
Cirrus processes an individual patient's brain magnetic resonance imaging (MRI) dataset which includes blood oxygenation level dependent (BOLD) functional MRI (fMRI) data and structural MRI data. Software components making up Cirrus include (i) a suite of fMRI preprocessing tools; (ii) a voxel-wise resting state fMRI correlation map generator, (iii) a nonadaptive machine-learning based resting state network (RSN) membership scoring algorithm; and (iv) an RSN map output generator.
The output of Cirrus is a set of patient-specific, task-analogous motor, language, and vision resting state fMRI correlation maps. The output maps correspond to three canonical, predefined brain resting state networks:
{5}
- Sensorimotor network (SMN),
- Language network (LAN), and
- Vision network (VIS).
Output resting state network maps are provided in DICOM® format for visualization and analysis external of Cirrus and accompanied by a quality report.
## Intended Use / Indications for Use
Cirrus Resting State fMRI Software (Cirrus) is a software solution that performs magnetic resonance image processing including the processing of blood oxygen level dependent (BOLD) functional magnetic resonance imaging (fMRI) data, resting state fMRI analysis, and output generation. Cirrus generates task-analogous motor, language, and vision resting state fMRI correlation maps, in DICOM® format for visualization and analysis external to Cirrus.
Cirrus maps have been found to vary in normal subjects tested by repeat MR acquisition under conditions where no functional mapping change was expected. Medical imaging processing systems intended for BOLD fMRI post-processing are adjunctive and not intended to replace direct functional mapping procedures.
Typical users of Cirrus are medical professionals, including but not limited to surgeons, radiologists, and other clinicians.
## Summary of Technological Characteristics as Compared to Predicate
Both the subject device and predicate device are based on the same scientific and technological principle, namely, that spontaneous neural activations revealed in resting state BOLD fMRI data exhibit temporal correlation within functionally connected brain locations. At a high level, both the subject device and predicate device have these same technological elements:
- Both are software applications for post-processing resting state BOLD fMRI data.
- Both co-register BOLD fMRI data with anatomical scan data.
- Both perform fMRI preprocessing on the resting state BOLD fMRI data.
- Both compute a correlation matrix for the resting state BOLD fMRI data.
- Both perform resting state fMRI analysis to generate output task-analogous motor, language, and vision resting state fMRI correlation maps.
To the extent technological differences exist between the subject device and the predicate device regarding the details of their respective BOLD fMRI preprocessing pipelines and methodologies for resting state fMRI analysis, the technological characteristics of the subject device do not raise new questions of safety or effectiveness.
{6}
Performance Data
The design and development of Cirrus complies with direction found in ISO 13485:2016 (Medical device quality management requirements and systems), IEC-62304:2006 + A1:2015 (Software life cycle processes), ANSI/AAMI/ISO 14971:2019 (Risk management for medical devices), AAMI TIR57:2016/R2019 (Medical device security / risk management), and NEMA PS 3.1-3.20 2024e (DICOM set).
Machine learning algorithm training, optimization, and testing used data sets that were acquired at a US clinical research institute (N = 48: 19M + 29F). A second, large data set (acquired at a second US clinical research institute) was used for further testing (N = 692: 305M + 387F). All subjects were adults screened to exclude neurological impairment and psychotropic medications.
Software unit testing, verification testing, clinical performance validation testing, host platform testing, and cybersecurity penetration testing have been conducted upon Cirrus according to defined protocols. In all instances, Cirrus functioned as intended and output resting state network (RSN) maps and accompanying quality reports generated by Cirrus were as expected.
Cirrus' clinical performance was demonstrated by results from analyses conducted by Sora and published literature including:
- Dierker et al. (2017): Dierker D, Roland JL, Kamran M, Rutlin J, Hacker CD, Marcus DS, Milchenko M, Miller-Thomas MM, Benzinger TL, Snyder AZ, Leuthardt EC, Shimony JS. Resting-state Functional Magnetic Resonance Imaging in Presurgical Functional Mapping: Sensorimotor Localization. Neuroimaging Clin N Am. 2017 Nov;27(4):621-633. doi: 10.1016/j.nic.2017.06.011. PMID: 28985933; PMCID: PMC5773116.
- Hacker et al. (2013): Hacker CD, Laumann TO, Szrama NP, Baldassarre A, Snyder AZ, Leuthardt EC, Corbetta M. Resting state network estimation in individual subjects. Neuroimage. 2013 Nov 15;82:616-633. doi: 10.1016/j.neuroimage.2013.05.108. Epub 2013 Jun 2. PMID: 23735260; PMCID: PMC3909699.
- Mitchell et al. (2013): Mitchell TJ, Hacker CD, Breshears JD, Szrama NP, Sharma M, Bundy DT, Pahwa M, Corbetta M, Snyder AZ, Shimony JS, Leuthardt EC. A novel data-driven approach to preoperative mapping of functional cortex using resting-state functional magnetic resonance imaging. Neurosurgery. 2013 Dec;73(6):969-82; discussion 982-3. doi: 10.1227/NEU.0000000000000141. PMID: 24264234; PMCID: PMC3871406.
- Park et al. (2020): Park KY, Lee JJ, Dierker D, Marple LM, Hacker CD, Roland JL, Marcus DS, Milchenko M, Miller-Thomas MM, Benzinger TL, Shimony JS, Snyder AZ, Leuthardt EC. Mapping language function with task-based vs. resting-state functional MRI. PLoS One. 2020 Jul 31;15(7):e0236423. doi: 10.1371/journal.pone.0236423. PMID: 32735611; PMCID: PMC7394427.
- Roland et al. (2019): Roland JL, Hacker CD, Snyder AZ, Shimony JS, Zempel JM, Limbrick DD, Smyth MD, Leuthardt EC. A comparison of resting state functional
{7}
magnetic resonance imaging to invasive electrocortical stimulation for sensorimotor mapping in pediatric patients. Neuroimage Clin. 2019;23:101850. doi: 10.1016/j.nicl.2019.101850. Epub 2019 May 4. PMID: 31077983; PMCID: PMC6514367.
Sora's software validation studies were performed retrospectively using patient MRI datasets previously collected in a well-defined and clinically meaningful patient care context in which safety, effectiveness, and equivalence could be established, namely, with brain tumor and epilepsy adult, adolescent, and child patients (ages 3 to 71 years).
- SMN and LAN Map Validation: An analysis was conducted comparing Cirrus sensorimotor network (SMN) and language network (LAN) maps to corresponding resting state network maps evaluated in the published literature, finding the Cirrus SMN and LAN maps to be consistent with those used in Dierker et al (2017), Mitchell et al. (2013), Park et al. (2020), and Roland et al. (2019), as cited above.
- Please see the relevant literature for patient demographics and assessment of resting state network maps compared to standard of care task-based fMRI and intraoperative stimulation maps.
- All data were acquired on 3T scanners manufactured by Siemens.
- Cirrus SMN maps had a mean 0.826 spatial correlation with corresponding SMN maps evaluated in the published literature.
- Cirrus LAN maps had a mean 0.793 spatial correlation with corresponding LAN maps evaluated in the published literature.
- VIS Map Validation: Cirrus VIS maps were compared to a reference of same-patient task-activated vision maps using a Receiver Operating Characteristic (ROC) analysis.
- 26 subjects included brain tumor and epilepsy adult and pediatric patients.
- All data were acquired on 3T scanners manufactured by Siemens.
- Cirrus vision maps had a mean area under the ROC curve of 0.84, demonstrating comparability to task-activated vision maps.
These software validation studies demonstrate the comparability of Cirrus-generated RSN maps to task-activated maps, both analytically and from an expert clinician's perspective.
Validation for GE MRI Input: Cirrus SMN, LAN and VIS maps based on data captured at 5 sites with Siemens MR devices were compared with data captured at 3 sites with GE MR devices using a permutation analysis.
- 8 healthy, normal subjects each imaged at 8 geographically diverse sites.
- All data were acquired on 3T scanners manufactured by Siemens or GE.
- Within-subject similarity across scanner types was shown to be greater than cross-subject similarity, with a greater than 99.9% confidence level for each resting state network.
## Conclusions
The Cirrus Resting State fMRI Software (Cirrus) raises no new issues of safety or effectiveness as compared to its predicate, the resting state fMRI analysis component of the Quicktome Software Suite (K222359). Cirrus has the same intended uses / indications for use and the same or similar technological characteristics and principles of operation as its predicate
{8}
device. Technological differences between Cirrus and its predicate device raise no new issues of safety or effectiveness. Clinical performance validation data demonstrate Cirrus is as safe and effective as its predicate. Accordingly, Cirrus is substantially equivalent to its predicate.
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:
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 Tutorial 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-only devices, 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-only devices), 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.