TeraRecon Neuro

K220349

TeraRecon, Inc · cleared 2022-08-12 · product code LLZ · Radiology

Premarket evidence — what FDA accepted

Device typesamd

source quote (p.3)

“The TeraRecon Neuro Algorithm is a standalone image processing software device that can be deployed as a Microsoft Windows executable on off-the-shelf hardware or as a containerized application (e.g., a Docker container) that runs on off-the-shelf hardware or on a cloud platform.”

AlgorithmBrain perfusion analysis algorithm that provides analysis capabilities for functional, dynamic, and derived imaging datasets acquired with CT or MRI, showing properties of changes in contrast over time. It includes calculation of parameters related to brain tissue perfusion, vascular assessment, tissue blood volume, and other parametric maps, as well as volume reformat, rotational MIP 3D batch, and 'tumble view' for qualitative review of vascular structure.

source quote (p.3)

“The TeraRecon Neuro Algorithm provides analysis capabilities for functional, dynamic, and derived imaging datasets acquired with CT or MRI. It can be used for the analysis of dynamic brain perfusion image data, showing properties of changes in contrast over time. This functionality includes calculation of parameters related to brain tissue perfusion, vascular assessment, tissue blood volume, and other parametric maps with or without the ventricles included in the calculation. The algorithm also include volume reformat in various orientation, rotational MIP 3D batch while removing the skull. This "tumble view" allows qualitative review of vascular structure in direct correlation to the perfusion maps for comprehensive review.”

Adaptive (vs locked)No

PCCPFDA source did not state this

Cybersecurity addressedFDA source did not state this

Validation studies (2)

Reader study (MRMC)

sample size not stated

endpoints: qualitative assessment that the generated maps of TeraRecon Neuro are at least 85% substantially equivalent or better than the predicate and reference devices

standards: IEC 62304:2006/AI:2015, ISO 14971:2007

Retrospective clinical

sample size not stated

endpoints: absolute error for Tmax measurements; absolute percent error for Tmax measurements; subject device limit of agreement for both metrics less than or equal than the limit of agreement of each predicate device compared to the ground truth

standards: IEC 62304:2006/AI:2015, ISO 14971:2007

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