Caption Interpretation Automated Ejection Fraction Software
Caption Health • Radiology • 07/22/2020
Device Purpose
The Caption Interpretation Automated Ejection Fraction Software utilizes machine learning algorithms to process transthoracic cardiac ultrasound images from various views, automatically calculating left ventricular ejection fraction to aid clinicians in cardiac assessments. Performance studies demonstrate its ability to accurately select image clips and estimate LVEF, particularly with combined or AP4 views, offering a quantifiable and consistent alternative or adjunct to manual methods.
Summary
The Caption Interpretation Automated Ejection Fraction Software is a medical device designed for adult patients, assisting clinicians in cardiac evaluations by providing automated estimation of left ventricular ejection fraction (LVEF). It processes previously acquired transthoracic cardiac ultrasound images using machine learning algorithms, functioning on ultrasound devices, personal computers, or compatible DICOM-compliant PACS systems. The software's core science lies in its algorithms which select optimal image clips from apical four-chamber (AP4), apical two-chamber (AP2), or parasternal long-axis (PLAX) views (or combinations) to calculate LVEF. Outputs include the LVEF percentage and a confidence metric, with this version benefiting from optimized algorithms via additional training and broader view compatibility. Extensive performance testing, including software verification and validation, confirmed design adherence. A "Clip Annotator" study showed high accuracy (PPV >97%, sensitivity >90%) for view and mode identification against expert consensus. A pivotal clinical investigation validated the AutoEF calculation against conventional LVEF methods. The primary endpoint, the root mean square deviation (RMSD) between AutoEF (using best view combinations) and a reference method, met acceptance criteria, as did combinations of AP2, AP4, or PLAX views. While single-view LVEF from AP2 and PLAX did not meet RMSD criteria, they outperformed physicians' quantitative visual assessments, and their RMSD was lower than sonographers' pre-overread tracings. Single-view AP4 met criteria and surpassed physician visual assessment. The confidence metric was also validated for estimating LVEF error ranges.
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 algorithm's performance for LVEF estimation vary across different patient demographics (e.g., age, sex, BMI, presence of arrhythmias) not explicitly detailed in the summary?; What specific machine learning models are employed, and what were the key features of the "additional training" that led to optimized EF estimation algorithms?; Given that AP2 and PLAX single-view EF estimations did not meet the primary RMSD acceptance criteria, what are the clinical implications and recommended best practices for clinicians when only these views are available or of sufficient quality?; How does the "confidence indication" quantitatively correlate with the actual error margin, and how should clinicians interpret varying levels of confidence in their decision-making process?; What are the performance characteristics of the software when processing suboptimal quality ultrasound images, and how does its clip selection algorithm handle images with significant artifacts or poor endocardial definition?
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 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, SaaSBOM, 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