FlightPlan for Embolization
GE Medical Systems SCS • Radiology • 03/21/2023
Device Purpose
FlightPlan for Embolization is a medical image processing software that enhances the planning phase of embolization procedures by enabling physicians to analyze 3D X-ray angiography images. It employs both semi-automatic tools and newly introduced AI-powered deep-learning algorithms for automatic vasculature segmentation and root point definition, with its efficacy supported by non-clinical testing and clinical evaluation.
Summary
FlightPlan for Embolization is a post-processing software package designed to assist physicians in analyzing 3D X-ray angiography (CBCT) images for planning endovascular embolization procedures. Its primary function is to help visualize vasculature, providing outputs such as segmented vasculature and selective display of proximal and distal vessels from a user-defined reference point. While user-defined data can be exported for use during the guidance phase of a procedure, the software is intended for the planning phase only and not for therapy delivery; injection points must be confirmed independently. The system operates on GE HealthCare's Advantage Workstation (AW) and AW Server (AWS) platforms and is an extension to their Volume Viewer application. The key technological advancement in this version of FlightPlan for Embolization is the introduction of an 'AI Segmentation' option. This option incorporates two new deep-learning algorithms: one for automatic segmentation of vasculature and another for automatic definition of the root point. These AI-driven features are intended for the adult population. The algorithms were developed and qualified using contrast-injected CBCT scans from GE HealthCare's interventional X-ray system. Performance was evaluated using a segregated test set of 207 scans, demonstrating a 93.7% success rate for the vessel extraction algorithm and a 95.2% success rate for the root definition algorithm against pre-defined acceptance criteria. Clinical assessment by interventional radiologists further substantiated the utility of these AI features in procedure planning.
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 automatic segmentation compare to experienced human operators in terms of time efficiency and accuracy for complex or atypical vascular anatomies?; What were the specific criteria defining success for the 90% threshold in the vessel extraction and root definition algorithm testing, and how were these criteria clinically validated?; Are there plans to expand the validation of the AI Segmentation option beyond the adult population, for instance, to pediatric cases or specific challenging anatomies not heavily represented in the test set?; How does the system handle image artifacts or variations in CBCT acquisition protocols (beyond GE HealthCare systems), and what is the impact on the AI algorithms' reliability and accuracy?; What is the typical learning curve for clinicians to proficiently use the new AI Segmentation features, and how does it integrate with existing downstream applications like GEHC’s Vision Applications for 3D road-mapping?
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