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.
Clinical role
Qualitative and quantitative cardiac MR analysis after required contour confirmation.
Images and patients
MRI · Heart; left ventricular myocardium and cardiovascular structures
Key limitation
Keep in mind: A qualified user must confirm endocardial and epicardial contours in a reference phase; the measurements support comprehensive physician decision-making and do not replace it.
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: 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.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Heart; left ventricular myocardium and cardiovascular structures Input: Supported cine cardiovascular MR images and user-confirmed endocardial and epicardial contours.
Who uses it?Intended users: Qualified medical professionals experienced with cardiovascular MR.
What does the software produce?Output: Displacement, velocity, strain, strain-rate, time-to-peak, torsion, and related cardiac measurements.
What is its most important limitation?Key limitation: A qualified user must confirm endocardial and epicardial contours in a reference phase; the measurements support comprehensive physician decision-making and do not replace it.
Clinical takeaway. Clinical role: 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.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports verification and validation testing per the FDA quantitative imaging technical performance guidance, and validation of tracking and Global Longitudinal and Global Circumferential strains using simple and realistic phantoms, real MRI data and analytical solutions, including comparison of the tissue tracking algorithm with manual tracking in ES phase by three expert readers; no numeric results are reported. No clinical studies were necessary to support substantial equivalence. Results are as reported in the FDA submission, not independent validation.
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
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.
A qualified user must confirm endocardial and epicardial contours in a reference phase; the measurements support comprehensive physician decision-making and do not replace it.
The exact FDA document reports verification and validation testing per the FDA quantitative imaging technical performance guidance, and validation of tracking and Global Longitudinal and Global Circumferential strains using simple and realistic phantoms, real MRI data and analytical solutions, including comparison of the tissue tracking algorithm with manual tracking in ES phase by three expert readers; no numeric results are reported. No clinical studies were necessary to support substantial equivalence. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Verification and validation testing were conducted to ensure specifications and performance of the device and were performed per the FDA Guidance “Technical Performance Assessment of Quantitative Imaging in Radiological Device Premarket Submission”." … "The tracking performance and the clinically relevant Global Longitudinal and Global Circumferential strains were validated using a complimentary combination of simple and realistic phantoms, real MRI data, and analytical solutions.". Read from the exact FDA decision document on 2026-11-14.
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
The exact FDA document reports verification and validation testing per the FDA quantitative imaging technical performance guidance, and validation of tracking and Global Longitudinal and Global Circumferential strains using simple and realistic phantoms, real MRI data and analytical solutions, including comparison of the tissue tracking algorithm with manual tracking in ES phase by three expert readers; no numeric results are reported. No clinical studies were necessary to support substantial equivalence. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Verification and validation testing were conducted to ensure specifications and performance of the device and were performed per the FDA Guidance “Technical Performance Assessment of Quantitative Imaging in Radiological Device Premarket Submission”." … "The tracking performance and the clinically relevant Global Longitudinal and Global Circumferential strains were validated using a complimentary combination of simple and realistic phantoms, real MRI data, and analytical solutions.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, and source if later verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K232661 FDA evidence package for Myocardial Strain Software Application
DesignFDA 510(k) or PMA decision evidence and product verification described in the exact submission.
PopulationHeart; left ventricular myocardium and cardiovascular structures
Scopeexact submission
Tested versionMyocardial Strain Software Application configuration described in K232661
IndependenceSponsor or vendor study
K232661
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K232661 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
No separate named-product payment identified in reviewed public material
Centers for Medicare & Medicaid Services · United States
This is not a product-specific reimbursement determination. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage assumptions independently.
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: Supported cine cardiovascular MR images and user-confirmed endocardial and epicardial contours.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes supported DICOM cine cardiovascular MR images and user-confirmed contours.
Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact public FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Displacement, velocity, strain, strain-rate, time-to-peak, torsion, and related cardiac measurements.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Displacement, velocity, strain, strain-rate, time-to-peak, torsion, and related cardiac measurements.
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 FDA package describes supported DICOM cine cardiovascular MR images and user-confirmed contours.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only qualified medical professionals experienced with cardiovascular mr should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K232661 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: A qualified user must confirm endocardial and epicardial contours in a reference phase; the measurements support comprehensive physician decision-making and do not replace it.
Exact FDA submission
Checked 2026-09-04
Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. A qualified user must confirm endocardial and epicardial contours in a reference phase; the measurements support comprehensive physician decision-making and do not replace it.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
Monitor K232661 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: A qualified user must confirm endocardial and epicardial contours in a reference phase; the measurements support comprehensive physician decision-making and do not replace it.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. cardiovascular MR analysis software limits remain submission-specific.
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.
Human reviewedStatus
2026-09-20Last searched
27Fields reviewed
13Source 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 decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact public FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
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
Security: Not publicly available - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
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.
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.