AI4CMR v2.0

K252084

Ai4medimaging Medical Solutions S.A. · cleared 2026-02-11 · product code QIH · Radiology

Premarket evidence — what FDA accepted

Device typesamd
source quote (p.6)
AI4CMR v2.0 is a cloud-based solution designed to integrate to any third-party DICOM viewer application where the DICOM viewer serves as the user interface and the interface to a PACS or scanner for AI4CMR.
AlgorithmConvolutional Neural Network (U-Net architecture)
source quote (p.10)
Model Category: Convolutional Neural Network (U-Net architecture)
Adaptive (vs locked)No
source quote (p.10)
The model is “locked,” meaning it does not adapt or change with new input data.
PCCPFDA source did not state this
Cybersecurity addressedFDA source did not state this

Validation studies (2)

Standalone

n=167 cases · 1 site(s)

endpoints: Dice Similarity Coefficient (DSC)

standards: IEC 62304:2006+A1:2015

Bench

sample size not stated

endpoints: Total Forward Volume (TFV); Total Backward Volume (TBV); Maximum Velocity (Vmax)

standards: IEC 62304:2006+A1:2015

Reported performance (6 observations)

diceas written: “Dice Similarity Coefficient (DSC) for ascending aorta0.952
source quote (p.11)
the model achieved DSC values of 0.952 for the ascending aorta
diceas written: “Dice Similarity Coefficient (DSC) for descending aorta0.957
source quote (p.11)
0.957 for the descending aorta
diceas written: “Dice Similarity Coefficient (DSC) for pulmonary artery0.952
source quote (p.11)
and 0.952 for the pulmonary artery
agreement_kappaas written: “Total Forward Volume (TFV) ICC0.95
source quote (p.11)
Total Forward Volume (TFV): ICC 0.95
agreement_kappaas written: “Total Backward Volume (TBV) ICC0.82
source quote (p.11)
Total Backward Volume (TBV): ICC 0.82
agreement_kappaas written: “Maximum Velocity (Vmax) ICC0.95
source quote (p.11)
Maximum Velocity (Vmax): ICC 0.95

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

0
recalls in product code, 24mo
3
MAUDE reports in code, 12mo
vs code's own 3-yr baseline
0
drift signals on this device

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

RIGOR™ Precedent · public FDA/CMS data · descriptive decision-support, not regulatory or reimbursement advice. Share this page: radar.healthai.com/precedent/device/K252084