FlightPlan for Embolization
K223490GE Medical Systems SCS · cleared 2023-03-21 · product code LLZ · Radiology
Premarket evidence — what FDA accepted
source quote (p.4)
“FlightPlan for Embolization is a post-processing, software-only application using 3D X-ray angiography images (CBCT) as input.”
source quote (p.6)
“The AI Segmentation option enabling both automatic segmentation of vasculature and automatic definition of the root point is based on two new algorithms: Deep-Learning based automatic vessels extraction algorithm and Deep-Learning based root definition algorithm.”
Validation studies (2)
Bench
n=207 scans
endpoints: success rate is 93.7% with acceptance criterion 90%; success rate is 95.2% with acceptance criterion 90%
standards: NEMA PS 3.1 - 3.20 Digital Imaging and Communications in Medicine (DICOM) Set (Radiology) standard, 21CFR 820, ISO 13485
Reader study (MRMC)
sample size not stated
endpoints: met its pre-defined acceptance criteria and helps physicians in their analysis of 3D X-ray angiography images and in the planning of embolization procedures, including the selection of embolization injection points
Reported performance (0 observations)
FDA source did not state a quantitative performance metric — non-reporting is itself the signal.
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (GE Medical Systems SCS, initiated 2026-05-08): "GE HealthCare has become aware of a context synchronization issue in AW Server 3.2 ext. 6.5. When a user selects a patient or exam in the AW Server Web Client worklist and launches" Recalling firm matches this device's applicant.
first seen 2026-07-08 · recall res_event_number:99042
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (GE Medical Systems, LLC, initiated 2026-01-30): "There is a potential cybersecurity vulnerability affecting certain versions of Centricity Universal Viewer. User login credentials may be exposed on the local client workstation, w" Recalling firm matches this device's applicant.
first seen 2026-07-08 · recall res_event_number:98428
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (GE Medical Systems, SCS, initiated 2025-09-05): "Firm has identified a security vulnerability in AW Server products. If exploited, a malicious actor could compromise the confidentiality, integrity, and availability of patient dat" Recalling firm matches this device's applicant.
first seen 2026-07-08 · recall res_event_number:97657
- adverse_event_inflection
MAUDE adverse-event reports for product code LLZ: 295 in the 12 months ending 2026-06, vs a 37.7/12mo average over the prior 3 windows (+683%). Code-level count — reports are not attributed to this specific device.
first seen 2026-07-08 · openFDA /device/event.json count=date_received product_code=LLZ
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (PHILIPS MEDICAL SYSTEMS NEDERLAND B.V. Veenpluis 4-6 Best Netherlands, initiated 2026-03-05): "Potential that mis-ordered frames in Vue Motion during dynamic cine runs may cause images frames to display out of sequence." Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98520
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (Focalyx Technologies, LLC., initiated 2025-12-23): "Software device that is an accessory for image-guided interventional and diagnostic procedures involving prostate has accessories that may not function properly with Windows 10, wh" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98137
- …and 20 more.
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).