Brainomix 360 e-CTA
K242123Brainomix Limited · cleared 2025-01-06 · product code LLZ · Radiology
Premarket evidence — what FDA accepted
source quote (p.4)
“Brainomix 360 e-CTA is an image processing software package to be used by trained professionals, including, but not limited to physicians and medical technicians. The software runs on standard "off the-shelf" hardware (physical or virtualized) and can be used to perform image viewing, processing, and analysis of images. Data and images are acquired through DICOM compliant imaging devices.”
source quote (p.6)
“Brainomix 360 e-CTA processes the images using AI/ML algorithms where the input channels will help the software distinguish bone from vessels and reduce image grain.”
source quote (p.10)
“Brainomix 360 e-CTA has been designed and validated to the FDA Cybersecurity Guidance and IEC 81001-5-1.”
Validation studies (2)
Bench
n=18 other
endpoints: vessel density ratio value; Mean Absolute Error (MAE)
Retrospective clinical
n=308 patients · 2 site(s)
endpoints: Dice Similarity Score (DSC) for Vessels; Dice Similarity Score (DSC) for Parenchyma
Reported performance (2 observations)
source quote (p.8)
“Vessels DSC 0.955 (0.953, 0.957)”
source quote (p.8)
“Parenchyma DSC 0.999 (0.999, 1.000)”
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
- 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 (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 is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:99042
- 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 (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 is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98428
- 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
- recall_reason_pattern
Software/algorithm-related recall in product code LLZ (DICOM Grid, Inc., initiated 2025-11-18): "Software intended to aid in diagnosing conditions, planning treatments, visualizing anatomical structures has a bug that, if all of following are met: Viewing images in InteleShare" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:97993
- …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).