Overall agreement (OA) metrics computed with bootstrapped median-point estimates and 95% confidence intervals
—
—
Performance evaluation against EnsoSleep (K162627) using two data sets (BEL and CSF)
—
Indications for Use
Automatically scoring of sleep EEG data to identify stages of sleep according the American Academy of Sleep Medicine definitions, rules and guidelines. It is to be used with adult populations.
Device Story
NEAT (Neurosom EEG Assessment Technology) is a client-server software application for post-acquisition sleep staging. Input: unscored MFF files containing EEG data. Operation: user initiates workflow via web-based UI; containerized neat-cli software on a FLOW server processes EEG data using machine learning to identify sleep stages; output: event track file (XML) added to MFF, hypnogram visualization, sleep statistics, and PDF summary. Used in physician offices or home settings; operated by clinicians. Output assists clinicians in sleep study interpretation. Benefits: provides automated, standardized sleep staging consistent with AASM guidelines, reducing manual scoring burden.
Clinical Evidence
Performance evaluation compared NEAT against EnsoSleep using two datasets. Metrics included sensitivity (positive agreement), specificity (negative agreement), and overall agreement (OA) calculated on a segment-by-segment basis (30-second epochs). Bootstrapped (R=2000) median-point estimates and 95% CIs were computed. Results showed NEAT and EnsoSleep performance differences were generally within the range of human inter-rater agreement. NEAT showed higher accuracy for Wake, N1, and N3 stages, while EnsoSleep performed better for REM and N2. NEAT demonstrated superior sensitivity for N3 classification compared to EnsoSleep.
Technological Characteristics
Software-only medical device; client-server architecture (Chrome browser UI, FLOW server CLI). Uses machine learning for sleep staging. Operates on forehead EEG signals. Connectivity: RESTful API over HTTP. Data storage: MongoDB. Safety classification: Class B per AAMI/ANSI/IEC 62304.
Indications for Use
Indicated for automatic scoring of sleep EEG data to identify sleep stages (Wake, REM, N1, N2, N3) in adult populations according to AASM guidelines.
Regulatory Classification
Identification
An electroencephalograph is a device used to measure and record the electrical activity of the patient's brain obtained by placing two or more electrodes on the head.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
April 10, 2025
Brain Electrophysiology Laboratory Company, LLC
Roman Shusterman
Chief Technology Officer
440 E Broadway, Suite 200
Eugene, Oregon 97401
Re: K250058
Trade/Device Name: NEAT 001
Regulation Number: 21 CFR 882.1400
Regulation Name: Electroencephalograph
Regulatory Class: Class II
Product Code: OLZ
Dated: January 10, 2025
Received: January 10, 2025
Dear Roman Shusterman:
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.
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"
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K250058 - Roman Shusterman
Page 2
(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-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).
{2}
K250058 - Roman Shusterman
Page 3
Sincerely,
Jay R. Gupta -S
Jay Gupta
Assistant Director
DHT5A: Division of Neurosurgical, Neurointerventional, and Neurodiagnostic Devices
OHT5: Office of Neurological and Physical Medicine Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
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.
Submission Number (if known)
Device Name
NEAT 001
Indications for Use (Describe)
Automatic scoring of sleep EEG data to identify stages of sleep according the American Academy of Sleep Medicine definitions, rules and guidelines. It is to be used with adult populations.
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}
K250058
510(K) Summary
| 1. SUBMITTER | |
| --- | --- |
| Submitter Name:
Address:
Phone Number:
Contact Person:
Date Prepared: | Brain Electrophysiology Laboratory Company, LLC
440 E Broadway, Eugene, OR 97401
541-653-9797
Dr. Phan Luu
April 07 2025 |
| 2. DEVICE | |
| Device Trade Name:
Common Name:
Classification Name,
Number &
Product Code:
Class:
Classification Panel: | NEAT 001
Automatic Event Detection Software For
Polysomnograph With Electroencephalograph
Electroencephalograph
21 CFR 882.1400
OLZ
II
Neurology |
| 3. PREDICATE DEVICES | |
| Primary Predicate Device:
Intended use: | K162627
EnsoSleep is intended for use for the diagnostic
evaluation by a physician to assess sleep quality
and as an aid for the diagnosis of sleep and
respiratory related sleep disorders in adults only.
EnsoSleep is a software-only medical device to be
used under the supervision of a clinician to analyze
physiological signals and automatically score
sleep study results, including the staging of sleep,
detection of arousals, leg movements, and sleep
disordered breathing events including obstructive
apneas. All automatically scored events are
subject to verification by a qualified clinician.
Central apneas, mixed apneas, and hypopneas
must be manually marked within records. |
| The primary predicate device has not been subject to a design-related recall. | |
{5}
Page 2
K250058
# 4. DEVICE DESCRIPTION
The Neurosom EEG Assessment Technology (NEAT) is a medical device software application that allows users to perform sleep staging post-EEG acquisition. NEAT allows users to review sleep stages on scored MFF files and perform sleep scoring on unscored MFF files.
NEAT software is designed in a client-server model and comprises a User Interface (UI) that runs on a Chrome web browser in the client computer and a Command Line Interface (CLI) software that runs on a Forward-Looking Operations Workflow (FLOW) server.
The user interacts with the NEAT UI through the FLOW front-end application to initiate the NEAT workflow on unscored MFF files and visualize sleep-scoring results. Sleep stages are scored by the containerized neat-cli software on the FLOW server using the EEG data. The sleep stages are then added to the input MFF file as an event track file in XML format. Once the new event track file is created, the NEAT UI component retrieves the sleep events from the FLOW server and displays a hypnogram (visual representation of sleep stages over time) on the screen, along with sleep statistics and other subject details. Additionally, a summary of the sleep scoring is automatically generated and added to the same participant in the FLOW server in PDF format.

Figure 1. Architecture Overview of NEAT for post-acquisition mode.
Modules description
# NEAT UI:
The graphical user interface for the NEAT workflow is accessible through the FLOW front-end application, which is served by FLOW's web server. NEAT UI communicates with the FLOW server through a RESTful API to run the NEAT workflow and retrieve sleep staging results.
{6}
Page 3
K250058
**RESTful API:**
The FLOW API runs on the FLOW server and is the primary back end for the application. It is a RESTful API and communicates over HTTP.
**neat-cli:**
The neat-cli software runs on the FLOW server as an executable Docker container and leverages Python libraries for identifying stages of sleep on MFF files using Machine Learning (ML). The neat-cli container interacts with the FLOW API to start the NEAT workflow and store sleep staging results on the database.
**FLOW Database:**
All data that the NEAT workflow uses to perform ML sleep staging is stored in a Mongo DB database on the FLOW server.
**5. INDICATIONS FOR USE**
Automatically scoring of sleep EEG data to identify stages of sleep according to the American Academy of Sleep Medicine definitions, rules and guidelines. It is to be used with adult populations.
**6. COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH PREDICATE DEVICE**
| | New Device | Predicate Device |
| --- | --- | --- |
| Device Name | NEAT | EnsoSleep |
| 510(k) number | | K162627 |
| Manufacturer | BELCo, LLC | EnsoData, Inc. |
| Regulation name | Electroencephalograph | Electroencephalograph |
| Product code | OLZ | OLZ |
| Regulatory class | Class II | Class II |
{7}
K250058
| Regulation number | 21 CFR 882.1400 | 21 CFR 882.1400 |
| --- | --- | --- |
| Software only | Yes | Yes |
| Indication for use | Automatically scoring of sleep EEG data to identify stages of sleep according to the American Academy of Sleep Medicine definitions, rules and guidelines. It is to be used with adult populations. | EnsoSleep is intended for use for diagnostic evaluation by a physician to assess sleep quality and as an aid for the diagnosis of sleep and respiratory related sleep disorders in adults only. EnsoSleep is a software-only medical device to be used under the supervision of a clinician to analyze physiological signals and automatically score sleep study results, including the staging of sleep, detection of arousals, leg movements, and sleep disordered breathing events including obstructive apneas. All automatically scored events are subject to verification by a qualified clinician. Central apneas, mixed apneas, and hypopneas must be manually marked within records. |
| Environment for Use | Physician office or at home | |
| Derived Signals | Sleep stages: Rapid eye movement (REM), non-REM (N1, N2, N3) and wake | Sleep stages: Rapid eye movement (REM), non-REM (N1, N2, N3) and wake |
| Sleep Measures | • Sleep, REM and N3 onset • Total sleep and recording times • Sleep efficiency • % time by sleep stage | |
| Sleep staging | Based on one forehead EEG signals to differentiate Wake (W), REM (R), NREM stage 1 (N1), NREM stage 2 (N2) and slow wave sleep (N3, includes both stages 3 and 4) | Not known if classification of sleep stages can operate on forehead EEG. Automated method, however, can differentiate Wake (W), REM (R), NREM stage 1 (N1), NREM stage 2 (N2) and slow wave sleep (N3, includes both stages 3 and 4) |
Table 1: Comparison of the new device to the predicate device
{8}
Page 5
K250058
## 7. PERFORMANCE DATA
### Summary of Non-Clinical Testing
Validation testing involved algorithm testing, which validated NEAT's accuracy. The product was deemed fit for clinical use.
NEAT was designed and developed as recommended by the FDA's Guidance, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Device". According to the AAMI/ANSI/IEC 62304 Standard, NEAT safety classification has been set to Class B. "Basic Documentation Level" applied to this device.
### Summary of Clinical Testing
NEAT and EnsoSleep Performance Evaluation Method
EnsoSleep: All data files were scored by EnsoSleep and sleep scores for each 30 second epoch were returned in JSON format. EnsoData uses a software-as-a-service model, where a client uploads PSG data to a cloud server and annotation files are output on the cloud server for the client to download.
NEAT: All data files were scored by NEAT and sleep scores for each 30-second epoch were labeled with a sleep stage.
Once the files were scored, performance on a segment-by-segment basis was compared against the established gold standard. Evaluation was performed by computing sensitivity performance (positive agreement--PA), specificity (negative agreement--NA), and overall agreement (OA) metrics for each data set (i.e., for different EEG systems). For each metric, we compute the bootstrapped (R=2000 resamples) median-point estimates and 95% confidence intervals. The 95% confidence interval was defined as the threshold values cutting off the top and bottom 2.5% of values.
Sensitivity was calculated by dividing the number of true positives (e.g., number of segments that NEAT correctly classified as N3) by the number of real positive cases (e.g., total number of segments classified as N3). Specificity (negative agreement--NA) was calculated by dividing the number of true negatives (e.g., number of segments which NEAT classified as not N3) by the number of real negative cases (e.g., number of epochs not classified as N3). OA was defined as the sum of all positive epochs (i.e., number of epochs that was correctly classified as a particular sleep stage) and negative epochs (i.e., number of epochs correctly classified as not being part of a particular sleep stages) divided by the total number of epochs.
NEAT vs EnsoSleep Overall Performance Comparisons
{9}
K250058
Figure 2 shows confusion matrices for EnsoSleep (left) and NEAT (right) across the two data sets. NEAT was more accurate at classifying Wake, N1, and N3 sleep stages. On the other hand, EnsoSleep is better at classifying REM (R) and N2 sleep stages.

Figure 2. Confusion matrices for EnsoSleep (left) and NEAT (right) performance by sleep stage for across data sets. Median performance and $95\%$ confidence interval (CI) are shown. Wa=Wake, R=REM.

In general, although there were different accuracies for different sleep stages for NEAT versus ENSO Sleep, these were largely within the range of differences that would be expected among expert human raters. We conclude that there is substantial equivalence between NEAT and the predicate ENSO Sleep.
The more specific findings are:
1) NEAT and EnsoSleep performed in an equivalent manner for correctly classifying Wake state EEG (1-2% difference depending on data set). This difference was within the range of human agreement variability.
2) EnsoSleep performed better (3-4% difference depending on data set) classifying REM state EEG.
3) EnsoSleep was better than NEAT in overall performance (4-7%) and specificity (5-9%) for classifying N1 sleep. However, only in the BEL data set was this difference bigger than the difference observed for human agreement. Moreover, sensitivity was substantially worse than NEAT (8-20%).
4) EnsoSleep was marginally better (5%) at classifying N2 sleep only for the BEL data set when compared to human agreement variability. Results showed EnsoSleep is more sensitive (22%) but less specific (9-11%) than NEAT.
{10}
Page 7
K250058
5) EnsoSleep and NEAT were equivalent (1% difference) in overall performance for N3 classification, with EnsoSleep being better (1%) for the BEL data set and NEAT being better (1%) for the CSF data set. Sensitivity is substantially better for NEAT across the two data sets (15-39%) compared to EnsoSleep, whereas specificity was marginally better for EnsoSleep (3-4%).
6) EnsoSleep sensitivity for N3 sleep is greatly affected by the data set. This may raise concerns about generalizability.
## Implications of the Specific Differences Between ENSO Sleep and NEAT
NEAT and EnsoSleep are equivalent in functional features with regard to automated staging of sleep from EEG data. NEAT does not detect leg movements or sleep disordered breathing. With regards to equivalent functional features, although there were statistically significant differences in performance between the two devices, due to the very small confidence interval estimates from the large resampling number, the differences are best interpreted practically. To provide context for practicality, we compare the differences between NEAT and EnsoSleep with the range of human differences (i.e., agreement) and found that for the CSF dataset the only practical difference was for REM. Even in this case, the difference between the two devices is 3%.
In general, although there were different accuracies for different sleep stages for NEAT versus ENSO Sleep, these were largely within the range of differences that would be expected among expert human raters. We conclude that there is substantial equivalence between NEAT and the predicate ENSO Sleep.
## 8. CONCLUSION
The information discussed above and provided in the 510(k) submission demonstrate that the NEAT device is substantially equivalent to the 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.