ADAS 3D

K191125

Galgo Medical S.L · cleared 2020-01-15 · product code LLZ · Radiology

Premarket evidence — what FDA accepted

Device typesamd

source quote (p.4)

“ADAS 3D is a software-based image processing tool for post-processing cardiovascular enhanced Magnetic Resonance (MRI) images and Computed Tomography Angiography (CTA) images.”

AlgorithmThe software includes algorithms for Left Ventricle Layer Computation, Left Atrium Layer Computation, Enhancement Quantification, 3D Corridor Detection, Heart Anatomy Extraction, From Binary image to surface mesh, and Left Ventricle Wall Thickness. The 3D Corridors Module is an automatic detection feature designed to help identify and visualize 3D corridors of border zone (BZ) tissue within the LV. The 3D Corridors algorithm generates visual representations of the corridors that may travel through multiple layers of the LV.

source quote (p.5)

“-Left Ventricle Layer Computation-Left Atrium Layer Computation Algorithm-Enhancement Quantification algorithm-3D Corridor Detection Algorithm-Heart Anatomy Extraction algorithm-From Binary image to surface mesh algorithm-Left Ventricle Wall Thickness algorithm. The 3D Corridors Module is an automatic detection feature designed to help identify and visualize 3D corridors of border zone (BZ) tissue within the LV. The 3D Corridors algorithm generates visual representations of the corridors that may travel through multiple layers of the LV.”

Adaptive (vs locked)FDA source did not state this

PCCPFDA source did not state this

Cybersecurity addressedFDA source did not state this

Validation studies (1)

Bench

sample size not stated

standards: Guidance for the Submission of Premarket Notifications for Medical Imaging Management Devices, Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices., Guidance for Off-The-Shelf Software Use in Medical Devices - September 9, 1999, General Principles of Software Validation; Final Guidance for Industry and FDA Staff – January 11, 2002., Design Considerations and Pre-market Submission Recommendations for Interoperable Medical Devices – September 6, 2017, ISO 14971, ISO 62304

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

recalls in product code, 24mo

295

MAUDE reports in code, 12mo

+683%

vs code's own 3-yr baseline

drift signals on this device

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).