Steth IO
STRATOSCIENTIFIC, INC. • Cardiovascular • 07/15/2016
Device Purpose
The Steth IO is an acoustic medical device that integrates with a smartphone, utilizing an acoustic waveguide to channel heart and lung sounds to the phone's microphone for real-time audio output, phonocardiogram visualization, and data recording. It serves as a diagnostic aid for healthcare providers to detect, amplify, and analyze physiological sounds in adult patients during physical assessments in various medical settings.
Summary
The Steth IO Model 1.0 is an acoustic medical device designed to integrate with a smartphone to facilitate the collection and analysis of heart and lung sounds. It functions by attaching to the back of a smartphone, employing an acoustic waveguide to direct sound from its chest piece to the smartphone’s microphone, while concurrently serving as a protective case for the phone. An accompanying smartphone application enables real-time sound analysis, allowing clinicians to listen to auscultated sounds via headphones and visualize them as an on-screen phonocardiogram. This device is intended for use by healthcare providers as a diagnostic aid during physical assessments of adult patients in environments such as hospitals, clinics, and physician offices. It aids in the detection and amplification of physiological sounds within selective frequency ranges, with capabilities to record both the audio and phonocardiogram data for later review or consultation. Key features include its reliance on the smartphone for power, processing, display, and data storage, offering longer recording times and direct on-device visualization compared to some traditional electronic stethoscopes. Its primary contraindication is use on open skin lesions at the examination site.
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 acoustic performance of the Steth IO's fiberglass/epoxy diaphragm compare to traditional materials or the predicate's polyurethane-coated silicone in terms of sound fidelity and frequency response for cardiac and pulmonary auscultation?; What validation studies were conducted to ensure the real-time analysis and phonocardiogram visualization on the smartphone app accurately represent physiological sounds without introducing artifacts or misinterpretations?; Considering the reliance on a smartphone's microphone, what measures are in place to ensure consistent sound quality and calibration across different smartphone units or if the microphone degrades over time?; How does the Steth IO system address potential cybersecurity risks and ensure patient data privacy when phonocardiogram data is captured, stored, and potentially transmitted using a commercial smartphone platform?; What is the impact of the smartphone's processing power, operating system version, and concurrent background applications on the Steth IO application's performance, particularly concerning real-time analysis accuracy and the potential for software-induced diagnostic delays or errors?
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 SaaSBOM, HBOM, OBOM 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, ML-BOM, CBOM, VDR/VEX. 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