Software as a Medical Device, Real-World Evidence, Pediatric
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K241513 · Sep 27, 2024
Sourcerer
Brain Electrophysiology Laboratory Company, LLC
Retrospective clinical data from epileptic patients; Standard presurgical evaluation records; hdEEG recordings; MRI-defined resected regions; Clinical outcome data
Retrospective clinical data from patients undergoing standard presurgical evaluation for epilepsy was used to compare the performance of the Sourcerer device against the predicate device (GeoSource). The study used resected regions as a ground-truth reference to evaluate the accuracy of Electrical Source Imaging (ESI).
Epileptic patients undergoing standard presurgical evaluation
GeoSource (K092844)
Euclidian distance between the location of maximal amplitude (ESI) and the nearest voxel of the resected boundary
Indications for Use
The software is intended for use by a trained/qualified EEG technologist or physician on both adult and pediatric subjects at least 16 years of age for the visualization of human brain function by fusing a variety of EEG information with rendered images of an idealized head model and an idealized MRI image.
Device Story
Sourcerer is EEG source localization software; uses high-density EEG (hdEEG) and idealized MRI-derived head models to estimate/visualize cortex projections of brain activity. Operates in client-server model; server (FLOW) integrates EEG/MRI data; Electro-magnetic Inverse Module (EMIM API) computes inverse source projections; client (Chrome browser) uses Electro-magnetic Functional Anatomy Viewer (EMFAV) for interactive visualization (scalp, cortical, dipoles, flat map, butterfly plot). Used by trained EEG technologists or physicians in clinical settings. Output assists clinicians in visualizing brain function; supports presurgical evaluation by comparing Electrical Source Imaging (ESI) results against resected regions in epileptic patients. Benefits include non-invasive visualization of brain activity to aid clinical decision-making.
Clinical Evidence
Clinical evaluation used retrospective data from epileptic patients undergoing presurgical evaluation. Sample included hdEEG (256 channels), MRI-defined resected regions, and clinical outcomes. ESI was performed on inter-ictal spikes; performance measured by Euclidean distance between maximal amplitude location and resected boundary. Sourcerer showed equivalent performance to GeoSource.
Technological Characteristics
Software-only device. Uses Finite Element Method (FEM) for forward head modeling. Tissue conductivities (S/m): air 0.0, CSF 1.6, eyes 1.55, skull 0.006, scalp 0.3, gray matter 0.45, white matter 0.2. Inverse methods: LORETA, sLORETA, MSP. Client-server architecture; web-based UI (Chrome). Safety classification: Class B per AAMI/ANSI/IEC 62304.
Indications for Use
Indicated for adult and pediatric patients (≥16 years) undergoing EEG-based visualization of brain function via fusion of EEG data with idealized head/MRI models.
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}------------------------------------------------
September 27, 2024
Image /page/0/Picture/1 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health and Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
Brain Electrophysiology Laboratory Company, LLC Phan Luu Chief Scientist 1776 Millrace Drive Suite 304 Eugene, Oregon 97403
Re: K241513
Trade/Device Name: Sourcerer Regulation Number: 21 CFR 882.1400 Regulation Name: Electroencephalograph Regulatory Class: Class II Product Code: OLX Dated: August 28, 2024 Received: August 28, 2024
Dear Dr. Luu:
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"
{1}------------------------------------------------
(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 OS 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 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-reportingcombination-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 Rue"). 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-advicecomprehensive-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-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/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-device-advice-comprehensive-regulatoryassistance/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}------------------------------------------------
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}------------------------------------------------
# Indications for Use
510(k) Number (if known) K241513
Device Name Sourcerer
Indications for Use (Describe)
The software is intended for use by a trained/qualified EEG technologist or physician on both adult and pediatric subjects at least 16 years of age for the visualization of human brain function by fusing a variety of EEG information with rendered images of an idealized head model and an idealized MRI image.
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
| 1. SUBMITTER | |
|----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Submitter Name:<br>Address:<br>Phone Number:<br>Contact Person:<br>Date Prepared: | Brain Electrophysiology Laboratory Company, LLC<br>1776 Millrace Drive, Eugene, OR 97403<br>541-653-9797<br>Dr. Phan Luu<br>June 10 2024 |
| 2. DEVICE | |
| Device Trade Name:<br>Common Name:<br>Classification Name,<br>Number &<br>Product Code:<br>Class:<br>Classification Panel: | Sourcerer<br>Electroencephalograph Software<br>Electroencephalograph<br>21 CFR 882.1400<br>OLX<br>II<br>Neurology |
| 3. PREDICATE DEVICES | |
| Primary Predicate Device:<br>Intended use: | K092844<br>GeoSource is intended for use by a<br>trained/qualified EEG technologist or physician on<br>both adult and pediatric subjects at least 3 years of<br>age for the visualization of human brain function by<br>fusing a variety of EEG information with rendered<br>images of an idealized head model and an<br>idealized MRI image. |
## 4. DEVICE DESCRIPTION
Sourcerer is an EEG source localization software that uses EEG and MRI-derived information to estimate and visualize cortex projections of human brain activity. Sourcerer is designed in a client-server model wherein the server components integrate directly with FLOW - BEL's software. Inverse source projections are computed on the server using EEG and MRI data from FLOW using the Electro-magnetic Inverse Module (EMIM API). The inverse results are interactively visualized in the Chrome browser running on the client computer using the Electro-magnetic Functional Anatomy Viewer (EMFAV). A functional overview and high-level communication pattern are shown in Figure 1. EMFAV is hosted on
{5}------------------------------------------------
FLOW's web server, from which the client computer can make requests when opening an MFF file using Sourcerer.
Image /page/5/Figure/3 description: The image shows a diagram of a system with three main components: EMFAV, FLOW, and EMIM API. EMFAV, located on the Client Computer, handles display methods such as Scalp, Cortical, Dipoles, Flat Map, and Butterfly Plot. FLOW, situated on the Server, manages User Authentication, MFF Files, Experiments, and Atlas Head Models, while EMIM API, also on the Server, provides Inverse Algorithms like sLORETA, LORETA, MSP, and Spectral, illustrating the data flow and interactions between these components.
Figure 1. Architecture Overview of Sourcerer. Sourcerer is divided into three software components shown in green: EMFAV, EMIM API, and Atlas Head Models.
## 5. INDICATIONS FOR USE
The software is intended for use by a trained/qualified EEG technologist or physician on both adult and pediatric subjects at least 16 years of age for the visualization of human brain function by fusing a variety of EEG information with rendered images of an idealized head model and an idealized MRI image.
## 6. COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH PREDICATE DEVICE
| | New Device | Primary Predicate Device |
|----------------------------------|---------------------------------------------------|--------------------------|
| Device name | Sourcerer | GeoSource |
| 510(k) number | | K092844 |
| Manufacturer | Brain Electrophysiology<br>Laboratory Company LLC | EGI |
| Regulation | 882.1400 | 882.1400 |
| Product Code | OLX | OLX |
| Device<br>Classification<br>Name | Class II | Class II |
| Software only<br>product | Yes | Yes |
{6}------------------------------------------------
| Computer OS | MS-windows 7, Mac OS, Linux. Is<br>cloud based and relies on web<br>browser for user interface. | Mac OS |
|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| MRI visualization | Idealized MRI (average) | Idealized MRI (average) |
| Source estimation<br>methods: | | sLORETA,LORETA,LAURA |
| Linear inverse<br>methods | | |
| Forward head<br>modeling | Finite Element Method<br>(FEM).<br>Tissues and respective<br>conductivities (S/m)<br>include:<br>air = 0.0<br>CSF = 1.6<br>eyes = 1.55<br>skull = 0.006<br>scalp = 0.3,<br>gray matter = 0.45<br>white matter = 0.2 | Sphere, Finite Difference<br>Model (FDM). Tissues<br>and respective<br>conductivities (S/m)<br>include:<br>air = 0.0<br>CSF = 1.79<br>eyes = 1.55<br>skull = 0.01<br>scalp = 0.33<br>gray matter = 0.25<br>white matter = 0.35 |
Table 1: Comparison of the new device to the predicate device
| Summary of<br>Technological<br>Characteristics | Inputs: Sourcerer takes as inputs hdEEG data.<br>Electrical Head Models: Sourcerer uses idealized (i.e., atlas) head<br>models to describe current flow from cortex to scalp, where the EEG<br>is recorded.<br>Conductivity values: Sourcerer use different conductivity values for<br>each of the different head tissues.<br>Forward model: Sourcerer uses the Finite Element Method (FEM) to<br>derive forward model.<br>Inverse Methods: Sourcerer uses the LORETA, sLORETA and Multiple<br>Sparse Priors (MSP) inverse methods.<br>Display: Sourcerer displays the results on idealized head models |
|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Substantial<br>Equivalence<br>Comparison | The identified equivalent device is GeoSource K092844. GeoSource is<br>equivalent and different to Sourcerer in the following ways:<br>● Like GeoSource, Sourcerer takes as inputs hdEEG data.<br>● Electrical Head Models: Like Sourcerer, GeoSource uses<br>idealized (i.e., atlas) head models to describe current flow<br>from cortex to scalp, where the EEG is recorded. Atlas head<br>models for both Sourcerer and Geosource characterize the |
{7}------------------------------------------------
same brain tissues: scalp, skull, eyeballs, air, cerebral spinal fluid, gray matter and white matter.
- Sourcerer and GeoSource use different conductivity values for each of the different head tissues (detailed below).
- Another difference between Sourcerer and GeoSource atlas head models is the way in which the forward model (i.e., how current flow is modeled) is computed. Sourcerer uses the Finite Element Method (FEM) whereas GeoSource uses the Finite Difference Method (FDM) and spherical model (which is not relevant for the present evaluation).
- Inverse Methods: Like Sourcerer, GeoSource uses the LORETA and sLORETA inverse methods. However, Sourcerer includes an additional inverse method (Multiple Sparse Priors—MSP) not supported by GeoSource.
- Display: Like Sourcerer, GeoSource displays the results on idealized head models.
## 7. PERFORMANCE DATA
Algorithmic testing of HexaFEM and Inverse methods
#### HexaFEM
HexaFEM is the computational modeling method used to compute current flow from a position on the cortex through the various head tissues in the Sourcerer device.
Comparison of a three-layer sphere between HexaFEM and Spherical Analytics showed that the HexaFEM solutions are consistent with the analytical solutions for the three-layer spherical model.
#### HexaFEM and FDM Results
Similar to the three-layer sphere analytics, we compared the HexaFEM and FDM solutions for one realistic head model using the same conductivity values. Results showed that the HexaFEM and the FDM solutions are the same.
#### Inverse Model (EMIM Module)
The inverse solvers were tested using test files with known signal sources. The known signals are from the forward projection, using an atlas head model, of current from each dipole to the scalp. The scalp data from the forward projections signals, with no noise added per standard procedure from scientific literature, were then used to recover the source generator (known) with the various inverse solvers.
{8}------------------------------------------------
| | Results are quantified as localization error distance (i.e., distance of the source estimate from the original source generating the scalp signal). |
|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | LORETA: The average localization error is about 7 mm. The localization error distance is similar to what is reported for LORETA from the creator of LORETA. |
| | sLORETA Source estimation results are exact for the simulated signal sources. This fully replicates the simulated results reported by the creator of sLORETA. |
| | MSP The results show 100% (zero localization error), as expected. |
| Clinical<br>Performance<br>Testing | The clinical data used in the evaluation is obtained from epileptic patients during standard presurgical evaluation. The data from the clinical assessment used in the current clinical evaluation are hdEEG (256 channels) data, resected region (from MRI) and clinical outcome. The hdEEG data allow for Electrical Source Imaging (ESI) to be performed, the resected region provides an anatomic location to compare the ESI results, and the clinical outcome provides assurance that the resected location can be trusted as a ground-truth location.<br>ESI was performed on an average inter-ictal spike derived from each patient's pre-operative hdEEG recording in both Sourcerer and Geosource. For each patient, the Euclidian distance between the location of maximal amplitude and the nearest voxel of the resected boundary was calculated for both devices.<br>Performance of Sourcerer was shown to be equivalent to GeoSource. |
| Software<br>Verification and<br>Validation Testing | Validation testing involved algorithm testing which validated the accuracy of Sourcerer. The product was deemed fit for clinical use. Sourcerer was designed and developed as recommended by FDA's Guidance, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Device". According to AAMI/ANSI/IEC 62304 Standard, Sourcerer safety classification has been set to Class B. "Basic Documentation Level" applied to this device. |
## 8. CONCLUSION
The information discussed above and provided in the 510(k) submission demonstrate that the Sourcerer 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.