FDA-cleared profile

Libby Echo:Prio

Dyad Medical, Inc · Ultrasound · FDA-cleared (510(k))

Authorized purpose: Process previously acquired DICOM-compliant cardiac ultrasound images and estimate cardiac measurements to support qualified cardiologists, sonographers, or other licensed professional healthcare practitioners in clinical decision-making; indicated for adults.

Clinical role
Post-processing echocardiography review and quantification with machine-learning view classification, ED/ES frame identification, LV/LA/LV-myocardium segmentation, sonographer markup and correction, and physician review/reporting.
Images and patients
Ultrasound · Heart and cardiovascular structures, including LV chamber/endocardium, LA, and LV myocardium
Key limitation
Keep in mind: The workflow uses a skilled sonographer to provide markup and allows automated results to be accepted, partially modified, or rejected before physician review. The device is indicated for adults and supports clinical decision-making as an aid; the packet does not establish autonomous use, a general population beyond adult cardiac ultrasound, or current interface compatibility beyond the described DICOM/PACS or personal-computer configurations.

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: Process previously acquired DICOM-compliant cardiac ultrasound images and estimate cardiac measurements to support qualified cardiologists, sonographers, or other licensed professional healthcare practitioners in clinical decision-making; indicated for adults.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart and cardiovascular structures, including LV chamber/endocardium, LA, and LV myocardium Input: Previously acquired DICOM-compliant cardiac ultrasound images from adult patients, including the echocardiographic views supported by the software's view-classification and analysis functions.
  • Who uses it?Intended users: Qualified cardiologists, sonographers, or other licensed professional healthcare practitioners
  • What does the software produce?Output: 2D, cine-loop, and secondary-capture review; echocardiographic view classification; ED and ES frame identification with heartbeat-rate estimates; ejection fraction from LV endocardium, LA, and LV-myocardium segmentation; manually entered or corrected markup; and a generated summary report.
  • What is its most important limitation?Key limitation: The workflow uses a skilled sonographer to provide markup and allows automated results to be accepted, partially modified, or rejected before physician review. The device is indicated for adults and supports clinical decision-making as an aid; the packet does not establish autonomous use, a general population beyond adult cardiac ultrasound, or current interface compatibility beyond the described DICOM/PACS or personal-computer configurations.

Clinical takeaway. Clinical role: Process previously acquired DICOM-compliant cardiac ultrasound images and estimate cardiac measurements to support qualified cardiologists, sonographers, or other licensed professional healthcare practitioners in clinical decision-making; indicated for adults.

Evidence takeaway. Evidence from the reviewed source record: FDA performance testing was retrospective on a diverse clinical dataset; the packet does not state a sample size in the reviewed summary. View-classification accuracy was 97% with average F1 greater than 96.6%, average sensitivity 96.8%, and average specificity 98.5%. Heart-rate output had a linear-regression slope of 0.98 against 12-lead ECG, and EF prediction had a bivariate linear-regression slope of 0.79 with 95% CI 0.52-0.98 against annotations by four human experts. These are separate view-classification and measurement-agreement endpoints.

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
Process previously acquired DICOM-compliant cardiac ultrasound images and estimate cardiac measurements to support qualified cardiologists, sonographers, or other licensed professional healthcare practitioners in clinical decision-making; indicated for adults.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Post-processing echocardiography review and quantification with machine-learning view classification, ED/ES frame identification, LV/LA/LV-myocardium segmentation, sonographer markup and correction, and physician review/reporting.
  • Exact FDA submission
  • Checked 2026-09-08
Required input
Previously acquired DICOM-compliant cardiac ultrasound images from adult patients, including the echocardiographic views supported by the software's view-classification and analysis functions.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
2D, cine-loop, and secondary-capture review; echocardiographic view classification; ED and ES frame identification with heartbeat-rate estimates; ejection fraction from LV endocardium, LA, and LV-myocardium segmentation; manually entered or corrected markup; and a generated summary report.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Medical facility or routine echocardiography workflow using a personal computer or compatible DICOM PACS; adult use is a patient-population boundary, not the care-setting value.
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Qualified cardiologists, sonographers, or other licensed professional healthcare practitioners
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
The workflow uses a skilled sonographer to provide markup and allows automated results to be accepted, partially modified, or rejected before physician review. The device is indicated for adults and supports clinical decision-making as an aid; the packet does not establish autonomous use, a general population beyond adult cardiac ultrasound, or current interface compatibility beyond the described DICOM/PACS or personal-computer configurations.
  • Exact FDA submission
  • Checked 2026-09-08
Evidence summary
FDA performance testing was retrospective on a diverse clinical dataset; the packet does not state a sample size in the reviewed summary. View-classification accuracy was 97% with average F1 greater than 96.6%, average sensitivity 96.8%, and average specificity 98.5%. Heart-rate output had a linear-regression slope of 0.98 against 12-lead ECG, and EF prediction had a bivariate linear-regression slope of 0.79 with 95% CI 0.52-0.98 against annotations by four human experts. These are separate view-classification and measurement-agreement endpoints.
  • Exact FDA submission
  • Checked 2026-09-08

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
FDA performance testing was retrospective on a diverse clinical dataset; the packet does not state a sample size in the reviewed summary. View-classification accuracy was 97% with average F1 greater than 96.6%, average sensitivity 96.8%, and average specificity 98.5%. Heart-rate output had a linear-regression slope of 0.98 against 12-lead ECG, and EF prediction had a bivariate linear-regression slope of 0.79 with 95% CI 0.52-0.98 against annotations by four human experts. These are separate view-classification and measurement-agreement endpoints.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
View-classification sensitivity: 96.8%.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

FDA K220956 reports these as view-classification endpoints; ejection-fraction and heart-rate agreement are separate measurement endpoints.

Reported specificity
View-classification specificity: 98.5%.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

FDA K220956 reports these as view-classification endpoints; ejection-fraction and heart-rate agreement are separate measurement endpoints.

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

Libby Echo:Prio regulatory performance study summary

  • DesignStand-Alone Performance
  • PopulationAdult
  • Scopeexact submission
  • Tested versionExact product version not reported; regulatory study summarized for FDA submission K220956
  • IndependenceIndependence not established

K220956

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

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 K220956. 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: Previously acquired DICOM-compliant cardiac ultrasound images from adult patients, including the echocardiographic views supported by the software's view-classification and analysis functions.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K220956: Libby Echo:Prio

  2. Routing

    Source context, not route validation: The software processes DICOM-compliant cardiac ultrasound images and is described as operating on a personal computer or compatible DICOM PACS; a web-browser interface is also compared. Results are reported through a generated report, and exact interface versions, local compatibility, and current deployment topology are not established.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K220956: Libby Echo:Prio

  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: 2D, cine-loop, and secondary-capture review; echocardiographic view classification; ED and ES frame identification with heartbeat-rate estimates; ejection fraction from LV endocardium, LA, and LV-myocardium segmentation; manually entered or corrected markup; and a generated summary report.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K220956: Libby Echo:Prio

  5. Viewer/worklist/report

    Unresolved route: 2D, cine-loop, and secondary-capture review; echocardiographic view classification; ED and ES frame identification with heartbeat-rate estimates; ejection fraction from LV endocardium, LA, and LV-myocardium segmentation; manually entered or corrected markup; and a generated summary report.

    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-08 · FDA K220956: Libby Echo:Prio

  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 software processes DICOM-compliant cardiac ultrasound images and is described as operating on a personal computer or compatible DICOM PACS; a web-browser interface is also compared. Results are reported through a generated report, and exact interface versions, local compatibility, and current deployment topology are not established.
  • Exact FDA submission
  • Checked 2026-09-08

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for Libby Echo:Prio; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
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
K220956
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Heart and cardiovascular structures, including LV chamber/endocardium, LA, and LV myocardium
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-07-20
  • 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-20Last searched
24Fields reviewed
9Source 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 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 verified - checked 2026-09-08 - Exact FDA submission

    No public price or quote for the exact K220956 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 - 3 history items

Source ledger

  1. FDA K220956: Libby Echo:Prio

    U.S. Food and Drug Administration - Published 2022-07-20 - Accessed 2026-09-08

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. Libby Echo:Prio model card (K220956)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, reportedSensitivity, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  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. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K220956

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

    Scope: postmarketSafety

Research history

  1. K220956 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record 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