K213794 · Eko Devices, Inc. · DQD · Jun 29, 2022 · Cardiovascular
Device Facts
Record ID
K213794
Device Name
Eko Murmur Analysis Software (EMAS)
Applicant
Eko Devices, Inc.
Product Code
DQD · Cardiovascular
Decision Date
Jun 29, 2022
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1875
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device, Real-World Evidence, Pediatric
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K213794 · Jun 29, 2022
Eko Murmur Analysis Software (EMAS)
Eko Devices, Inc.
Proprietary database of 2,380 heart sound recordings from 615 unique subjects; Eko CORE and Eko DUO digital stethoscope recordings
The retrospective database was used to validate the performance of the Murmur Detection & Classification and Heart Sound Timing algorithms by comparing software outputs against cardiologist annotations and gold-standard echocardiogram findings.
299 heart sound recordings annotated by expert cardiologists
>1 (cardiologists)
Indications for Use
The Eko Murmur Analysis Software (EMAS) is intended to provide decision support to clinicians in their evaluation of patients' heart sounds. The software analyzes heart sounds and phonocardiograms (and ECG signals, when available). The software will automatically detect murmurs that may be present, and the murmur timing and character, including S1, S2, innocent heart murmurs, structural heart murmurs, and the absence of a heart murmur. The Eko Murmur Analysis Software is not intended as a sole means of diagnosis and is for use in environments where health care is provided by clinicians. The interpretations of heart sounds offered by the software are meant only to provide decision support to the clinician, who may use the result in conjunction with their own evaluation and clinical judgment. The interpretations are not diagnoses. The Eko Murmur Analysis Software is intended for use on pediatic and adult patients.
Device Story
Cloud-based software service; analyzes heart sound/phonocardiogram (PCG) and optional ECG data. Inputs acquired via Eko DUO or Eko CORE stethoscopes; transmitted to Eko Cloud via mobile app or SDK-integrated third-party apps. Uses signal processing (waveform filtering) and machine learning algorithms to assess signal quality, detect/classify murmurs (innocent vs. structural), and determine S1/S2 timing. Outputs JSON results to requesting application for clinician display. Used in clinical environments by healthcare providers. Provides decision support to assist clinicians in ruling in/out pathological conditions; not a sole diagnostic tool. Benefits include automated murmur identification to augment physical assessment and clinical judgment.
Clinical Evidence
Retrospective analysis on proprietary database of 2,380 heart sound recordings from 615 subjects (age 0-95). Ground truth established via cardiologist annotation paired with echocardiogram. Murmur classification sensitivity 85.6% (95% CI: 82.6-88.7) and specificity 84.4% (95% CI: 81.3-87.5). S1 detection sensitivity 96.2% (PPV 97.1%); S2 detection sensitivity 92.3% (PPV 94.3%). No adverse events reported.
Technological Characteristics
Cloud-based software-only analysis tool. Inputs: PCG and ECG signals. Processing: Waveform filtering and machine learning algorithms. Outputs: JSON file containing murmur classification (innocent/structural/none) and S1/S2 timing. Connectivity: API-based integration with mobile/third-party applications. No hardware components.
Indications for Use
Indicated for pediatric and adult patients to provide clinical decision support for heart sound evaluation, including detection and classification of murmurs (innocent vs. structural) and timing of S1/S2 sounds.
Regulatory Classification
Identification
Manual stethoscope: A mechanical device used to project the sounds associated with the heart, arteries, and veins and other internal organs. Electronic stethoscope: An electrically amplified device used to project the sounds associated with the heart, arteries, and veins and other internal organs.
Special Controls
*Classification.* Class II (special controls). The device, when it is a lung sound monitor, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 870.9.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: a symbol on the left and the FDA name on the right. The symbol on the left is a stylized image of a human figure, while the FDA name on the right is written in blue letters. The words "U.S. FOOD & DRUG ADMINISTRATION" are written in a clear, sans-serif font.
June 29, 2022
Eko Devices, Inc. Sam Huang Director of Regulatory Affairs 1212 Broadway, Suite 100 Oakland, California 94612
Re: K213794
Trade/Device Name: Eko Murmur Analysis Software (EMAS) Regulation Number: 21 CFR 870.1875 Regulation Name: Stethoscope Regulatory Class: Class II Product Code: DQD, DQC, DPS Dated: Mav 28, 2022 Received: June 2, 2022
Dear Sam Huang:
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 statutes and regulations administered by other Federal agencies. You must comply with all the Act's
{1}------------------------------------------------
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 (OS) 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 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).
Sincerely,
LCDR 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}------------------------------------------------
#### Indications for Use
#### 510(k) Number (if known) K213794
#### Device Name
Eko Murmur Analysis Software (EMAS)
#### Indications for Use (Describe)
The Eko Murmur Analysis Software (EMAS) is intended to provide decision support to clinicians in their evaluation of patients' heart sounds. The software analyzes heart sounds and phonocardiograms (and ECG signals, when available). The software will automatically detect murmurs that may be present, and the murmur timing and character, including S1, S2, innocent heart murmurs, structural heart murmurs, and the absence of a heart murmur.
The Eko Murmur Analysis Software is not intended as a sole means of diagnosis and is for use in environments where health care is provided by clinicians. The interpretations of heart sounds offered by the software are meant only to provide decision support to the clinician, who may use the result in conjunction with their own evaluation and clinical judgment. The interpretations are not diagnoses. The Eko Murmur Analysis Software is intended for use on pediatic and adult patients.
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."
{3}------------------------------------------------
#### GENERAL INFORMATION
Applicant: Eko Devices, Inc. 1210 Broadway, Suite 100, Oakland, CA 94612 Phone: 844-356-3384
Contact Person: Sam Huang, Ph.D. Director of Regulatory Affairs Eko Devices, Inc. 1210 Broadway, Suite 100, Oakland, CA 94612
Date Prepared: Dec 03, 2021
### DEVICE INFORMATION
Trade/Proprietary Name: Eko Murmur Analysis Software (EMAS) Regulation number: 21 CFR 870.1875 Classification Name: Electronic Stethoscope Regulatory Class: Class II Product Code: DOD, DOC, DPS
### PREDICATE DEVICES
CSD Labs GmbH, eMurmur ID (K181988) Eko Devices, Inc., Eko Analysis Software (K192004)
### DEVICE DESCRIPTION
Eko Murmur Analysis Software (EMAS) is a cloud-based service that allows users to upload heart sound/phonocardiogram (PCG) and optional electrocardiogram (ECG) data via an application programming interface (API) for analysis. The software uses signal processing (such as waveform filtering), as well as algorithms derived from machine learning, to analyze the acquired data and generate clinical decision support output for clinicians. EMAS is designed to evaluate data derived by the company's two previously cleared devices, the Eko DUO (K170874) and Eko CORE (K151319, K200776). The heart sound data from those devices can be transmitted to the Eko Cloud using either the Eko mobile application or thirdparty applications that use a software development kit (SDK). The EMAS algorithm analyzes the heart sound data and outputs a JSON file with the algorithm results, which is passed down to the requesting application and displayed by the requesting application to the user in the humanreadable format.
{4}------------------------------------------------
The analysis will assess the signal quality of the phonocardiogram; detect heart murmurs and classify them as innocent or structural; determine the timing of S1 and S2 heart sounds; and distinguish between systolic and diastolic heart murmurs. As an integral part of a physical assessment, clinicians' interpretations of EMAS' output can help them rule in or out different pathological conditions in a patient.
The EMAS consists of the following algorithm components:
- Signal Quality Detection Algorithm: .
This pre-processing algorithm accepts as input the PCG sound from the API controller (e.g., a mobile smartphone application). The algorithm is used to classify PCG recordings based on their signal quality as good or poor.
- Heart Sound Timing Algorithm: ● This algorithm detects the presence and timing of specific heart sounds including S1, S2, the systole region, and the diastole region.
- Murmur Detection & Classification Algorithm: This algorithm is used to identify and classify heart sounds as having "No Murmur", an "Innocent Murmur" (i.e., not pathologic), or a "Structural Murmur" (i.e., pathologic).
- Murmur Timing Algorithm:
This algorithm is used to identify in which regions of the heart cycle (systole vs diastole) a heart murmur occurs if either an "Innocent Murmur" or "Structural Murmur" is identified by the Murmur Detection and Classification Algorithm.
## INDICATIONS FOR USE
The Eko Murmur Analysis Software is intended to provide decision support to clinicians in their evaluation of patients' heart sounds. The software analyzes heart sounds and phonocardiograms (and ECG signals, when available). The software will automatically detect murmurs that may be present, and the murmur timing and character, including S1, S2, innocent heart murmurs, structural heart murmurs, and the absence of a heart murmur.
The Eko Murmur Analysis Software is not intended as a sole means of diagnosis and is for use in environments where health care is provided by clinicians. The interpretations of heart sounds offered by the software are meant only to provide decision support to the clinician, who may use the result in conjunction with their own evaluation and clinical judgment. The interpretations are not diagnoses. The Eko Murmur Analysis Software is intended for use on pediatric and adult patients.
## SUBSTANTIAL EQUIVALENCE
Eko Murmur Analysis Software (EMAS) has the same intended use as the predicate devices for providing support to the physician in the evaluation of heart-related physiological data. Additionally, EMAS combines the indications of the predicate devices into a single product: algorithms to classify suspected murmurs as either innocent or structural, similar to that of the eMurmur ID; and algorithms that analyze heart sound data to identify the presence of suspected murmurs, similar to that of the Eko Analysis Software. Any differences in the Eko Murmur
{5}------------------------------------------------
Analysis Software's indication statement. i.e., omission of certain outputs and compatible device information, do not alter the intended diagnostic effect of the device.
Eko Murmur Analysis Software also has similar technological characteristics as the predicate devices in regard to it being a software-only analysis tool that analyzes and classifies heart sound data. EMAS's new technological characteristics, i.e., proprietary analysis algorithms, could affect its safety or effectiveness, but do not raise any different questions of safety or effectiveness, because they analyze the same data (input) to determine the same parameters (output) as those of the predicate devices. The performance testing data shown in this application demonstrate that the Eko Murmur Analysis Software is as safe and as effective as the predicate device(s).
A table comparing the key features of the subject and predicate devices is provided below.
| Parameters | Eko Murmur Analysis<br>Software | eMurmur ID<br>(Primary Predicate) | Eko Analysis<br>Software<br>(Secondary Predicate) |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| FDA Number | K213794 | K181988 | K192004 |
| Indications for<br>Use | The Eko Murmur Analysis<br>Software is intended to<br>provide decision support<br>to clinicians in their<br>evaluation of patients'<br>heart sounds. The software<br>analyzes heart sounds and<br>phonocardiograms (and<br>ECG signals, when<br>available). The software<br>will automatically detect<br>murmurs that may be<br>present, and the murmur<br>timing and character,<br>including S1, S2, innocent<br>heart murmurs, structural<br>heart murmurs, and the<br>absence of a heart<br>murmur.<br>The Eko Murmur Analysis<br>Software is not intended<br>as a sole means of<br>diagnosis and is for use in | The eMurmur ID software<br>system is a decision<br>support device for the<br>healthcare provider (the<br>user) in the evaluation of<br>patient heart sounds.<br>eMurmur ID is used to<br>record, display, analyze,<br>and store the acoustic<br>signal of the heart,<br>recorded by means of an<br>electronic stethoscope. The<br>automated analysis will<br>identify specific heart<br>sounds that may be present,<br>including S1, S2,<br>physiological heart<br>murmurs, pathological<br>heart murmurs and absence<br>of a heart murmur.<br>eMurmur ID is indicated<br>for use in a setting where<br>auscultation would | The Eko Analysis<br>Software is intended to<br>provide support to the<br>physician in the<br>evaluation of patients'<br>heart sounds and<br>ECG's. The software<br>analyzes simultaneous<br>ECG and heart sounds.<br>The software will<br>detect the presence of<br>suspected murmurs in<br>the heart sounds. The<br>software also detects<br>the presence of atrial<br>fibrillation and normal<br>sinus rhythm from the<br>ECG signal. In<br>addition, it calculates<br>certain cardiac time<br>intervals such as heart<br>rate, ORS duration and<br>EMAT. The software<br>does not distinguish |
| Parameters | Eko Murmur Analysis<br>Software | eMurmur ID<br>(Primary Predicate) | Eko Analysis<br>Software<br>(Secondary Predicate) |
| environments where<br>health care is provided by<br>clinicians. The<br>interpretations of heart<br>sounds offered by the<br>software are meant only to<br>provide decision support<br>to the clinician, who may<br>use the result in<br>conjunction with their<br>own evaluation and<br>clinical judgment. The<br>interpretations are not<br>diagnoses. The Eko<br>Murmur Analysis<br>Software is intended for<br>use on pediatric and adult<br>patients. | typically be performed by a<br>healthcare provider. It is<br>not intended as a sole<br>means of diagnosis. The<br>heart sound interpretations<br>offered by eMurmur ID are<br>only significant when<br>considered in conjunction<br>with healthcare provider<br>over-read and including all<br>other relevant patient data. | between different kinds<br>of murmurs and does<br>not identify other<br>arrhythmias.<br>It is not intended as a<br>sole means of<br>diagnosis. The<br>interpretations of heart<br>sounds and ECG<br>offered by the software<br>are only significant<br>when used in<br>conjunction with<br>physician over-read and<br>is for use on adults (><br>18 years). | |
| Patient<br>Population | Adult and pediatric<br>patients | Adult and pediatric patients | Adult patients |
| Device<br>Classification | DQD, DQC, DPS | DQD, DQC | MWI, DQD, DPS |
| Prescribed | Prescription Only | Prescription Only | Prescription Only |
| Components | Software Only | Software Only | Software Only |
| Interface | Callable application<br>programming interface<br>(API) | N/A (Self-contained<br>software application) | Callable application<br>programming interface<br>(API) |
| Display | No primary display | No primary display | No primary display |
| Murmur<br>Detection | Yes | Yes | Yes |
| Murmur<br>Classification | Yes | Yes | No |
## Table 1 Substantial Equivalence Summary Comparison
{6}------------------------------------------------
{7}------------------------------------------------
# PERFORMANCE DATA - NONCLINICAL TESTING SUMMARY
The Eko Murmur 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 issued May 11, 2005.
# PERFORMANCE DATA - CLINICAL TESTING SUMMARY
The algorithms in this submission have been validated using retrospective analysis on a proprietary database. The database contains 2.380 unique heart sound recordings from 615 unique subjects. In the proprietary database, all heart sound recordings were collected using the Eko CORE (67.6%) or Eko DUO (32.4%) digital stethoscopes. The subject population was 42.6% female and had an age range of 0 to 95 years old, race was recorded in 45% of the subjects and out of that subset, 98% were white, 1.5% were African American and 0.7% were Asian. No complications or adverse events were experienced during the use of the EMAS device.
All recordings were annotated by multiple cardiologists in respect to their quality and the presence of any murmur. Of the recordings identified as being good signal by the expert cardiologists, 45.8% had a confirmed structural murmur and 54,2% had a confirmed no murmur or innocent murmur. Ground truth for murmur classification was obtained via pairing cardiologist annotations with gold standard echocardiogram. Additionally, 299 heart sound recordings were annotated by expert cardiologists to obtain the timing of the S1 and S2 sounds. Cardiologists were blinded to all subject demographic data and echocardiogram findings during annotation.
No study subjects included in the training datasets were included in the test database. All algorithm testing was performed once the final EMAS version was locked.
The following tables demonstrate the results of the primary performance analyses (Murmur Classification and Heart Sound Timing).
### Table 2 EMAS Murmur Classification Performance
| | Sensitivity (%) | Specificity (%) |
|-----------------------|-------------------------------|-------------------------------|
| Murmur Classification | 85.6<br>(95% CI: 82.6 - 88.7) | 84.4<br>(95% CI: 81.3 - 87.5) |
The lower bounds of the 95% confidence intervals of the primary predicate device are 72.9% and 74.9% for sensitivity and specificity, respectively. Through clinical validation, the lower bound of EMAS' calculated 95% confidence interval is found to be above 75.0%, thus demonstrating substantially equivalent performance (effectiveness) to the predicate device (eMurmur).
{8}------------------------------------------------
| | | Sensitivity (%) | PPV (%) |
|-----------------------|--------------|-------------------------------|-------------------------------|
| Heart Sound<br>Timing | S1 Detection | 96.2<br>(95% CI: 94.9 - 97.4) | 97.1<br>(95% CI: 96.3 - 98.0) |
| | S2 Detection | 92.3<br>(95% CI: 90.3 - 94.3) | 94.3<br>(95% CI: 93.4 - 95.1) |
## Table 3 EMAS Heart Sound Timing Performance
Given the data described above, the EMAS algorithm testing shows substantially equivalent performance to the predicate devices where applicable. Based on the clinical performance, the Eko Murmur Analysis Software has a safety and effectiveness profile that is similar to the predicate devices.
## CONCLUSIONS
The Eko Murmur Analysis Software is as safe and as effective as the predicate devices. The Eko Murmur Analysis Software has the same intended uses and similar indications, technological characteristics, and principles of operation as its primary 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 Murmur Analysis Software and its predicate devices raise no new issues of safety or effectiveness. Performance data demonstrate that the Eko Murmur Analysis Software is as safe and effective as the predicate devices. Thus, the Eko Murmur Analysis Software is substantially equivalent.
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.