EFAI RTSuite CT HN-Segmentation System
Ever Fortune.AI Co., Ltd. • Radiology • 04/28/2022
Device Purpose
The EFAI RTSuite CT HN-Segmentation System aims to enhance efficiency in radiation therapy planning by providing automated initial contours of critical structures. It achieves this by employing deep learning algorithms to analyze non-contrast CT images of the head and neck region, segmenting organs-at-risk for subsequent review and modification by oncology professionals.
Summary
The EFAI RTSuite CT HN-Segmentation System (EFAI HNSeg v1.0) is a standalone software device designed to assist radiation oncology professionals by automatically delineating head-and-neck organs-at-risk (OARs) on non-contrast CT images. It employs deep-learning algorithms to process DICOM CT images and generate OAR contours in DICOM RTSTRUCT format, which are then intended for use in radiation therapy treatment planning workflows for adult patients. The system operates without a direct user interface, requiring integration with a DICOM-compliant treatment planning system where clinicians can review and edit the generated contours; it is explicitly positioned as an adjunct tool, not for primary diagnostic decisions or lesion detection, and clinician oversight is mandatory. The EFAI HNSeg system's technological characteristics were compared to the AccuContour™ device, sharing similarities in using deep learning for segmentation on non-contrast CT images and DICOM compliance, but differing in operating system, user interface (EFAI HNSeg has none), and scope of anatomical coverage (EFAI HNSeg is specific to head and neck OARs). Performance was evaluated through software verification and validation, including a non-inferiority standalone test against AccuContour™. This test compared the mean Dice coefficient of the automatically generated head and neck OAR contours, with results demonstrating that EFAI HNSeg was non-inferior to the predicate device within a clinically acceptable non-inferiority limit of 0.1 Dice.
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 deep learning architecture is employed by EFAI HNSeg, and how was its training dataset curated to ensure generalizability across diverse patient anatomies and image qualities?; The non-inferiority test used a Dice coefficient limit of 0.1; what were the mean Dice scores for individual head and neck OARs, and how do these compare to established inter-observer variability for manual delineation of these structures?; How does the EFAI HNSeg system address challenging cases, such as CT images with significant artifacts, post-operative changes, or highly variable patient anatomy, and are there specific contraindications or limitations for its use?; Given that EFAI HNSeg operates without a user interface and relies on integration with DICOM-compliant treatment planning systems, what are the specific technical requirements and recommended best practices for seamless workflow integration and ensuring data integrity during transfer?; Are there plans to evaluate the clinical impact of EFAI HNSeg on treatment planning efficiency, such as reduction in contouring time or improvement in consistency, compared to fully manual contouring workflows?
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