Medscape Medical NewsAll articles

DASI Dimensions (V1.0)

DASI Simulations • Radiology • 01/08/2024

510(k)IEC 62304 Class B
FDA Summary PDF

Device Purpose

DASI Dimensions (V1.0) is a clinical decision support software that processes patient CTA scans using an AI-enhanced workflow, incorporating proprietary algorithms and human quality assurance, to deliver precise anatomical measurements of cardiovascular structures for pre-procedural TAVR planning in aortic stenosis patients. The system's methodology relies on automated detection of aortic root control points and calculation of key dimensions, with its accuracy, reliability, and usability validated through comprehensive non-clinical testing.

Summary

DASI Dimensions (V1.0) is a standalone, non-invasive clinical decision support software designed for cardiologists and radiologists to aid in pre-procedural planning for Transcatheter Aortic Valve Replacement (TAVR) in patients with aortic stenosis. The system operates off-site, receiving patient-specific multiphase DICOM computed tomography angiography (CTA) chest image files uploaded by clinicians via a web portal. It then processes these images using proprietary algorithms, which include a static deep learning artificial intelligence (AI) model for detecting key aortic root control points, and calculates various anatomical measurements. DASI Simulations engineers perform quality checks on these AI-assisted detections and calculations before a report containing pre-defined images and measurements (diameters, lengths, angles, areas, perimeters) of cardiovascular structures like the aorta, aortic root, and aortic valve is released to the end-user for viewing and downloading. The core technology involves automated segmentation and centerline detection of cardiac structures, specifically targeting the aortic root, aortic valve, sinus of valsalva, sinotubular junction, and ascending aorta relevant to TAVR. Non-clinical validation studies demonstrated the system's performance. For instance, in a performance validation study, AI-generated control points achieved an 85.3% success rate (points within a 3mm error tolerance), exceeding the study's acceptance threshold. Automatic measurements, such as primary outputs like annulus area, showed mean percentage errors around 1% compared to clinician manual measurements, meeting acceptance criteria of ≤10% error in ≥95% of cases. Operator variability was low (ICC 0.96 for annulus area), and usability testing confirmed the interface was user-friendly. Sensitivity analysis indicated that key measurements like annulus area remained within a 10% error margin even with 3mm perturbations in control points. The software provides measurements but is not diagnostic, and clinicians retain full responsibility for all treatment decisions.

AI Regulatory Concerns

Powered byJev by TypeSafe AI

Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.

Keywords

TAVR planningAortic stenosisClinical decision supportCTA imagingAI modelCardiovascular measurementsAortic rootImage post-processingDICOMSoftware validation

Device Metadata

Submission Number
K231324
Company
DASI Simulations
Panel
Radiology
Product Code
N/A
Data Type
Images
Clinical Function
Assessment
AI Function
Analysis
AI Subclass
quantification/feature localization

Relevant Clinical Questions

  • Q1. How does the performance of the AI model in detecting aortic root control points vary across different patient anatomies or image qualities not extensively covered in the validation cohort?; What is the specific definition and clinical relevance of 'primary,' 'secondary,' and 'tertiary' measurements, and how were these categories determined for setting differential error acceptance criteria?; Given that DASI Simulations engineers perform quality checks, what is the typical intervention rate, and what are the common reasons for manual adjustments to the AI-generated control points or measurements?; How does the 'static' nature of the deep learning AI model accommodate evolving anatomical understanding or new imaging protocols without requiring frequent re-validations?; What are the performance metrics of DASI Dimensions when compared directly against the predicate device (K153736, 3mensio Workstation) using the same dataset, particularly for the overlapping functionalities?

Risk Classification

ESL Analysis
FDA Device ClassII

FDA 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.

Cyber Score5/100
SBOM Evidence⚠ Not in summary - likely in full submission per §524B
Cyber Risk Assessment⚠ Not in summary - likely in full submission per §524B
Postmarket Plan⚠ Not in summary - likely in full submission per §524B
§524B ApplicableYes

Supply Chain BOM Evidence

Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.

SBOMSoftware Bill of Materials
- Not detected
ML-BOMMachine Learning Bill of Materials(deep learning, algorithm, dataset)
✓ Detected
SaaSBOMSoftware-as-a-Service Bill of Materials
- Not detected
HBOMHardware Bill of Materials
- Not detected
CBOMCryptography Bill of Materials
- Not detected
VDR/VEXVulnerability Disclosure Report / Vulnerability Exploitability eXchange
- Not detected
OBOMOperations Bill of Materials
- Not detected

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
DASI Dimensions (V1.0) - DASI Simulations | ESL FDA AI Device Intelligence