LVivo IQS
DiA Imaging Analysis Ltd • Radiology • 02/01/2023
Device Purpose
The LVivo IQS is an advanced software module that processes cardiac ultrasound images to provide real-time quality feedback for left ventricular views, aiming to improve the consistency and utility of echocardiographic examinations. Its underlying algorithmic approach, validated through studies showing strong agreement with expert assessments and high clinical interpretability of acquired images, supports its use in detecting, measuring, and calculating key medical parameters for patients with suspected heart disease, particularly in point-of-care settings.
Summary
LVivo IQS is a software algorithm and Application Programming Interface (API) module developed by DiA Imaging Analysis Ltd., designed as an extension to their existing LVivo Software Application. Its primary purpose is the non-invasive processing of ultrasound images to detect, measure, and calculate relevant medical parameters of cardiac structures and function for patients with suspected heart disease. A key innovation of LVivo IQS is its ability to provide real-time "Quality Score" feedback specifically for the left ventricle as imaged from the 4-chamber apical view, and it can be integrated as a component into other legally marketed ultrasound imaging devices. The performance of LVivo IQS was validated through two main evaluations. The first study compared the software's quality scoring against manual quality tagging by experienced sonographers using a dataset of 100 patient examinations (22,663 frames), achieving an 81% overall agreement, surpassing the 75% success criterion. The second study assessed its real-time utility when used by point-of-care (POC) interns scanning 64 patients; results showed that in 90% of cases with initially adequate visual image quality (3-5 by ACEP guidelines), a "Medium" or higher quality score was achieved using LVivo IQS, and 93% of these acquired clips were deemed clinically interpretable by expert echocardiologists.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the LVivo IQS "Quality Score" quantitatively correlate with established echocardiographic image quality metrics beyond subjective sonographer assessment and general interpretability?; What was the range of performance (agreement and interpretability rates) of LVivo IQS across different ultrasound machine manufacturers and patient populations with varying cardiac pathologies in the validation studies?; Can the LVivo IQS algorithm provide specific actionable feedback to the operator (e.g., "adjust probe angle," "apply more gel") to improve image quality, or is the feedback limited to a general quality score?; How does the integration of LVivo IQS into third-party ultrasound devices impact the overall workflow and examination time in a typical clinical or point-of-care setting?; Are there comparative studies demonstrating a measurable improvement in diagnostic accuracy or efficiency when point-of-care users utilize LVivo IQS feedback versus traditional unassisted scanning?
Risk Classification
ESL AnalysisFDA 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.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
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 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, SaaSBOM, 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