ADAS 3D
Galgo Medical S.L • Radiology • 01/15/2020
Device Purpose
ADAS 3D is a software tool designed to enhance the clinical understanding of cardiovascular disease by enabling advanced post-processing, 3D visualization, and quantitative analysis of cardiac MR and CTA images, specifically focusing on myocardial scar and related anatomical features. It utilizes specialized algorithms to process DICOM images, quantify tissue enhancement, identify structural details like LV wall thickness, and detect potential arrhythmogenic substrate pathways via its 3D corridors module, thereby providing decision support for medical professionals.
Summary
ADAS 3D is a software-based image processing tool designed for the post-processing of cardiovascular Magnetic Resonance (MR) images and Computed Tomography Angiography (CTA) images from patients with cardiovascular disease, particularly those with myocardial scar. Its primary purpose is to support clinicians in the visualization and analysis of these images by processing DICOM image databases to enable the calculation, quantification, and 3D visualization of cardiac imaging data. The software focuses on displaying and quantifying levels of myocardial enhancement, visualizing the shape of cardiac chambers (Left Ventricle and Left Atrium) and adjacent anatomy, with the accuracy of its output directly dependent on the quality and resolution of the input medical images. Key functionalities of ADAS 3D include quantifying the total volume and distribution of enhancement in the LV and LA, calculating LV wall thickness from CTA images, and identifying other 3D anatomical structures. A notable feature is the "3D Corridors Module," which automatically detects and visualizes 3D corridors of border zone (BZ) tissue within the LV, defined as paths of intermediate MRI signal intensity connecting healthy tissue regions and bordered by core scar tissue. The software employs several algorithms for these tasks, including layer computation, enhancement quantification, 3D corridor detection, heart anatomy extraction, and wall thickness calculation. While ADAS 3D exports data for use in other systems, including Electrophysiology (EP) navigation systems, it is intended as a decision support tool for qualified medical professionals and not for direct patient management, catheter ablation guidance, or as the sole basis for diagnosis; the 3D corridor detection tool specifically has not been clinically validated for patient management.
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 is the typical processing time for a standard cardiac MR or CTA dataset using ADAS 3D, and how does image quality or dataset size impact this?; How does the "Enhancement Quantification algorithm" differentiate between core scar, border zone, and healthy tissue, and what are its reported sensitivity and specificity for myocardial scar characterization compared to established methods?; What specific "industry standard file formats supported by catheter navigation systems" can ADAS 3D export, and what level of detail is preserved in these exported 3D models?; Given the precaution that the "3D Corridor" detection tool has not been clinically validated for patient management, what were the findings from the non-clinical (synthetic/phantom) and any initial clinical data testing regarding its accuracy and reproducibility in identifying these corridors?; How does the ADAS 3D software handle variations in image acquisition protocols or scanner vendors for MR and CTA images, and are there specific sequence requirements for optimal performance of its quantification algorithms?
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