eMurmur ID
CSD Labs GmbH • Cardiovascular • 04/17/2019
Device Purpose
The eMurmur ID system offers decision support for cardiac auscultation by leveraging an algorithm to analyze heart sounds captured via an electronic stethoscope and processed through a mobile application and backend server. Its core science involves automated identification and classification of various heart sounds, including pathological and physiological murmurs, and it has demonstrated enhanced diagnostic accuracy in clinical evaluations when compared to earlier technologies.
Summary
The eMurmur ID system functions as a decision support tool for healthcare providers evaluating patient heart sounds. Its methodology involves recording acoustic heart signals for 20 seconds using a compatible electronic stethoscope, the Littmann 3200, which then transmits the data via Bluetooth to a mobile application; this application forwards the recordings to a backend server where a specialized Heart Sound Analysis Algorithm processes the signals, and the system architecture also includes this backend (hosting an encrypted database and API), the mobile app (for data capture and results display), and a web portal (for data management). The scientific basis of eMurmur ID lies in its automated analysis of these acoustic recordings to identify normal heart sounds (S1, S2) and to differentiate between physiological murmurs, pathological murmurs, and the absence of any murmur; its efficacy was assessed in a pivotal clinical study with 120 subjects, comparing its diagnostic capabilities against a reference device using physician diagnoses confirmed by echocardiography as the standard, with results indicating eMurmur ID achieved a sensitivity of 85.0% and a specificity of 86.7%, statistically significantly superior to the reference device's 58.3% for both metrics.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the eMurmur ID Heart Sound Analysis Algorithm differentiate between subtle variations in physiological and pathological murmurs, and what specific acoustic features does it prioritize in its analysis?; What was the inter-observer variability among the expert physicians who established the 'gold standard' diagnosis in the clinical study, and how might this variability have influenced the reported sensitivity and specificity of the eMurmur ID system?; Beyond the binary classification of murmurs, does the eMurmur ID system provide any quantitative metrics or detailed characterizations of detected murmurs (e.g., timing, intensity, radiation, shape) that could further assist clinicians in etiological diagnosis?; What specific types of challenging heart conditions or patient characteristics (such as severe arrhythmias, obesity, chest wall deformities, or very young pediatric patients) might affect the accuracy of the eMurmur ID's automated analysis, and were these conditions explored in sub-group analyses of the pivotal clinical study?; Given the system's current reliance on the Littmann 3200 electronic stethoscope, how is the performance of the eMurmur ID algorithm affected by variations in recording quality due to user technique or ambient noise, and what is the potential for adapting the system to other electronic stethoscopes?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class C (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM, SaaSBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, HBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly