Cardiac CT Function Software Application
Circle Cardiovascular Imaging • Radiology • 06/07/2024
Device Purpose
The Cardiac CT Function Software Application utilizes AI/Machine Learning algorithms for semi-automatic segmentation of the left and right ventricles from cardiac CT angiography images to aid clinicians in assessing cardiac function. Its methodology involves processing DICOM images to calculate key volumetric and functional parameters, such as ejection fraction and myocardial mass, with performance validated against expert reader consensus.
Summary
The Cardiac CT Function Software Application, developed by Circle Cardiovascular Imaging, is a software tool designed to assist qualified medical professionals in the analysis of cardiac function using cardiovascular CT angiography images. It provides qualitative and quantitative evaluation capabilities by enabling visualization, assessment, and calculation of key cardiac metrics from DICOM standard images. The software features multi-planar reconstruction (MPR) views and 3D rendering, allowing users to manually draw regions of interest or utilize semi-automatic segmentation for the left ventricle (LV) and right ventricle (RV). It is intended as an aid to the standard of care, processing images acquired from various CT scanners without direct interface to the acquisition equipment. A core component of the CT Function Module is its Artificial Intelligence/Machine Learning (AI/ML) algorithm, which detects and segments heart structures (LV cavity, LV myocardium, and RV cavity). These AI-generated segmentations are converted into editable surfaces, emphasizing that users should verify and correct any inaccuracies, with options for full manual segmentation also available. The software calculates critical cardiac functional parameters including end-diastolic volume (EDV), end-systolic volume (ESV), stroke volume (SV), ejection fraction (EF), cardiac output (CO), cardiac index (CI), and LV myocardial mass. Performance validation, conducted against a reference standard from expert readers, demonstrated robust segmentation accuracy for the LV cavity (Dice > 86%, EF bias 1.3%), RV cavity (Dice > 85%, EF bias -5.5%), and LV myocardium (Dice > 82%), with comparable performance across diverse imaging conditions and patient demographics.
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 performance of the AI/ML segmentation for the RV, particularly the EF bias of -5.5%, compare to established clinical acceptance limits or the predicate device's RV performance?; Given the reliance on AI/ML, what is the variability in segmentation accuracy and subsequent metric calculation when encountering images with significant artifacts or rare cardiac pathologies not extensively represented in the training data?; The document mentions validation data was 90% from US sources; how was the algorithm's performance validated on diverse global populations and imaging protocols outside the US?; While LV myocardial mass is calculated, are there plans to extend AI/ML-based segmentation and mass calculation to the RV myocardium, and what are the anticipated challenges?; The predicate device includes regional wall motion analysis and left atrium segmentation; what was the rationale for not including these features, and are they planned for future iterations?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Post-§524B but no clear network capability detected
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.
• SBOM not mentioned in AI-generated device summary. Under §524B (effective Oct 2023), cyber devices must provide a SBOM.
• Cybersecurity risk assessment not referenced in AI-generated device summary. FDA cybersecurity guidance (2023) expects this for cyber devices.
• 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