Limbus Contour
Limbus AI Inc. • Radiology • 10/09/2024
Device Purpose
Limbus Contour is a software medical device designed to automate the contouring of CT and MRI DICOM images to support radiation treatment planning for trained oncology professionals. It achieves this by employing an automated segmentation methodology, validated through rigorous benchtop testing comparing its outputs to expert-created contours using the Dice Similarity Coefficient, consistently meeting performance requirements with good geometric alignment.
Summary
Limbus Contour is a stand-alone software medical device designed for the automatic contouring (segmentation) of CT and MRI DICOM images. Intended for use by trained radiation oncologists, dosimetrists, and physicists, the software aims to derive optimal contours essential for radiation treatment planning. It facilitates the creation, transformation, and modification of contours, seamlessly integrating with existing radiotherapy treatment planning systems and DICOM image viewers by importing image files and exporting segmented RT-Structure Set files. This software assists in localizing and defining anatomical structures for treatment evaluation and planning, but it is not intended for use with digital mammography.The device has been found substantially equivalent to a previously marketed version of the Limbus Contour software. While maintaining identical indications for use and a similar software-only design, the current version expands the range of anatomical structures available for automatic contouring and has a slightly increased RAM requirement. Performance was validated through rigorous software verification and benchtop testing, where contours generated by the software were compared to expert-created contours using the Dice Similarity Coefficient. The results demonstrated that the device's outputs consistently meet specified requirements and exhibit good geometric alignment, requiring minimal editing, thus confirming its comparable performance to the predicate.
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 specific clinical impact of the "minimal editing" required for the automatically generated contours on treatment planning efficiency and accuracy?; How does the expanded range of anatomical structures in the new version compare in accuracy and reliability to the structures available in the predicate device?; Are there any specific types of image artifacts or patient anatomies that Limbus Contour performs less optimally with, and how are these handled or mitigated?; What are the long-term data on the clinical outcomes of patients whose treatment plans utilized contours generated by Limbus Contour?; Beyond Dice Similarity Coefficient, what other metrics or clinical endpoints were used to validate the performance and equivalence of the software, particularly concerning dosimetric impact?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class C (software safety classification); Post-§524B but no clear network capability detected
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.
• SBOM not mentioned in AI-generated device summary. Under §524B (effective Oct 2023), cyber devices must provide a SBOM.
• Cybersecurity risk assessment not referenced in AI-generated device summary. FDA cybersecurity guidance (2023) expects this for cyber devices.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, ML-BOM, 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