DV. Target
Deepvoxel INC • Radiology • 04/02/2021
Device Purpose
DV.Target is a machine learning-based software application designed to automatically delineate organs-at-risk on CT images, providing critical input for radiation therapy treatment planning. Its methodology relies on processing DICOM-compliant data through deep learning algorithms to generate OAR contours, which are then managed via an administration interface and reviewed in a separate Treatment Planning System, with performance validated through non-inferiority to existing solutions using DICE scores.
Summary
DV.Target is a standalone software application designed for trained medical professionals to assist in radiation therapy treatment planning. Its primary function is to automatically delineate organs-at-risk (OARs) on CT images. The system processes DICOM-compliant CT image data through machine learning-based algorithms to generate these OAR contours. DV.Target operates without a direct user interface for image visualization; instead, users manage image uploads, auto-contouring processes, and output files (in RTSTRUCT format) via an administration interface. It is specifically intended for contouring normal organs and not for delineating tumors or clinical target volumes, requiring integration with a Treatment Planning System (TPS) or similar software for the review, editing, and approval of all generated contours. The core science behind DV.Target involves deep learning processing for its auto-contouring capabilities, necessitating installation on a specialized server. The software can delineate a total of 49 OARs across three anatomical regions: Head & Neck, Thorax, and Abdomen & Pelvis. Non-clinical performance was evaluated through three comparison studies against a predicate device (Mirada Workflow Box) and a reference device (MIM – MRT Dosimetry). These studies utilized both public (TCIA) and in-house clinical datasets, with ground truth established by physician consensus or actual clinical contours. Using the Dice-Sørensen coefficient (DICE score) as the primary metric, DV.Target demonstrated non-inferior auto-contouring accuracy for 19 OARs shared with the predicate device and for 30 additional OARs compared to the reference device, confirming its performance capabilities.
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 DV.Target's machine learning algorithms for OAR delineation vary across different CT scanner manufacturers and imaging protocols, beyond the DICOM compliance requirement?; What specific machine learning model architectures are employed in DV.Target, and how were they trained and validated to ensure generalizability across diverse patient populations and anatomical variations for the 49 specified OARs?; Given that DV.Target requires a separate TPS for contour review and editing, what is the typical quantitative and qualitative impact on dosimetrist/physicist workload and contouring efficiency compared to manual delineation or other auto-segmentation tools?; The non-clinical testing showed non-inferiority based on DICE scores. Are there data on other clinically relevant metrics, such as Hausdorff distance or mean surface distance, particularly for OARs with complex geometries or those in close proximity to target volumes?; How does DV.Target handle challenging cases, such as images with significant artifacts, post-operative anatomy, or unusual patient positioning, and what are the documented failure modes or limitations of the auto-contouring algorithms in such scenarios?
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, SaaSBOM 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, 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