Authorized purpose: Automatic segmentation and reporting of cardiac function measurements from 1.5T and 3T MR images to support clinical decision-making; results are not intended for standalone clinical decision-making.
Clinical role
Post-processing cardiac MR segmentation and quantification through a plug-in to a third-party DICOM viewer, with results made available to the user for review and reporting.
Images and patients
MRI · Heart, including left and right ventricles, myocardium, and cardiac chambers
Key limitation
Keep in mind: Results are not for standalone clinical decision-making, and the user is responsible for implementing the DICOM viewer user interface. Indices derived from height and weight are available only when those values are included in the DICOM data. The FDA evidence uses small bench and retrospective MRMC datasets across specified 1.5T/3T scanners and establishes measurement agreement and segmentation endpoints rather than autonomous diagnosis.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: Automatic segmentation and reporting of cardiac function measurements from 1.5T and 3T MR images to support clinical decision-making; results are not intended for standalone clinical decision-making.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Heart, including left and right ventricles, myocardium, and cardiac chambers Input: Cardiac MR images from 1.5T and 3T scanners, including multi-slice MR data received through a DICOM viewer that provides the user interface and connection to a PACS or scanner.
Who uses it?Intended users: The user incorporating AI4CMR into a DICOM application of choice
What does the software produce?Output: Anatomical and tissue segmentation; LV/RV stroke volume, cardiac output, ejection fraction, end-diastolic volume, end-systolic volume, and myocardial mass; derived indices when required patient height and weight are present in DICOM; and report or DICOM Secondary Capture outputs.
What is its most important limitation?Key limitation: Results are not for standalone clinical decision-making, and the user is responsible for implementing the DICOM viewer user interface. Indices derived from height and weight are available only when those values are included in the DICOM data. The FDA evidence uses small bench and retrospective MRMC datasets across specified 1.5T/3T scanners and establishes measurement agreement and segmentation endpoints rather than autonomous diagnosis.
Clinical takeaway. Clinical role: Automatic segmentation and reporting of cardiac function measurements from 1.5T and 3T MR images to support clinical decision-making; results are not intended for standalone clinical decision-making.
Evidence takeaway. Evidence from the reviewed source record: FDA bench testing used 15 CMR cases annotated by seven independent expert readers across 1.5T and 3T Siemens, GE, and Philips scanners; average myocardium segmentation Dice similarity coefficient was 0.72. Reported measurement agreement included LV EF bias 3.87 (SD 5.74), LV ICC 0.96; RV EF bias 7.80 (7.32), RV ICC 0.81; LV EDV bias 8.66 (17.28), LV ICC 0.99; RV EDV bias 8.36 (15.59), RV ICC 0.96; LV ESV bias -2.90 (17.52), LV ICC 0.99; RV ESV bias -9.08 (13.83), RV ICC 0.95; and LV myocardial-mass bias 2.45 (18.04), ICC 0.96. The retrospective MRMC clinical performance assessment used 146 CMR cases and two expert readers to evaluate agreement with manual segmentation and measurements; the reviewed text does not provide a single diagnostic sensitivity or specificity result.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
Automatic segmentation and reporting of cardiac function measurements from 1.5T and 3T MR images to support clinical decision-making; results are not intended for standalone clinical decision-making.
Post-processing cardiac MR segmentation and quantification through a plug-in to a third-party DICOM viewer, with results made available to the user for review and reporting.
Cardiac MR images from 1.5T and 3T scanners, including multi-slice MR data received through a DICOM viewer that provides the user interface and connection to a PACS or scanner.
Anatomical and tissue segmentation; LV/RV stroke volume, cardiac output, ejection fraction, end-diastolic volume, end-systolic volume, and myocardial mass; derived indices when required patient height and weight are present in DICOM; and report or DICOM Secondary Capture outputs.
Results are not for standalone clinical decision-making, and the user is responsible for implementing the DICOM viewer user interface. Indices derived from height and weight are available only when those values are included in the DICOM data. The FDA evidence uses small bench and retrospective MRMC datasets across specified 1.5T/3T scanners and establishes measurement agreement and segmentation endpoints rather than autonomous diagnosis.
FDA bench testing used 15 CMR cases annotated by seven independent expert readers across 1.5T and 3T Siemens, GE, and Philips scanners; average myocardium segmentation Dice similarity coefficient was 0.72. Reported measurement agreement included LV EF bias 3.87 (SD 5.74), LV ICC 0.96; RV EF bias 7.80 (7.32), RV ICC 0.81; LV EDV bias 8.66 (17.28), LV ICC 0.99; RV EDV bias 8.36 (15.59), RV ICC 0.96; LV ESV bias -2.90 (17.52), LV ICC 0.99; RV ESV bias -9.08 (13.83), RV ICC 0.95; and LV myocardial-mass bias 2.45 (18.04), ICC 0.96. The retrospective MRMC clinical performance assessment used 146 CMR cases and two expert readers to evaluate agreement with manual segmentation and measurements; the reviewed text does not provide a single diagnostic sensitivity or specificity result.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
FDA bench testing used 15 CMR cases annotated by seven independent expert readers across 1.5T and 3T Siemens, GE, and Philips scanners; average myocardium segmentation Dice similarity coefficient was 0.72. Reported measurement agreement included LV EF bias 3.87 (SD 5.74), LV ICC 0.96; RV EF bias 7.80 (7.32), RV ICC 0.81; LV EDV bias 8.66 (17.28), LV ICC 0.99; RV EDV bias 8.36 (15.59), RV ICC 0.96; LV ESV bias -2.90 (17.52), LV ICC 0.99; RV ESV bias -9.08 (13.83), RV ICC 0.95; and LV myocardial-mass bias 2.45 (18.04), ICC 0.96. The retrospective MRMC clinical performance assessment used 146 CMR cases and two expert readers to evaluate agreement with manual segmentation and measurements; the reviewed text does not provide a single diagnostic sensitivity or specificity result.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
AI4CMR v1.0 regulatory performance study summary
DesignStand-alone performance and reader study (ACR AI Central category)
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K220624
Samplen=15
IndependenceIndependence not established
K220624
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K220624. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: Cardiac MR images from 1.5T and 3T scanners, including multi-slice MR data received through a DICOM viewer that provides the user interface and connection to a PACS or scanner.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: AI4CMR is described as a cloud-hosted service implemented as a plug-in to any third-party DICOM viewer; the viewer serves as the user interface and the interface to a PACS or scanner. DICOM input and report/DICOM Secondary Capture output are described, but specific PACS, RIS, EHR, interface versions, and current local compatibility are not established.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes AI4CMR v1.0 as a cloud-hosted service implemented by the user as a plug-in to a third-party DICOM viewer, which serves as its user interface and its interface to a PACS or scanner. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "AI4CMR v1.0 is a cloud-hosted service used with 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." … "AI4CMR is implemented as a plug-in to the DICOM viewer by the user". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Anatomical and tissue segmentation; LV/RV stroke volume, cardiac output, ejection fraction, end-diastolic volume, end-systolic volume, and myocardial mass; derived indices when required patient height and weight are present in DICOM; and report or DICOM Secondary Capture outputs.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Anatomical and tissue segmentation; LV/RV stroke volume, cardiac output, ejection fraction, end-diastolic volume, end-systolic volume, and myocardial mass; derived indices when required patient height and weight are present in DICOM; and report or DICOM Secondary Capture outputs.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
The exact FDA package describes AI4CMR v1.0 as a cloud-hosted service implemented by the user as a plug-in to a third-party DICOM viewer, which serves as its user interface and its interface to a PACS or scanner. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "AI4CMR v1.0 is a cloud-hosted service used with 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." … "AI4CMR is implemented as a plug-in to the DICOM viewer by the user". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
AI4CMR is described as a cloud-hosted service implemented as a plug-in to any third-party DICOM viewer; the viewer serves as the user interface and the interface to a PACS or scanner. DICOM input and report/DICOM Secondary Capture output are described, but specific PACS, RIS, EHR, interface versions, and current local compatibility are not established.
AI4CMR's security & compliance page states that AI4CMR operates cloud sites in multiple global regions so that data remains within the appropriate jurisdiction in compliance with GDPR and local data-protection regulations, and maintains cloud-based disaster recovery systems to preserve availability and data integrity.
Product family
Checked 2026-10-27
Vendor statement, not an attestation. The page names the AI4CMR product without distinguishing v1.0 (K220624) from v2.0 (K252084); exact-release scope is not established. The page's listed QMS/regulatory standards (ISO 13485, ISO 14971, IEC 62304, MDR, 21 CFR 820) are not treated as security evidence; no certificate or report was read.
ACR AI Central provides an exact-submission model card for AI4CMR v1.0; FDA labeling remains controlling for clinical use, limitations, and performance.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Exact FDA record reviewedStatus
2026-09-20Last searched
22Fields reviewed
9Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, acr ai central product, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not verified - checked 2026-09-08 - Exact FDA submission
No public price or quote for the exact K220624 configuration was established in this review.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Reimbursement: Not publicly available - checked 2026-09-08 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Myomics assists qualified medical professionals with viewing, post-processing and qualitative/quantitative evaluation of 3T cardiovascular MR images in DICOM format, including heart and adjacent-vessel measurements; semi-automated machine-learning workflows are intended for adults and contribute to comprehensive diagnostic decision-making.
Authorized purpose: Provide cardiac-chamber segmentations for trained healthcare professionals reviewing adult cardiac MR to assist diagnosis or treatment planning; the physician makes final patient-management decisions.
Modality
MRI
Anatomy
Cardiac chambers: left-ventricular myocardium and chamber, and right-ventricular chamber for the Cine-ax component; left-ventricular myocardium and chamber for the De-ax component.
Authorized purpose: Myocardial Strain Software Application provides qualitative and quantitative evaluation of cardiovascular MR images, including two-dimensional displacement, velocity, strain, strain rate, time to peak, and torsion after a qualified user confirms the contours.
Modality
MRI
Anatomy
Heart; left ventricular myocardium and cardiovascular structures
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.