FDA-cleared profile

LVivo Software Application

DIACARDIO, LTD. · Ultrasound · FDA-cleared (510(k))

Non-invasive processing of previously acquired echocardiographic images to detect and measure the left-ventricular wall and calculate left-ventricular function.

Clinical role
Fully automated processing of already acquired echocardiographic DICOM movies that detects and measures the left ventricular wall to evaluate global ejection fraction and strain; the measurements assist the clinician in a cardiac evaluation.
Images and patients
Ultrasound · Heart/Cardiovascular
Key limitation
Not publicly available

Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial 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

  • Imaging and anatomyUltrasound · Heart/Cardiovascular
  • Workflow roleFully automated processing of already acquired echocardiographic DICOM movies that detects and measures the left ventricular wall to evaluate global ejection fraction and strain; the measurements assist the clinician in a cardiac evaluation.
  • Required inputalready acquired echocardiographic images
  • Output and human actiondetect, measure, and calculate the left ventricular wall for left ventricular function evaluation

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
Non-invasive processing of previously acquired echocardiographic images to detect and measure the left-ventricular wall and calculate left-ventricular function.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Fully automated processing of already acquired echocardiographic DICOM movies that detects and measures the left ventricular wall to evaluate global ejection fraction and strain; the measurements assist the clinician in a cardiac evaluation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "LVivo Software Application is intended for non-invasive processing of already acquired echocardiographic images in order to detect, measure, and calculate the left ventricular wall for left ventricular function evaluation. This measurement can be used to assist the clinician in a cardiac evaluation." … "The LVivo System analyzes echocardiographic patient examination DICOM movies for Global ejection fraction (EF) evaluation. EF is evaluated using two orthogonal planes, four-chamber (4CH) and two-chamber (2CH) views, to provide fully automated analyses of LV function from the echo examination movies.". Read from the exact FDA decision document on 2026-11-14.

Required input
already acquired echocardiographic images
  • Exact FDA submission
  • Checked 2026-09-19

The packet identifies already acquired echocardiographic images as the processed input.

Output and clinician action
detect, measure, and calculate the left ventricular wall for left ventricular function evaluation
  • Exact FDA submission
  • Checked 2026-09-19

The packet states the device processing and measurement result in this wording.

Intended users
the clinician
  • Exact FDA submission
  • Checked 2026-09-19

The packet states that the measurement can be used to assist the clinician in a cardiac evaluation; it does not state a more specific user class.

Evidence summary
In the blinded clinical trial, ultrasound clips of 100 subjects were evaluated with the LVivo System. The primary end point defined for this study was met with a correlation coefficient calculated for biplane EF (r=0.88, p<0001).
  • Exact FDA submission
  • Checked 2026-09-19

The replacement is limited to the packet's stated clinical-test population and reported primary endpoint.

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
In the blinded clinical trial, ultrasound clips of 100 subjects were evaluated with the LVivo System. The primary end point defined for this study was met with a correlation coefficient calculated for biplane EF (r=0.88, p<0001).
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

The replacement is limited to the packet's stated clinical-test population and reported primary endpoint.

Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

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 exact-identifier FDA recall query returned no native recall record for K161382. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

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: already acquired echocardiographic images

    Scope: Exact FDA submission. The packet identifies already acquired echocardiographic images as the processed input.

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

    Field checked 2026-09-19 · FDA K161382: LVivo Software Application

  2. Routing

    Source context, not route validation: The exact FDA package describes LVivo analyzing echocardiographic patient examination DICOM movies, with offline ejection fraction evaluation using DICOM clips of any vendor listed for the subject device. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "The LVivo System analyzes echocardiographic patient examination DICOM movies for Global ejection fraction (EF) evaluation." … "Off line EF evaluation YES YES YES using DICOM clips of any vendor". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-11-14 · FDA K161382: LVivo Software Application

  3. AI processing

    Unresolved route: Not established for the exact route.

    Scope: Exact FDA submission. The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-08 ·

  4. Returned objects

    Source context, not route validation: detect, measure, and calculate the left ventricular wall for left ventricular function evaluation

    Scope: Exact FDA submission. The packet states the device processing and measurement result in this wording.

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

    Field checked 2026-09-19 · FDA K161382: LVivo Software Application

  5. Viewer/worklist/report

    Unresolved route: detect, measure, and calculate the left ventricular wall for left ventricular function evaluation

    Scope: Exact FDA submission. The packet states the device processing and measurement result in this wording.

    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-19 · FDA K161382: 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 exact FDA package describes LVivo analyzing echocardiographic patient examination DICOM movies, with offline ejection fraction evaluation using DICOM clips of any vendor listed for the subject device. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The LVivo System analyzes echocardiographic patient examination DICOM movies for Global ejection fraction (EF) evaluation." … "Off line EF evaluation YES YES YES using DICOM clips of any vendor". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Current product-family workflow context

GE HealthCare's LVivo EF support material describes automated left-ventricular border tracing and EF, EDV, and ESV calculation from an apical four-chamber ultrasound view.

product family · checked 2026-09-08

Confirm exact-release availability, interfaces, hosting, security, support, and commercial terms during procurement.

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
K161382
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Anatomy
Heart/Cardiovascular
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2016-07-28
  • 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.

Exact FDA record reviewedStatus
2026-09-19Last searched
19Fields reviewed
10Source classes checked
0Awaiting review PubMed leads
0Awaiting review trial leads
0Unreviewed FDA recall leads

Recovered from the prior exact-submission extraction and normalized under the current provenance rules. Exact FDA support assessed on 2026-09-19. Packet-supported facts: purpose, modality, anatomy; packet-unavailable facts: intendedUsers, input, output, limitations, evidenceSummary. Candidate literature and postmarket candidates remain in their existing review state. Automated exact-name discovery found 0 PubMed and 0 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads remain unpublished until a human confirms the exact product and tested version.

Source classes: fda ai list, fda decision summary, vendor product page, fda device recall, literature index, trial registry, fda decision summary packet, 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.

  • Care setting: Not publicly available - checked 2026-11-14 - Exact FDA submission

    The exact FDA decision document was reviewed on 2026-11-14 and does not state a care setting or patient population for the subject device. Confirm intended sites and patients with the vendor and local policy.

  • Limitations: Not publicly available - checked 2026-11-14 - Exact FDA submission

    The exact FDA decision document was reviewed on 2026-11-14 and states no use limitation for the subject device beyond its indication. Confirm contraindications and labeled limits in the current labeling.

  • Public pricing: Not verified - checked 2026-09-08 - Exact FDA submission

    No public price or quote for the exact K161382 configuration was established in this review.

  • 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
  • Reimbursement: Not publicly available - checked 2026-09-08 - Exact FDA submission

    No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.

  • Deployment: Not verified - checked 2026-09-08 - Exact FDA submission

    The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.

  • 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 verified - checked 2026-09-08 - Exact FDA submission

    Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.

  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-08 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

  • Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission

    Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

7 sources - 2 history items

Source ledger

  1. FDA K161382: LVivo Software Application

    U.S. Food and Drug Administration - Published 2016-07-28 - Accessed 2026-09-19

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, evidenceSummary, integration

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

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

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

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

    Scope: evidenceDiscovery, studyStatus

  5. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  6. LVivo EF App support article

    GE HealthCare - Accessed 2026-09-07

    Scope: product_family, clinical_workflow, outputs, limitations

  7. openFDA exact recall query for K161382

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

    Scope: postmarketSafety

Research history

  1. K161382 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

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