Medscape Medical NewsAll articles

Myocardial Strain Software Application

Circle Cardiovascular Imaging • Radiology • 12/07/2023

510(k)IEC 62304 Class B
FDA Summary PDF

Device Purpose

The Myocardial Strain Software Application is designed for qualified medical professionals to perform qualitative and quantitative evaluation of cardiovascular MR images, providing measurements of 2D LV myocardial function to aid in diagnosing suspected heart disease. The software employs a feature tracking algorithm based on a 2D nearly incompressible deformable model, initiated by user-defined myocardial contours, to compute parameters like strain, displacement, and velocity from SSFP cine CMR images.

Summary

The Myocardial Strain Software Application, also known as the Strain Module, is a medical image processing system developed by Circle Cardiovascular Imaging. It is intended for the qualitative and quantitative analysis of cardiovascular magnetic resonance (CMR) images, specifically those acquired using SSFP cine imaging. The software assists qualified medical professionals in evaluating 2D left ventricular (LV) myocardial function by providing a suite of measurements such as displacement, velocity, strain (including Global Longitudinal Strain and Global Circumferential Strain), strain rate, time to peak, and torsion. These measurements are used to obtain diagnostic information for patients with suspected heart disease, serving as an aid to the existing standard of care and not replacing other diagnostic tools. The results can be visualized on-screen, saved for later review, and the module can be integrated into broader cardiac image viewing platforms. The core methodology of the Strain Module relies on CMR feature tracking. Users initiate the process by confirming endocardial and epicardial contours in a reference phase of the cardiac cycle. The software then utilizes a 2D nearly incompressible deformable model algorithm to track these features throughout the cardiac cycle, with deformation determined by control points on the myocardial wall that are detected based on feature-tracked boundaries and an incompressibility constraint. This process is purely mathematical and does not involve artificial intelligence or machine learning. The device's performance and output validation were conducted using a combination of analytical phantoms, realistic phantoms with known deformations, real MRI data, and comparison against manual tracking by expert readers, ensuring compliance with relevant ISO standards and FDA guidance for quantitative imaging.

AI Regulatory Concerns

Powered byJev by TypeSafe AI

Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.

Keywords

Myocardial StrainCardiovascular MR (CMR)Feature TrackingDeformation Analysis2D LV FunctionGlobal Longitudinal Strain (GLS)Global Circumferential Strain (GCS)Quantitative ImagingDICOMImage Processing Software

Device Metadata

Submission Number
K232661
Company
Circle Cardiovascular Imaging
Panel
Radiology
Product Code
N/A
Data Type
Images
Clinical Function
Assessment
AI Function
Analysis
AI Subclass
quantification/feature localization

Relevant Clinical Questions

  • Q1. How does the performance of the 2D nearly incompressible deformable model compare to other strain analysis algorithms (e.g., speckle tracking echocardiography or other CMR-based techniques) in terms of accuracy and reproducibility across different patient populations and image qualities?; What is the sensitivity and specificity of the derived strain parameters (GLS, GCS) using this software for detecting specific cardiac pathologies, and are there established cut-off values for these parameters based on studies using this specific module?; The validation involved phantoms and real MRI data; could you elaborate on the characteristics of the 'real MRI data' patient cohort (e.g., healthy volunteers, specific pathologies) and the inter-observer variability of contour placement affecting the strain results?; While the software is vendor-independent for CMR acquisition, are there any known impacts of varying acquisition parameters (e.g., temporal resolution, spatial resolution, slice thickness) on the accuracy of the strain measurements?; Given the module's reliance on user-defined contours in a reference phase, what is the learning curve for new users to achieve consistent and accurate contouring, and does the software offer any tools to guide or validate user inputs?

Risk Classification

ESL Analysis
FDA Device ClassII

FDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Authorized before §524B enforcement

Learn how Parasoft automates IEC 62304 compliance testing →

Cybersecurity Evidence

Powered by SBOMator™

Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.

Cyber Score10/100
SBOM Evidence⚠ Not mentioned in summary
Cyber Risk Assessment⚠ Not mentioned in summary
Postmarket Plan⚠ Not mentioned in summary
§524B ApplicableNo

Supply Chain BOM Evidence

Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.

SBOMSoftware Bill of Materials
- Not detected
ML-BOMMachine Learning Bill of Materials(machine learning, algorithm)
✓ Detected
SaaSBOMSoftware-as-a-Service Bill of Materials(server, platform)
✓ Detected
HBOMHardware Bill of Materials
- Not detected
CBOMCryptography Bill of Materials
- Not detected
VDR/VEXVulnerability Disclosure Report / Vulnerability Exploitability eXchange
- Not detected
OBOMOperations Bill of Materials
- Not detected

Analysis:

• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.

• Evidence of ML-BOM, SaaSBOM detected in AI-generated device summary.

• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.

• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.

• Not detected in AI-generated device summary: SBOM, HBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.

Preparing a similar submission?

ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.

Assess Your Readiness →Or contact ESL directly
Myocardial Strain Software Application - Circle Cardiovascular Imaging | ESL FDA AI Device Intelligence