The eMurmur ID software system is a decision support device for the healthcare provider (the user) in the evaluation of patient heart sounds. eMurmur ID is used to record, display, analyze, and store the acoustic signal of the heart, recorded by means of an electronic stethoscope. The automated analysis will identify specific heart sounds that may be present, including S1, S2, physiological heart murmurs, pathological heart murmurs and absence of a heart murmur. eMurmur ID is indicated for use in a setting where auscultation would typically be performed by a healthcare provider. It is not intended as a sole means of diagnosis. The heart sound interpretations offered by eMurmur ID are only significant when considered in conjunction with healthcare provider over-read and including all other relevant patient data.
Device Story
eMurmur ID is a software-based decision support system for heart sound evaluation. It utilizes a 20-second digital heart sound recording captured via an off-the-shelf electronic stethoscope (Littmann 3200). Data is transmitted via Bluetooth to a mobile app, then uploaded to a secure backend server for automated analysis. The system identifies S1, S2, and presence/type of heart murmurs. Results are returned to the mobile app for display alongside visual/acoustic playback. Used by healthcare providers in clinical settings, the device provides decision support; clinicians must perform an over-read and integrate findings with other patient data. Benefits include assisting in the identification of pathological murmurs, potentially improving diagnostic accuracy during routine auscultation.
Clinical Evidence
Prospective clinical study of 120 subjects (all ages, 50% pathological/50% innocent or no murmur). Compared eMurmur ID to SensiCardiac (K121617) using expert auscultation verified by echocardiography as ground truth. eMurmur ID sensitivity: 85.0% (95% CI: 72.9%-92.5%); specificity: 86.7% (95% CI: 74.9%-93.7%); accuracy: 85.8% (95% CI: 78.0%-91.3%). eMurmur ID demonstrated statistically significant improvement over the reference device (p<0.002 for all metrics). Bench testing, EMC, electrical safety, and wireless coexistence testing also performed.
Technological Characteristics
Software system comprising mobile app, web portal, and backend server. Uses off-the-shelf Littmann 3200 electronic stethoscope for acoustic signal acquisition. Connectivity via Bluetooth and secure internet (REST/JSON API). Data encrypted at rest and in transit. Backend hosts heart sound analysis algorithm and database. No PHI stored on user devices.
Indications for Use
Indicated for healthcare providers performing auscultation to evaluate heart sounds in patients of all ages. Used to identify S1, S2, physiological murmurs, pathological murmurs, or absence of murmurs. Not for sole diagnosis; requires provider over-read.
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 contains the logos of the U.S. Department of Health & Human Services and the U.S. Food & Drug Administration (FDA). The Department of Health & Human Services logo is on the left, and the FDA logo is on the right. The FDA logo includes the letters "FDA" in a blue box, followed by the words "U.S. Food & Drug Administration" in blue text. The word "Administration" is in a smaller font size than the other words.
April 17, 2019
CSD Labs GmbH % Yarmela Pavlovic Partner Hogan Lovells US LLP 3 Embarcadero Center San Francisco, California 94501
# Re: K181988
Trade/Device Name: eMurmur ID Regulation Number: 21 CFR 870.1875 Regulation Name: Stethoscope Regulatory Class: Class II Product Code: DOD, DOC Dated: March 19, 2019 Received: March 19, 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 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
{1}------------------------------------------------
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/CombinationProducts/GuidanceRegulatoryInformation/ucm597488.htm); 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 http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm.
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/DeviceRegulationandGuidance/) and CDRH Learn (http://www.fda.gov/Training/CDRHLearn). 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 (http://www.fda.gov/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 C. Browning -S5
for
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K181988
Device Name eMurmur ID
#### Indications for Use (Describe)
The eMurmur ID software system is a decision support device for the user) in the evaluation of patient heart sounds. eMurmur ID is used to record, display, and store the acoustic signal of the heart, recorded by means of an electronic stethoscope. The automated analysis will identify specific heart sounds that may be present, including S1, S2, physiological heart murmurs, pathological heart murmurs and absence of a heart murmur.
eMurmur ID is indicated for use in a setting where auscultation would typically be performed by a healthcare provider. It is not intended as a sole means of diagnosis. The heart sound interpretations offered by eMurmur ID are only significant when considered in conjunction with healthcare provider over-read and including all other relevant patient data.
**Type of Use (Select one or both, as applicable)**
X 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 Druq 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}------------------------------------------------
#### 510(k) SUMMARY
## CSD Labs' eMurmur ID (K181988)
#### SPONSOR
Company name: CSD Labs GmbH Company address: Nikolaiplatz 4 8020 Graz Austria Contact Person: Andreas Reinisch Date Prepared: March 19, 2019
#### DEVICE
Trade Name: eMurmur ID Computer Aided Auscultation, Heart Sounds Analyzer Common or usual name: Classification name: Electronic Stethoscope; Phonocardiograph; Requlation number: 21 CFR 870.1875, 870.2390 Product code: DQD, DQC Device class: Class II Reviewing panel: Cardiology PREDICATE DEVICE
| Company | Product | 510(k) |
|----------------------------|-------------------|-----------------------------|
| Diacoustic Medical Devices | SensiCardiac Mobi | K131044 (Primary Predicate) |
| Discoustic Medical Devices | SensiCardiac | K121617 (Reference Device) |
#### INDICATIONS FOR USE
The eMurmur ID software system is a decision support device for the healthcare provider (the user) in the evaluation of patient heart sounds. eMurmur ID is used to record, display, analyze, and store the acoustic signal of the heart, recorded by means of an electronic stethoscope. The automated analysis will identify specific heart sounds that may be present, including S1, S2, physiological heart murmurs, pathological heart murmurs and absence of a heart murmur.
eMurmur ID is indicated for use in a setting where auscultation would typically be performed by a healthcare provider. It is not intended as a sole means of diagnosis. The heart sound interpretations offered by eMurmur ID are only significant when considered in conjunction with healthcare provider over-read and including all other relevant patient data.
#### DEVICE DESCRIPTION
eMurmur ID is a software system comprised of the following components:
- 1. The eMurmur ID Backend, running on a server environment, hosts the eMurmur ID Heart Sound Analysis Algorithm, an encrypted database for archiving patient and user information, and an application programming interface (API) for communication with the web portal and mobile application.
{4}------------------------------------------------
- 2. The eMurmur ID Mobile App, which runs on a mobile device. The app permits the following activities:
- a. Electronic recording of heart sound signals via a compatible electronic stethoscope, the Littmann 3200
- b. Visual and acoustic playback of heart and lung sounds
- Capturing patient information C.
- d. Transferring data to and from the eMurmur ID backend through a secure connection
- Displaying heart sound analysis results e.
- 3. The eMurmur ID Web Portal, which provides the following functionalities:
- a. Capturing and editing patient information
- Displaying and editing patient encounters including heart sound analysis results b.
- C. Visual and acoustic playback of heart and lung sounds
- d. Downloading reports (PDF) and heart and lung sound recordings
- Transferring data to and from the eMurmur ID backend through a secure connection e.
The acquisition of the acoustic data is carried out by the FDA-cleared off-the-shelf electronic stethoscope Littmann 3200 by 3M (MN, USA) (K083903).
For heart sounds to be analyzed by the heart sound analysis algorithm, a 20 second digital recording of the patient's heart sounds and the patient's date of birth are required. Heart sounds are recorded using the compatible, FDA-cleared, off-the-shelf electronic stethoscope Littmann 3200. The heart sounds are transmitted via Bluetooth to a mobile device running the eMurmur ID mobile app. The app then stores and sends the recorded data to the eMurmur ID backend for analysis. The results of the heart sound analysis are returned to the app within a few seconds, where they are displayed to the user together with the heart sound recording. The user can utilize the heart sound analysis results and the acoustic and visual representation of the heart sound recordings as decision support data in their decision-making process regarding the presence and type of a heart murmur.
# TECHNOLOGICAL CHARACTERISTICS
eMurmur ID has technological characteristics that are comparable to the predicate and reference devices:
- 1. Each of the systems host a heart sound analysis algorithm, a web API and a database on a backend server.
- 2. Each of the systems provide the user with a mobile app, which is used to record heart sounds and patient information. The mobile app transfers the data to the backend through a secure connection and displays the analysis results to the user.
- 3. Each of the systems require an FDA-cleared off-the-shelf electronic stethoscope for the acquisition of the heart sounds.
- 4. Each of the devices provide similar heart sound analysis output and similar additional supporting information to the user.
{5}------------------------------------------------
| | eMurmur ID (K181988) | SensiCardiac Mobi (K131044)<br>(Primary Predicate) | SensiCardiac (K121617)<br>(Reference Device) |
|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Intended Use /<br>Indications for<br>Use | The eMurmur ID software system is a<br>decision support device for the<br>healthcare provider (the user) in the<br>evaluation of patient heart sounds.<br>eMurmur ID is used to record, display,<br>analyze, and store the acoustic signal<br>of the heart, recorded by means of an<br>electronic stethoscope. The automated<br>analysis will identify specific heart<br>sounds that may be present, including<br>S1, S2, physiological heart murmurs,<br>pathological heart murmurs and<br>absence of a heart murmur.<br><br>eMurmur ID is indicated for use in a<br>setting where auscultation would<br>typically be performed by a healthcare<br>provider. It is not intended as a sole<br>means of diagnosis. The heart sound<br>interpretations offered by eMurmur ID<br>are only significant when considered in<br>conjunction with healthcare provider<br>over-read and including all other<br>relevant patient data. | The SensiCardiac Mobi Diagnostic is an<br>electronic auscultatory device, intended<br>to provide support to the physician in the<br>evaluation of patients' heart sounds.<br><br>The product acquires and records the<br>acoustic signals of the heart and<br>analyzes these signals. The analysis<br>procedure will identify specific heart<br>sounds that may be present. Identified<br>sounds include S1, S2, and suspected<br>murmurs. The device is indicated for use<br>in a clinical setting, by a physician or by<br>trained personnel who are acting on the<br>order of a licensed physician. It is not<br>intended as a sole means of diagnosis.<br><br>The interpretation of heart sounds offered<br>by the SensiCardiac Mobi are only<br>significant when used in conjunction with<br>physician over-read as well as<br>consideration of all other relevant patient<br>data. | Sensi is a decision support software<br>package intended to assist medical<br>examiners in heart auscultation.<br><br>The Sensi Diagnostic Heart Murmur<br>Software distinguishes between<br>normal/physiological and<br>pathological heart murmurs by<br>analyzing the acoustic heart signals<br>captured with an electronic<br>stethoscope. The device will record<br>the acoustic sound of the heart at the<br>four main auscultation positions. The<br>acoustic heart signal is analyzed to<br>identify heart sounds that may be<br>present, identified sounds include<br>S1, S2 and suspected murmurs. |
| User Population | Healthcare provider licensed or<br>authorized to perform auscultation | Healthcare provider licensed or<br>authorized to perform auscultation | Healthcare provider licensed or<br>authorized to perform auscultation |
| Acquires and<br>Records Heart<br>Sounds | Yes – acoustic signal of heart by<br>means of electronic stethoscope and<br>mobile app | Yes – acoustic signal of heart by means<br>of electronic stethoscope and mobile app | Yes – acoustic signal of heart by<br>means of electronic stethoscope and<br>Windows desktop app |
| Analyzes Heart<br>Sounds | Yes – distinguishes between<br>normal/physiological and pathological<br>heart murmurs | Yes - distinguishes between<br>normal/physiological and pathological<br>heart murmurs | Yes - distinguishes between<br>normal/physiological and<br>pathological heart murmurs |
{6}------------------------------------------------
| Y |
|------|
| 1819 |
| 88 |
| | eMurmur ID (K181988) | SensiCardiac Mobi (K131044)<br>(Primary Predicate) | SensiCardiac (K121617)<br>(Reference Device) |
|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| User Interface | Android app for recording heart<br>sounds, sending analysis requests and<br>receiving analysis results. Web portal<br>for reviewing and editing user and<br>patient data, OS independent. | Recording and analysis are conducted on<br>an iOS mobile app, which is also used for<br>reviewing auscultations. | Recording and analysis are<br>conducted on a Windows desktop<br>app, which is also used for reviewing<br>auscultations. |
| Backend | Server analyzes (algorithm) and stores<br>(database) patient-related data and<br>communicates with the other<br>components of eMurmur ID. The<br>interface to the other components is a<br>REST/JSON web API. | Equivalent architecture. The API uses the<br>XML data format instead of JSON. Is<br>equipped with algorithm identical to<br>K121617. | Equivalent architecture. Instead of a<br>mobile app, a desktop app is used.<br>The API uses the XML data format<br>instead of JSON. The equivalence of<br>algorithm performance is<br>demonstrated in a clinical trial. |
| Safety Features | Encrypted internet traffic, data stored in<br>the database on the backend is<br>encrypted, data in the database is<br>duplicated to another database in a<br>different datacenter, no protected<br>health information is stored on the<br>user's devices, user needs to<br>authenticate, user can only access<br>authorized data | Identical regarding aspects that are<br>verifiable by CSD Labs. | Identical regarding aspects that are<br>verifiable by CSD Labs. |
{7}------------------------------------------------
### PERFORMANCE DATA
Performance data included software verification and validation testing, electromagnetic compatibility, electrical safety, wireless coexistence, and bench validation testing using existing heart sound databases. It also included a pivotal clinical study. The pivotal clinical study was conducted comparing eMurmur ID to the reference device, SensiCardiac (K121617) — the predecessor to the primary predicate, SensiCardiac Mobi (K131044), which was not yet commercially available for comparison at the time of testing — in a prospective clinical investigation. It verified the hypothesis that eMurmur ID can distinguish between AHA class I (pathologic murmurs) and AHA class III heart sounds (innocent murmurs and/or no murmurs) with a sensitivity and specificity not worse than that of the predicate device.
The study population consisted of 120 subjects across all ages where 50% had a confirmed pathological murmur (class )) and 50% had a confirmed innocent or no murmur (class III). Patient's heart sounds were recorded by the expert physician and analyzed by both eMurmur ID and the predicate device. The findings for both devices were compared to clinical gold standard reference, defined as the expert physician's auscultation-based diagnosis, independently verified by cardiac echocardiography.
The following table shows the results of the primary (sensitivity, specificity) and secondary (accuracy) endpoints of the study with their respective 95% confidence intervals. The results were compared using the 95%-Fleiss confidence interval method for paired binary data.
| | eMurmur ID | SensiCardiac |
|----------------------|---------------------|---------------------|
| Sensitivity (95% CI) | 85.0% (72.9%-92.5%) | 58.3% (44.9%-70.7%) |
| Specificity (95% CI) | 86.7% (74.9%-93.7%) | 58.3% (44.9%-70.7%) |
| Accuracy (95% CI) | 85.8% (78.0%-91.3%) | 58.3% (49.0%-67.2%) |
The results of the study met the criteria for successfully demonstrating that eMurmur ID performance was not worse than the predicate device. In fact, the actual study results demonstrated that the eMurmur ID performed statistically significantly better than the predicate with respect to both sensitivity (p=0.0014) and specificity (p=0.0009), as well as with respect to overall accuracy (p<0.0001).
In all instances, eMurmur ID functioned as intended, and the electromagnetic compatibility, bench testing, and clinical performance observed were as expected.
# CONCLUSIONS
Performance data demonstrate that the eMurmur ID software system performs in a manner that is comparable to the reference device, meeting the criteria that it be at least non-inferior. eMurmur ID has the same intended uses and similar indications, technological characteristics, and principles of operation as the predicate device. The minor technological differences between eMurmur ID and its predicate device raise no new questions of safety or effectiveness. Thus, eMurmur ID 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.