Advanced Algorithms for Treatment Management Applications (AATMA)
Elekta Solutions AB • Radiology • 10/25/2021
Device Purpose
AATMA™ is a medical image processing library that leverages machine-learning convolutional neural networks via an API to perform auto-segmentation of 3D CT images for radiation therapy planning. Its core function is to produce derived datasets for treatment planning systems, with its efficacy demonstrated through validated performance of Head & Neck and Male Pelvis models, necessitating review by qualified healthcare professionals before clinical application.
Summary
Advanced Algorithms for Treatment Management Applications (AATMA™) is a medical image processing library designed to generate derived datasets for radiation therapy treatment planning systems and other pre-treatment planning applications. It functions as an accessory, utilizing machine-learning convolutional neural networks for the auto-segmentation of medical images, and includes pre-trained models specific to body sites and imaging modalities. AATMA™ operates as a computational engine without storing data or logs, lacks a user interface, and is accessed via an Application Programming Interface (API), requiring external software for the review and editing of automatically generated contours. All datasets produced by AATMA™ must be reviewed and validated by a qualified healthcare professional prior to clinical use. Performance of AATMA™ was evaluated through non-clinical software verification and validation, specifically for two pre-trained models utilizing 3D CT image sets: Head & Neck and Male Pelvis. The Head & Neck model, trained on 66 image sets, achieved an average DICE coefficient of 0.84 during verification with 6 different patient CTs and passed validation with 13 additional image sets. The Male Pelvis model, trained on 205 image sets, demonstrated an average DICE coefficient of 0.93 in verification using 5 patient CTs and also met validation criteria with 20 further image sets, confirming its ability to meet user needs for auto-segmentation.
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 specific anatomical structures are the Head & Neck and Male Pelvis models trained to segment, and what is the variability in performance (e.g., DICE coefficient) across these different structures within each model?; How does the performance of AATMA™, particularly segmentation accuracy and processing time, vary when applied to CT images from different scanner manufacturers or with diverse acquisition parameters not included in the training/validation sets?; What are the mechanisms or recommended best practices for clinical sites to validate AATMA™'s pre-trained models with their local patient data and imaging protocols before routine clinical use?; Given that AATMA™ is an API-driven library, what are the detailed computational requirements (e.g., GPU specifications, memory, processing cores) for integrating and optimally running the auto-segmentation algorithms within various existing treatment planning systems?; Are there plans to expand the AATMA™ library with pre-trained models for other anatomical regions, different imaging modalities (e.g., MRI, PET-CT), or to address specific pathological conditions beyond standard anatomical segmentation?
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 SBOM, 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: 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