FDA-cleared profile

LVivo Software Application

DiA Imaging Analysis Ltd · Ultrasound · FDA-cleared (510(k))

Authorized purpose: LVivo Software Application processes ultrasound clips and supports the labeled LVivo EF, SG, SAX, RV, and Bladder measurements and analyses, with user review and editing of supported studies.

Clinical role
Echocardiography classification, measurement, quantification, and reporting support.
Images and patients
Ultrasound · Cardiac structures, right and left ventricles, bladder, and other supported ultrasound anatomy
Key limitation
Keep in mind: Only the supported LVivo modules and ultrasound clips are in scope; user review and editing of measurements remain necessary.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: LVivo Software Application processes ultrasound clips and supports the labeled LVivo EF, SG, SAX, RV, and Bladder measurements and analyses, with user review and editing of supported studies.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Cardiac structures, right and left ventricles, bladder, and other supported ultrasound anatomy Input: Supported DICOM ultrasound images and B-mode, M-mode, pulsed-wave, or continuous-wave Doppler data.
  • Who uses it?Intended users: Licensed physicians and trained echocardiography professionals.
  • What does the software produce?Output: Verified measurements, calculations, annotations, and reports for physician review.
  • What is its most important limitation?Key limitation: Only the supported LVivo modules and ultrasound clips are in scope; user review and editing of measurements remain necessary.

Clinical takeaway. Clinical role: LVivo Software Application processes ultrasound clips and supports the labeled LVivo EF, SG, SAX, RV, and Bladder measurements and analyses, with user review and editing of supported studies.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports retrospective, single center clinical studies of LVivoRV and LVivo Bladder. LVivoRV output was compared with conventional echocardiography methods; the primary endpoint, FAC correlation with manual measurements, was r=0.79 (p<0.0001). LVivo Bladder was compared with manual measurements on 226 bladder images (113 pairs): at a 200ml threshold, Kappa was 0.84 with sensitivity and specificity of 100 and 80, and volume correlation with manual tracing was r=0.94. 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
LVivo Software Application processes ultrasound clips and supports the labeled LVivo EF, SG, SAX, RV, and Bladder measurements and analyses, with user review and editing of supported studies.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Echocardiography classification, measurement, quantification, and reporting support.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported DICOM ultrasound images and B-mode, M-mode, pulsed-wave, or continuous-wave Doppler data.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Verified measurements, calculations, annotations, and reports for physician review.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Adult echocardiography workflows in clinical imaging settings.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Licensed physicians and trained echocardiography professionals.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
Only the supported LVivo modules and ultrasound clips are in scope; user review and editing of measurements remain necessary.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports retrospective, single center clinical studies of LVivoRV and LVivo Bladder. LVivoRV output was compared with conventional echocardiography methods; the primary endpoint, FAC correlation with manual measurements, was r=0.79 (p<0.0001). LVivo Bladder was compared with manual measurements on 226 bladder images (113 pairs): at a 200ml threshold, Kappa was 0.84 with sensitivity and specificity of 100 and 80, and volume correlation with manual tracing was r=0.94. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "the LVivoRV output for RV function was compared with conventional methods that are used in echocardiography for RV function evaluation (2D manual measurements by technicians and when relevant to M-Mode, doppler and VVI). Study: Retrospective, single center study." … "The results showed that the primary end point was successfully met with a very good correlation of FAC between LVivoRV and manual measurements (r=0.79, p<0.0001).". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

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 retrospective, single center clinical studies of LVivoRV and LVivo Bladder. LVivoRV output was compared with conventional echocardiography methods; the primary endpoint, FAC correlation with manual measurements, was r=0.79 (p<0.0001). LVivo Bladder was compared with manual measurements on 226 bladder images (113 pairs): at a 200ml threshold, Kappa was 0.84 with sensitivity and specificity of 100 and 80, and volume correlation with manual tracing was r=0.94. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "the LVivoRV output for RV function was compared with conventional methods that are used in echocardiography for RV function evaluation (2D manual measurements by technicians and when relevant to M-Mode, doppler and VVI). Study: Retrospective, single center study." … "The results showed that the primary end point was successfully met with a very good correlation of FAC between LVivoRV and manual measurements (r=0.79, p<0.0001).". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

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.

K200232 FDA evidence package for LVivo Software Application

  • DesignFDA 510(k) or PMA decision evidence and product verification described in the exact submission.
  • PopulationCardiac structures, right and left ventricles, bladder, and other supported ultrasound anatomy
  • Scopeexact submission
  • Tested versionLVivo Software Application configuration described in K200232
  • IndependenceSponsor or vendor study

K200232

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.

Safety and lifecycle

Postmarket record

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 K200232 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.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
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.
  • Service-level, not product-specific
  • Checked 2026-09-04

No product-specific code

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 implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Supported DICOM ultrasound images and B-mode, M-mode, pulsed-wave, or continuous-wave Doppler data.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-04 · FDA 510(k) decision material K200232: LVivo Software Application

  2. Routing

    Source context, not route validation: The FDA package describes ultrasound clips, including DICOM clips from ultrasound systems, with user editing of supported measurements.

    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.

    Field checked 2026-09-04 · FDA 510(k) decision material K200232: LVivo Software Application

  3. AI processing

    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 ·

  4. Returned objects

    Source context, not route validation: Verified measurements, calculations, annotations, and reports for physician review.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA 510(k) decision material K200232: LVivo Software Application

  5. Viewer/worklist/report

    Unresolved route: Verified measurements, calculations, annotations, and reports for physician review.

    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.

    Field checked 2026-09-04 · FDA 510(k) decision material K200232: LVivo Software Application

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Integration
The FDA package describes ultrasound clips, including DICOM clips from ultrasound systems, with user editing of supported measurements.
  • 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.

Training
Only licensed physicians and trained echocardiography professionals should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor K200232 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: Only the supported LVivo modules and ultrasound clips are in scope; user review and editing of measurements remain necessary.
  • 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.

Release and scope verification

Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K200232 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared release includes them.

Deployment boundary

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.

Interoperability acceptance

The FDA package describes ultrasound clips, including DICOM clips from ultrasound systems, with user editing of supported measurements.

exact submission · checked 2026-09-04

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.

Clinical acceptance

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. Only the supported LVivo modules and ultrasound clips are in scope; user review and editing of measurements remain necessary.

exact submission · checked 2026-09-04

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

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.

Lifecycle monitoring

Monitor K200232 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: Only the supported LVivo modules and ultrasound clips are in scope; user review and editing of measurements remain necessary.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. echocardiography analysis software limits remain submission-specific.

Sources & review details FDA 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.

FDA submission
K200232
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Cardiac structures, right and left ventricles, bladder, and other supported ultrasound anatomy
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-06-23
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

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.

  • Installation timeline: Not yet reviewed

7 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K200232: LVivo Software Application

    U.S. Food and Drug Administration - Published 2020-06-23 - Accessed 2026-09-04

    Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. LVivo Software Application model card (K200232)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

Research history

  1. K200232 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K253535

Ligence Heart

Ligence Uab

Ligence Heart is a fully automated software platform that processes, analyses and makes measurements on acquired transthoracic cardiac ultrasound images, automatically producing a full report with measurements of several key cardiac structural and functional parameters. The data produced by this software is intended to be used to support qualified cardiologists or sonographers for clinical decision making. Ligence Heart is indicated for use in adult patients. Ligence Heart has not been validated for the assessment of congenital heart disease, valve disease, pericardial disease, and/or intra-cardiac lesions (e.g., tumors, thrombi). Limitations: Poor image capture will lead to poor annotations and subsequent measurements. Multiple image quality algorithms are used to filter out images of poor quality. Our software complements good patient care and does not exempt the user from the responsibility to provide supervision, clinically review the patient, and make appropriate clinical decisions. If no gender is present, female referenced guideline values will be used for conclusions. If Body Surface Area (BSA) is not present, indexed values cannot be provided. During image acquisition, inappropriate use of the echo machine, use of non-cardiac ultrasound probes, or use of suboptimal settings (e.g., gain, contrast, depth) may lead to lower accuracy of the software. Ligence Heart has not been validated in patients with prosthetic or surgically altered cardiac valves, implantable intracardiac devices, or irregular (non-sinus) rhythm; these conditions may affect automated measurement accuracy.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2026-02-27
FDA-cleared K252235

PVAD IQ Software

Ultrasight, Ltd.

Authorized purpose: PVAD IQ supports qualified-physician clinical decision support by identifying the aortic annulus and PVAD inlet, calculating their mean distance, and identifying clips acceptable for this measurement.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2025-12-18

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history