The 'eMurmur Heart AI' software is a decision support system in the evaluation of recorded patient heart sounds. The automated analysis by eMurmur Heart Al identifies specific heart sounds that may be present, including S1, S2, physiological heart murmurs, pathological heart murmurs and the absence of a heart murmur. eMurmur Heart Al 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 Heart AI are only significant when considered in conjunction with healthcare provider over-read and including all other relevant patient data.
Device Story
eMurmur Heart AI is a decision support software that analyzes digital heart sound recordings to identify S1, S2, and heart murmurs. Input requires a 20-second digital heart sound recording and patient age, captured via a supported digital stethoscope (e.g., Littmann 3200) and transmitted through the eMurmur platform (app/web portal) to a backend server. The algorithm processes the audio to detect and classify heart sounds, returning results to the front-end client for clinician review. Used in clinical settings by healthcare providers, the device output serves as an adjunct to physical auscultation and clinical judgment. It does not provide a definitive diagnosis; clinicians must integrate findings with other patient data. The system benefits patients by providing automated, objective analysis of heart sounds to support timely identification of potential cardiac abnormalities.
Clinical Evidence
No new clinical data provided. Substantial equivalence is based on the use of the identical heart sound analysis algorithm as the predicate device, eMurmur ID (K181988). Predicate clinical performance reported: Sensitivity 85.0% (95% CI: 72.9%-92.5%) and Specificity 86.7% (95% CI: 74.9%-93.7%).
Technological Characteristics
Server-hosted heart sound analysis algorithm; requires 20-second digital audio input and patient age. Connectivity via secure REST/JSON web API. Compatible with Littmann 3200 digital stethoscope. Cybersecurity features include encrypted traffic and database storage, user authentication, and access controls.
Indications for Use
Indicated for use by healthcare providers in clinical settings to assist in the evaluation of recorded heart sounds in patients. Identifies S1, S2, physiological murmurs, pathological murmurs, or absence of murmurs. Not for sole diagnosis; requires clinician 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 Department of Health & Human Services and the Food and 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 square, followed by the words "U.S. FOOD & DRUG" and "ADMINISTRATION" in blue text.
May 31, 2022
CSD Labs GmbH % Allison Komiyama Principal Consultant Ram+ 2251 San Diego Ave, Suite B-257 San Diego, California 92110
Re: K220766
Trade/Device Name: eMurmur Heart AI Regulation Number: 21 CFR 870.1875 Regulation Name: Stethoscope Regulatory Class: Class II Product Code: DQD, DQC Dated: May 6, 2022 Received: May 9, 2022
Dear Allison Komiyama:
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}------------------------------------------------
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,
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}------------------------------------------------
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
**Indications for Use**
| Form Approved: | OMB No. 0910-0120 |
|------------------|-------------------|
| Expiration Date: | 06/30/2023 |
See PRA Statement below.
510(k) Number (if known)
K220766
Device Name
#### eMurmur Heart Al
Indications for Use (Describe)
The 'eMurmur Heart AI' software is a decision support system in the evaluation of recorded patient heart sounds. The automated analysis by eMurmur Heart Al identifies specific heart sounds that may be present, including S1, S2, physiological heart murmurs, pathological heart murmurs and the absence of a heart murmur.
eMurmur Heart Al 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 Heart AI 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)
| <div> <span style="font-size:10pt"> <span style="font-family:Wingdings">✓</span> </span> Prescription Use (Part 21 CFR 801 Subpart D) </div> |
|---------------------------------------------------------------------------------------------------------------------------------------------------|
| <div> <span>▢</span> Over-The-Counter Use (21 CFR 801 Subpart C) </div> |
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}------------------------------------------------
## 510(k) SUMMARY
#### CSD Labs' eMurmur Heart Al
## SPONSOR
| Company name: | CSD Labs GmbH |
|------------------|----------------------------------------|
| Company address: | Nikolaiplatz 4<br>8020 Graz<br>Austria |
| Phone: | +43 650 5272666 |
| Contact Person: | Andreas Reinisch |
| Date Prepared: | March 14, 2022 |
#### CONSULTANT
| Company name: | RQM+ |
|------------------|--------------------------------------------------------|
| Company address: | 2251 San Diego Ave. Ste B-257<br>San Diego, CA 92110 |
| Phone: | (412) 816-8253 |
| Contact Person: | Allison Komiyama, PhD, RAC<br>Anike Freeman, MEng, PMP |
## DEVICE
| Trade Name: | <b>eMurmur Heart Al</b> |
|-----------------------|----------------------------------------------------|
| Common or usual name: | Computer Aided Auscultation, Heart Sounds Analyzer |
| Classification name: | Electronic Stethoscope; Phonocardiograph; |
| Regulation number: | 21 CFR 870.1875, 870.2390 |
| Product code: | DQD, DQC |
| Device class: | Class II |
| Reviewing panel: | Cardiology |
# PREDICATE DEVICE
| Company | CSD Labs GmbH |
|---------|---------------|
| Product | eMurmur ID |
| 510(k) | K181988 |
#### INDICATIONS FOR USE
The 'eMurmur Heart AI' software is a decision support system in the evaluation of recorded patient heart sounds. The automated analysis by eMurmur Heart Al identifies specific heart sounds that may be present, including S1, S2, physiological heart murmurs, pathological heart murmurs and the absence of a heart murmur.
eMurmur Heart AI 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 Heart AI are only significant when considered in conjunction with healthcare provider over-read and including all other relevant patient data.
{4}------------------------------------------------
# DEVICE DESCRIPTION
To analyze heart sounds via the eMurmur Heart AI, a digital recording of a patient's heart sounds is required. Recordings are made using a supported digital stethoscope, connected to a front-end client like, e.g., the eMurmur app or the eMurmur web portal. The recorded auscultation data are transmitted from the front-end client to the eMurmur backend, which hosts the eMurmur Heart Al. After analysis by the eMurmur Heart Al, the results of the analysis are returned to the front-end client where they are displayed to the user. The user can utilize the eMurmur Heart AI results to support their decision-making process regarding the potential presence and type of a heart murmur.
eMurmur is a non-medical device software platform which includes the eMurmur backend, eMurmur apps and eMurmur web portal. The platform is used to stream, record, display. replay, and store auscultation data, recorded by means of supported digital stethoscopes.
The eMurmur software platform has functions subject to FDA premarket review, i.e., eMurmur Heart AI, as well as functions that are not subject to FDA premarket review. For this application. FDA assessed those functions only to the extent that they could adversely impact the safety and effectiveness of the functions subject to FDA premarket review.
# TECHNOLOGICAL CHARACTERISTICS
The eMurmur Heart Al has the same technological characteristics as the predicate device eMurmur ID. It can be accessed via the eMurmur backend, which in turn communicates with the front-end clients, e.g., the eMurmur app and eMurmur web portal.
- Both systems use the same heart sound analysis algorithm, hosted on a server, requiring 1. a 20 second digital heart sound recording and the patient's age as input.
- 2. Both systems provide heart sound analysis outputs and additional supporting information to the user.
- 3. Both systems provide the transfer of auscultation data and the analysis results through a secure connection.
- 4. Both systems employ equivalent usability and cybersecurity features.
- 5. Both systems use the electronic stethoscope Littmann 3200 by 3M (MN, USA) (K083903) for the acquisition of the heart sounds that are to be analyzed.
## PERFORMANCE DATA
eMurmur Heart AI and the predicate, eMurmur ID (K181988), utilize the same heart sound analysis algorithm, hence no new performance data is required.
All applicable verification measures (unit tests, system tests, inspections) that were performed for the predicate were also performed for the current device, using the same pass/fail criteria.
# SUBSTANTIAL EQUIVALENCE
eMurmur Heart AI and eMurmur ID differ only in scope. For the previously cleared device eMurmur ID, all components of the software system (mobile app, web portal, backend, etc.) were treated as a medical device. For eMurmur Heart AI, only the relevant component, i.e., the algorithm analyzing heart sounds, is treated as a medical device. The other components which are solely intended to transfer, store, convert and display medical data or results are excluded from the scope of the medical device.
Thus, eMurmur Heart AI is substantially equivalent to eMurmur ID, see the table below.
{5}------------------------------------------------
| | eMurmur Heart Al | eMurmur ID |
|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Indications for<br>Use | The 'eMurmur Heart Al' software is a<br>decision support system in the evaluation<br>of recorded patient heart sounds. The<br>automated analysis by eMurmur Heart<br>Al identifies specific heart sounds that<br>may be present, including S1, S2,<br>physiological heart murmurs, pathological<br>heart murmurs and the absence of a<br>heart murmur.<br><br>eMurmur Heart Al is indicated for use in<br>a 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 Heart<br>Al are only significant when considered in<br>conjunction with healthcare provider over-<br>read and including all other relevant<br>patient data.<br><br>'eMurmur' is a non-medical device<br>software platform which includes the<br>eMurmur apps and eMurmur web portal.<br>The platform is used to stream, record,<br>display, replay, and store auscultation<br>data, recorded by means of supported<br>digital stethoscopes. eMurmur Heart Al<br>interacts with the 'eMurmur' software<br>platform. | The eMurmur ID software system is a<br>decision support device for the healthcare<br>provider (the user) in the evaluation of<br>patient heart sounds. eMurmur ID is used<br>to record, display, analyze, and store the<br>acoustic signal of the heart, recorded by<br>means of an electronic stethoscope. The<br>automated analysis will identify specific<br>heart sounds that may be present,<br>including S1, S2, physiological heart<br>murmurs, 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 typically<br>be performed by a healthcare provider. It<br>is not intended as a sole means of<br>diagnosis. The heart sound interpretations<br>offered by eMurmur ID are only significant<br>when considered in conjunction with<br>healthcare provider over-read and<br>including all other relevant patient data. |
| User Population | Identical | Healthcare provider licensed or authorized<br>to perform auscultation |
| Acquires and<br>Records Heart<br>Sounds | Identical | Acquires acoustic signals of the heart by<br>means of electronic stethoscope and<br>mobile app |
| Analyzes Heart<br>Sounds | Identical | Distinguishes between<br>normal/physiological and pathological<br>heart murmurs |
| User Interface | The user interface is not a part of<br>eMurmur Heart Al (medical device);<br>the user interface is part of 'eMurmur',<br>a non-medical device. | Android app for recording heart sounds,<br>sending analysis requests and receiving<br>analysis results. Web portal for reviewing<br>and editing user and patient data, OS<br>independent. |
| Backend | The backend is not a part of eMurmur<br>Heart AI (medical device); the backend<br>is part of 'eMurmur', a non-medical<br>device. | Server analyzes (algorithm) and stores<br>(database) patient-related data and<br>communicates with the other components<br>of eMurmur ID. The interface to the other<br>components is a REST/JSON web API. |
| Accessories | Identical | Electronic stethoscope Littmann 3200 |
| Safety Features | Identical | 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 health<br>information is stored on the user's<br>devices, user needs to authenticate, user<br>can only access authorized data |
| Clinical<br>Performance | Identical | Sensitivity: 85.0% (72.9%-92.5%)<br>Specificity: 86.7% (74.9%-93.7%) |
# Table 1. Substantial Equivalence Summary Comparison Table
{6}------------------------------------------------
# CONCLUSIONS
The medical device eMurmur Heart Al has the same intended use, similar indications for use, and the same technological characteristics, and principles of operation as eMurmur ID. Thus, eMurmur Heart AI is substantially equivalent to eMurmur ID.
eMurmur Heart AI consists of the same heart sound analysis algorithm as eMurmur ID. Other components that were part of the eMurmur ID medical device (e.g., the app and web portal) have been excluded from the eMurmur Heart Al medical device, since these components are software solely intended to transfer, store, convert and display medical data or results.
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.