Us2.v1
eko.ai Pte. Ltd. d/b/a Us2.ai • Radiology • 07/27/2021
Device Purpose
Us2.v1 is a software device utilizing machine learning for automated view classification and border detection to analyze and quantify adult transthoracic cardiac ultrasound images. It aims to support clinicians by generating comprehensive reports of cardiac structural and functional parameters, with its performance demonstrated as non-inferior to manual expert analysis in a retrospective validation study.
Summary
Us2.v1 is an image post-processing analysis software designed to assist in the diagnostic review and analysis of cardiovascular ultrasound images in DICOM format. Its primary function is to aid skilled sonographers by providing tools for manual or automated markup of echocardiographic data, which includes measurements of distance, time, area, blood flow, and quantitative analysis of cardiac function, ultimately generating a summary report for physician review. The software employs machine learning algorithms for automated view classification and border detection to facilitate this analysis, allowing sonographers to accept, modify, or reject the automated suggestions, and it organizes quantitative data against reference guidelines to support clinical decision-making for adult patients. The Us2.v1 software platform automatically processes, analyzes, and measures acquired transthoracic cardiac ultrasound images, producing a comprehensive report on numerous key cardiac structural and functional parameters. While indicated for adult patients, it has not been validated for conditions such as congenital heart disease, valve disease, pericardial disease, or intra-cardiac lesions, and its accuracy depends on good image quality and appropriate ultrasound acquisition settings. A retrospective non-interventional validation study involving 600 echocardiograms (from patients with heart failure with reduced ejection fraction and normal subjects) demonstrated that, compared to triplicate human measurements from an independent core laboratory, Us2.v1's automated measurements met a pre-specified non-inferiority margin using the individual equivalence coefficient (IEC), indicating its interchangeability with human readers for the assessed parameters.
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. What specific machine learning architectures are utilized for the automated view classification and border detection, and what were the key characteristics of the training dataset distinct from the validation set?; How does the Us2.v1 software account for or mitigate the impact of inter-operator variability and differences in ultrasound equipment on the accuracy of its automated measurements?; Beyond the overall non-inferiority established by the Individual Equivalence Coefficient (IEC), what are the specific agreement statistics (e.g., bias, limits of agreement) for each of the individual cardiac parameters measured by Us2.v1 compared to expert human readers?; Are there plans to validate Us2.v1 for the explicitly excluded conditions such as congenital heart disease, valve disease, or pericardial disease, and what challenges are anticipated?; What mechanisms are in place to ensure ongoing performance monitoring and algorithm updates for Us2.v1 as new echocardiographic data and clinical insights emerge?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (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.
• 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