K192004 · Eko Devices, Inc. · MWI · Jan 15, 2020 · Cardiovascular
Device Facts
Record ID
K192004
Device Name
Eko Analysis Software
Applicant
Eko Devices, Inc.
Product Code
MWI · Cardiovascular
Decision Date
Jan 15, 2020
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K192004 · Jan 15, 2020
Eko Analysis Software
Eko Devices, Inc.
Proprietary clinical datasets (Eko CORE and Eko DUO recordings); Publicly available clinical databases (MIT-BIH Arrhythmia, MIT-BIH Noise Stress, AHA, NST, PhysioNet QT, PhysioNet 2016)
Retrospective analysis of clinical recordings was used to validate the performance (sensitivity, specificity, and accuracy) of the software's rhythm detection, murmur detection, heart rate, QRS duration, and EMAT calculation algorithms.
Absolute Mean Error 9.25 ms (95% CI: 7.93 - 10.58)
PhysioNet QT database
—
—
—
Electromechanical Activation Time (EMAT) Calculation
Signal processing algorithm
—
Absolute Error 1.68% (95% CI: 1.06 - 2.30)
Physionet 2016 database and Eko ECG dataset
—
—
—
Indications for Use
The Eko Analysis Software is intended to provide support to the physician in the evaluation of patients' heart sounds and ECG's. The software analyzes simultaneous ECG and heart sounds. The software will detect the presence of suspected murmurs in the heart sounds. The software also detects the presence of atrial fibrillation and normal sinus rhythm from the ECG signal. In addition, it calculates certain cardiac time intervals such as heart rate. QRS duration and EMAT. The software does not distinguish between different kinds of murmurs and does not identify other arrhythmias. It is not intended as a sole means of diagnosis. The interpretations of heart sounds and ECG offered by the software are only significant when used in conjunction with physician over-read and is for use on adults (> 18 years).
Device Story
Cloud-based software API; processes synchronized ECG and heart sound (PCG) data acquired via Eko DUO or Eko CORE devices. Uses signal processing and neural networks to analyze inputs; outputs include murmur detection, rhythm classification (AFib/Normal Sinus Rhythm), and cardiac interval measurements (heart rate, QRS duration, EMAT). Used by physicians in clinical settings; results displayed via companion mobile apps. Assists clinicians in cardiac evaluation; provides decision support; not for sole diagnosis. Benefits include automated screening support for cardiac abnormalities.
Clinical Evidence
Retrospective validation using public (MIT-BIH, AHA, NST, PhysioNet) and proprietary datasets (732 recordings from 139 patients via Eko DUO; 1445 recordings from 236 patients via Eko CORE). Rhythm detection: 100% sensitivity, 96.2% specificity. Murmur detection: 87.6% sensitivity, 87.8% specificity. Heart rate error: 1.14%. Bradycardia/Tachycardia detection: 94.7%/93.6% sensitivity, 99.7%/99.0% specificity. QRS duration: 9.25ms absolute mean error. EMAT: 1.68% absolute error.
Technological Characteristics
Cloud-based software API. Standards: IEC 60601-1, IEC 60601-1-2, IEC 60601-2-47, IEC 60601-2-25, ANSI/AAMI EC57. Inputs: ECG and heart sounds. Processing: Signal processing and neural network models. Connectivity: API-based data transfer from mobile/computer applications.
Indications for Use
Indicated for adult patients (> 18 years) to support physicians in evaluating heart sounds and ECGs. Detects suspected murmurs, atrial fibrillation, and normal sinus rhythm; calculates heart rate, QRS duration, and EMAT. Not for sole diagnosis; requires physician over-read.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left, there is a symbol representing the Department of Health & Human Services - USA. To the right of this symbol, there is a blue square with the letters "FDA" in white. Next to the blue square, the words "U.S. FOOD & DRUG ADMINISTRATION" are written in blue.
January 15, 2020
Eko Devices Inc % Yarmela Pavlovic Partner Manatt, Phelps & Phillips, LLP One Embarcadero Center, 30th Floor San Francisco, California 94111
Re: K192004
Trade/Device Name: Eko Analysis Software Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MWI, DOD, DPS Dated: December 18, 2019 Received: December 18, 2019
Dear Yarmela Pavlovic:
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 (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 located 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.
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
{1}------------------------------------------------
Page 2
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 803) for devices or postmarketing safety reporting (21 CFR 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 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 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 medical devices and radiation-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).
Sincerely,
Stephen Browning Assistant Director Division of Cardiac Electrophysiology, Diagnostics and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
510(k) Number (if known) K192004
Device Name
Eko Analysis Software (EAS) Indications for Use (Describe)
The Eko Analysis Software is intended to provide support to the evaluation of patients ' heart sounds and ECG's. The software analyzes simultaneous ECG and heart sounds. The software will detect the presence of suspected murmurs in the heart sounds. The software also detects the presence of atrial fibrillation and normal sinus rhythm from the ECG signal. In addition, it calculates certain cardiac time intervals such as heart rate, QRS duration and EMAT. The software does not distinguish between different kinds of murmurs and does not identify other arrhythmias.
It is not intended as a sole means of diagnosis. The interpretations of heart sounds and ECG offered by the software are only significant when used in conjunction with physician over-read and is for use on adults (> 18 years).
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.qov
"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."
{3}------------------------------------------------
### 510(k) SUMMARY
### Eko Devices, Inc.'s Eko Analysis Software
### Submitter
Eko Devices Inc. 2600 10th Street, Suite #260, Berkeley, CA - 94710
Contact Person: Subramaniam Venkatraman, CTO Phone: 844-356-3384 Email: contact@ekohealth.com
Date Prepared: January 8, 2020
Name of Device: Eko Analysis Software (EAS) Common or Usual Name: CardiacAl
Classification Name: Cardiac monitor Regulatory Class: Class II Product Code: MWI, DQD, DPS
### Predicate Devices
Dictum Health Inc., IDM100 (K170798) Diacoustic Medical Devices (Pty) Ltd, SensiCardiac Mobi (K131044) Inovise Medical. AUDICOR 200 (K073545) physIQ Inc, physIQ Heart Rhythm Module (K180234)
### Device Description
The Eko Analysis Software is a cloud-based software API that allows a user to upload synchronized ECG and heart sound/phonocardiogram (PCG) data for analysis. The software uses several methods to interpret the acquired signals including signal processing and artificial neural networks. The API can be electronically interfaced, and perform analysis with data transferred from multiple mobile or computer based applications.
The EAS software is only intended to be used in conjunction with data acquired using two previously-cleared physiological data acquisition devices (Eko DUO (K170874) and Eko CORE (K151319)). The software is designed to be used with companion mobile apps that are used during data acquisition. After analysis, results are returned through an interface to the mobile apps for display.
The algorithm consists of the following components:
- Rhythm detection algorithm: A neural network model that uses ECG to detect normal sinus rhythm and atrial fibrillation.
- Murmur detection algorithm: A neural network model that uses heart sounds to detect the ● presence of murmurs.
- Heart rate analysis algorithm: A signal processing algorithm that uses ECG or heart ● sounds as appropriate to calculate heart rate. It also provides an alert if the measured heart rate is indicative of Bradycardia or Tachycardia.
{4}------------------------------------------------
- QRS duration algorithm: A signal processing algorithm that measures the width of the ● QRS pulse on a single-channel ECG.
- EMAT Interval algorithm: A signal processing algorithm that uses Q peak detection and ● S1 envelope detection to measure the Q-S1 interval, defined as electromechanical activation time or EMAT.
### Intended Use / Indications for Use
The Eko Analysis Software is intended to provide support to the physician in the evaluation of patients' heart sounds and ECG's. The software analyzes simultaneous ECG and heart sounds. The software will detect the presence of suspected murmurs in the heart sounds. The software also detects the presence of atrial fibrillation and normal sinus rhythm from the ECG signal. In addition, it calculates certain cardiac time intervals such as heart rate. QRS duration and EMAT. The software does not distinguish between different kinds of murmurs and does not identify other arrhythmias.
It is not intended as a sole means of diagnosis. The interpretations of heart sounds and ECG offered by the software are only significant when used in conjunction with physician over-read and is for use on adults (> 18 years).
### Summary of Technological Characteristics
EAS combines the features of multiple predicate devices into a single combined software package. The intended use of the subject product (i.e., analysis of physiological data) is the same as that of all of the predicate devices and the indications for use and technological characteristics are either identical or very similar between the subject device and each relevant predicate. Any differences in specific analyzed parameters (indications for use) do not raise different questions of safety or effectiveness in comparison to the predicates. While some of the predicate devices feature additional technological capabilities (e.g., the SensiCardiac predicate additional features differentiation between pathologic and innocent murmur, while the subject device and predicate both differentiate between the presence of murmur and no murmur), this does not raise different questions of safety or effectiveness because in all cases the subject device features are a subset of those cleared for the predicates.
A table comparing the key features of the subject and predicate devices is provided below.
{5}------------------------------------------------
K192004
Page 3 of 5
| | Eko Analysis<br>Software | IDM100 | Sensi Cardiac Mobi<br>Diagnostic Heart<br>Murmur<br>Application | AUDICOR 200 | physIQ Heart Rhythm<br>Module (version 1.0) |
|--------------------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------|----------------------------------------------------------|
| 510K<br>Number | K182119 | K170798 | K131044 | K073545 | K180234 |
| Patient<br>Population | Adult patients | Neonate (up to 28<br>days); pediatric (29<br>days to 12 years,<br>excepted as<br>noted); adolescent<br>(13-17 years); adult<br>(18 years and<br>older) | Adult and pediatric<br>patients | Patients over 18 years<br>of age | Adult patients |
| Intended<br>User | Physicians | Physicians and<br>patients | Physicians | Physician | Physician or other<br>qualified medical<br>professionals |
| Standards<br>Met | IEC 60601-1<br>IEC 60601-1-2<br>IEC 60601-2-47<br>IED 60601-2-25<br>ANSI/AAMI EC57 | ANSI/AAMI EC53<br>EN/IEC 60601-2-25<br>EN/IEC 60601-2-51 | IEC 60601-1<br>IEC 60601-1-2 | EN 60601-1<br>EN60601-1-2<br>IEC 60601-2-25<br>IEC 60601-2-51 | ANSI/AAMI EC57 |
| Device<br>Classificati<br>on | MWI, DQD, DPS | MWI | DQD, DQC | DPS, DQD, MLO | DPS |
| Prescribed | Prescription Only | Prescription Only | Prescription Only | Prescription Only | Prescription Only |
| Componen<br>ts | Software Only | Software +<br>Hardware | Software Only | Software + Hardware | Software Only |
| Interface | Application<br>programming<br>interface (API) | | | | Callable application<br>programming interface<br>(API) |
| Display | No primary display | Yes | No primary display | Yes on Audicor-<br>enabled laptop | No primary display |
| Physiologi<br>cal Inputs | Heart sounds and<br>ECG data | Heart sounds, ECG<br>data, SpO2, NIBP | Heart sounds | Heart sounds and ECG<br>data | Heart sounds and ECG<br>data |
| Murmur<br>Detection | Yes (classification) | No | Yes (classification) | No | No |
| A-fib<br>detection | Yes (classification) | No, ECG<br>acquisition only. | No | No | Yes (classification) |
| EMAT<br>Calculation | Yes | No | No | Yes | No |
| Heart Rate<br>Calculation | Yes | Yes | Yes | Yes | Yes |
| QRS<br>duration<br>Calculation | Yes | No | No | Yes | Yes |
{6}------------------------------------------------
# Performance Data - Nonclinical Testing
The Eko Analysis Software was the subject of software verification and validation testing, consistent with the principles outlined in FDA's General Principles of Software Validation; Final Guidance for Industry and FDA Staff.
# Performance Data - Clinical Testing
The algorithms in this submission have been validated using retrospective analysis on a combination of publicly available (MIT-BIH Arrhythmia Database, MIT-BIH Arrhythmia Noise Stress Database, AHA Database, NST Database, Physionet QT Database, and PhysioNet 2016 Database) and proprietary datasets captured with the Eko CORE and Eko DUO. In the proprietary datasets, the Eko CORE and Eko DUO were used to capture 15 second long heart sound and ECG recordings from chests of individual volunteers. A total of 732 recording were captured from 139 patients using the Eko DUO and 1445 recordings were captured from 236 patients using the Eko CORE. In the Eko DUO dataset 54.7% of patients were female and all patients were over the age of 18, with the largest percentage being 61 to 80 years of age. Additionally, 79.9% were white, while 9.4% were Asian and the remainder were Black or African American, American Indian or Alaskan Native, Native Hawaiian or Pacific Islander or Hispanic/Latino. In the Eko CORE dataset, 47.9% of patients were female. Additionally, 83.9% were white, 7.6% were black or African American and the remainder were Asian (4.2%), Hispanic or Latino (2.1%) or other/unknown. Patients were all over the age of 18 with the largest percentage being 51 to 80 years of age.
A brief description of the testing provided for each individual analysis algorithm is provided below along with performance results from the most relevant datasets:
# Rhythm Detection
Testing was carried out on publicly available databases as well as the EKO ECG dataset. When the device was tested with the EKO ECG dataset, 74.3% (544/732) of ECG recordings were classified as either Normal or Atrial Fibrillation. Sensitivity and specificity measured in the classifiable ECGs were 100% (95% Cl: 93.8 - 100.0) and 96.2% (95% Cl: 93.8 -97.7), respectively.
# Murmur Detection
Testing was carried out on the Eko Heart Sound Database comprised of data collected using both the Eko CORE and Eko DUO devices. Sensitivity and specificity in the Eko Heart Sound Database were 87.6% (95% C1: 84.2 – 90.5) and 87.8% (95% C1: 85.3 – 89.9), respectively.
# Heart Rate Calculation
Testing was carried out on publicly available datasets as well as the EKO ECG dataset (described above). Bradycardia and Tachycardia detection accuracy was also measured in the publicly available datasets. Heart rate error measured in the MIT-BIH dataset was 1.14% (95% Cl: 0.95 - 1.34). Bradycardia detection had a sensitivity and specificity of 94.7% (95%
{7}------------------------------------------------
Cl: 89.8 - 97.3) and 99.7% (95% Cl: 99.4 - 99.8) respectively. Tachycardia detection had a sensitivity and specificity of 93.6% (95% C1: 90.9 - 95.6) and 99.0% (95% C1: 98.7 - 99.3) respectively.
### QRS Duration Calculation
Testing was carried out using the publicly available PhysioNet QT database. Absolute Mean Error (ms) for calculating QRS duration was 9.25 (95% Cl: 7.93 - 10.58).
### EMAT Calculation
Testing was carried out on publicly available Physionet 2016 database, as well as the Eko ECG dataset. Absolute Error in the Physionet 2016 dataset was 1.68% (95% Cl: 1.06 -2.30).
Given the data described above, the algorithms performed as expected. Based on the clinical performance the Eko Analysis Software has a safety and effectiveness profile that is similar to the predicate devices.
### Conclusions
The Eko Analysis Software is as safe and effective as the predicate devices. The Eko Analysis Software has the same intended uses and similar indications, technological characteristics, and principles of operation as its predicate device. The minor differences in indications do not alter the intended diagnostic use of the device and do not raise different questions of safety and effectiveness when used as labeled. In addition, the minor technological differences between the Eko Analysis Software and its predicate devices raise no new issues of safety or effectiveness. Performance data demonstrate that the Eko Analysis Software is as safe and effective as the predicate devices. Thus, the Eko Analysis Software is substantially equivalent.
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.