LVivo Seamless
DiA Imaging Analysis Ltd • Radiology • 09/29/2020
Device Purpose
LVivo Seamless is a specialized software application designed to automate the non-invasive analysis of cardiac ultrasound images, specifically for quantifying left ventricular Ejection Fraction. Its methodology involves offline processing of DICOM echo clips on a server, using its LVivo EF module to automatically select relevant frames, calculate EF via Simpson's method, and measure Global Longitudinal Strain, with results sent to PACS for clinical review.
Summary
LVivo Seamless, developed by DiA Imaging Analysis Ltd., is a standalone software application designed for the automated analysis of cardiac ultrasound (echocardiography) examinations. It operates offline on a server within a healthcare environment, accepting DICOM-formatted echo studies from ultrasound machines. The system's primary purpose is to automatically select appropriate cardiac image loops (clips) and then utilize its integrated LVivo EF module to perform an automated evaluation of left ventricular Ejection Fraction (EF). The processed results, including EF values, are then transmitted to a Picture Archiving and Communication System (PACS) for review and interpretation by healthcare professionals in the context of patients with suspected cardiac disease. The core methodology of LVivo Seamless for EF calculation relies on the automated identification of end-diastolic (ED) and end-systolic (ES) frames and subsequent left ventricular volume calculation using the standard Simpson's method of discs. A key characteristic of LVivo Seamless is its full automation post-clip selection, as it does not permit manual adjustments or editing of the ventricular contours by the user. While focused on EF, the system also provides Global Longitudinal Strain (GLS) measurement. However, it does not support segmental longitudinal strain, segmental wall motion evaluation, or volume curve presentation. The device is designed to work with DICOM clips from any vendor and includes automated rejection of false results, presenting EF for default cardiac beats.
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. What is the typical processing time for an individual patient study from DICOM ingestion to EF result availability in PACS using LVivo Seamless?; How does the "automated rejection of false results" feature function, and what are its performance metrics (sensitivity/specificity for rejecting poor quality studies or inaccurate analyses)?; Given the removal of manual adjustment capabilities, what validation studies were performed to ensure the accuracy and robustness of the fully automated EF and GLS calculations across diverse patient populations and image qualities?; How does the automated clip selection algorithm identify "adequate clips" for EF evaluation, and what criteria does it use?; What is the specific algorithm or method used by the LVivo EF module within Seamless to calculate Global Longitudinal Strain, especially in the absence of segmental strain analysis capabilities?
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, SaaSBOM, OBOM 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. 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