VisAble.IO
TechsoMed • Radiology • 08/28/2023
Device Purpose
VisAble.IO is a CT image processing software designed to assist physicians in planning and confirming liver ablation procedures by providing tools for anatomic segmentation, virtual needle placement, and quantitative analysis of ablation zones. It employs AI algorithms for liver and vessel segmentation and a structured workflow to enhance the precision and evaluation of liver ablation treatments, though final clinical accuracy relies on user judgment.
Summary
VisAble.IO is a user-controlled software application designed for processing Computed Tomography (CT) images specifically for liver ablation procedures. It facilitates the import of images from CT scanners and PACS systems, allowing physicians to utilize these images for both planning and confirmation stages of liver ablation. Its core purpose is to assist in identifying ablation targets, planning virtual needle placements, and subsequently confirming the achieved ablation zones post-procedure, though it is explicitly not intended for diagnostic purposes or predicting treatment outcomes. The software operates through a five-step workflow: data import, anatomic structures segmentation (including liver, vessels, and target), instrument placement planning, ablation zone segmentation, and treatment confirmation involving image registration and quantitative analysis. Key functionalities include manual and AI-driven automated segmentation tools, virtual instrument overlay, image fusion, and the computation of achieved margins and missed volumes to evaluate target coverage. VisAble.IO supports specific Medtronic and NeuWave Medical needle models for planning and utilizes AI algorithms for key segmentation tasks; validation studies demonstrated a mean DICE score of 0.98 for liver segmentation (goal 0.92), 0.80 for ablation target segmentation (goal 0.70), 0.86 for ablation zone segmentation (goal 0.70), 0.72 for liver vessel segmentation (goal 0.70), and a mean corresponding distance of 4.11 mm for pre-post ablation image registration (goal 6.06 mm).
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-driven liver and vessel segmentation algorithms (e.g., DICE scores) compare to manual segmentation by experienced radiologists in terms of time efficiency and accuracy for complex cases?; What are the specific limitations of the software when dealing with CT images of varying quality or from different CT scanner manufacturers, beyond general image resolution dependencies?; Can the system's quantitative analysis of 'achieved margins' and 'missed volumes' be correlated with long-term patient outcomes or recurrence rates in liver ablation?; How does the 'automated local rigid registration' handle significant anatomical changes or deformations between pre- and post-ablation scans, and what is the typical extent of user modification required?; Given the software supports specific needle models for planning, how adaptable is it to new or different ablation needle technologies, and what is the process for incorporating them?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class C (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