FDA-cleared profile

EchoMD Automated Ejection Fraction Software

Bay Labs, Inc. · Ultrasound · FDA-cleared (510(k))

Authorized purpose: Processes previously acquired transthoracic cardiac ultrasound images to estimate left-ventricular ejection fraction.

Clinical role
Processes previously acquired transthoracic cardiac ultrasound images, selects the image clips, estimates left ventricular ejection fraction, and forwards the percentage to a destination PACS for clinician viewing, to assist cardiac evaluation.
Images and patients
Ultrasound · Heart/Cardiovascular
Key limitation
Keep in mind: For adults and intended to assist cardiac evaluation; multiple tested platforms do not establish universal scanner compatibility.

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: Processes previously acquired transthoracic cardiac ultrasound images to estimate left-ventricular ejection fraction.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart/Cardiovascular Input: Previously acquired DICOM ultrasound clips, including apical four- and two-chamber views.
  • Who uses it?Intended users: Clinicians.
  • What does the software produce?Output: An ejection-fraction percentage sent to PACS plus qualitative and quantitative image-quality feedback.
  • What is its most important limitation?Key limitation: For adults and intended to assist cardiac evaluation; multiple tested platforms do not establish universal scanner compatibility.

Clinical takeaway. Clinical role: Processes previously acquired transthoracic cardiac ultrasound images to estimate left-ventricular ejection fraction.

Evidence takeaway. Evidence from the reviewed source record: Retrospective non-interventional study of over 300 studies using biplane reference; RMSD was 8.290% (p=0.00052).

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
Processes previously acquired transthoracic cardiac ultrasound images to estimate left-ventricular ejection fraction.
  • Exact FDA submission
  • Checked 2026-09-15

Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.

Workflow role
Processes previously acquired transthoracic cardiac ultrasound images, selects the image clips, estimates left ventricular ejection fraction, and forwards the percentage to a destination PACS for clinician viewing, to assist cardiac evaluation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "used to process previously acquired transthoracic cardiac ultrasound images, to store images, and to manipulate and make measurements on images using a personal computer or a compatible DICOM-compliant PACS system in order to provide automated estimation of left ventricular ejection fraction." … "The software selects the image clips to be used, performs the AutoEF calculation, and forwards the results to a destination PACS server for clinician viewing. The output of the program is the Ejection Fraction estimate stated as a percentage". Read from the exact FDA decision document on 2026-11-14.

Required input
Previously acquired DICOM ultrasound clips, including apical four- and two-chamber views.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet image-input scope.

Output and clinician action
An ejection-fraction percentage sent to PACS plus qualitative and quantitative image-quality feedback.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet output scope.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
Clinicians.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet intended-user statement.

Limitations
For adults and intended to assist cardiac evaluation; multiple tested platforms do not establish universal scanner compatibility.
  • Exact FDA submission
  • Checked 2026-09-15

Exact FDA limitation boundary.

Evidence summary
Retrospective non-interventional study of over 300 studies using biplane reference; RMSD was 8.290% (p=0.00052).
  • Exact FDA submission
  • Checked 2026-09-15

Submission-reported study result.

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
Retrospective non-interventional study of over 300 studies using biplane reference; RMSD was 8.290% (p=0.00052).
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

Submission-reported study result.

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.

EchoMD Automated Ejection Fraction Software regulatory performance study summary

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

K173780

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 K173780. 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-09
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 ultrasound clips, including apical four- and two-chamber views.

    Scope: Exact FDA submission. FDA packet image-input scope.

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

    Field checked 2026-09-15 · FDA K173780: EchoMD Automated Ejection Fraction Software

  2. Routing

    Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.

    Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

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

    Field checked 2026-09-01 · EchoMD Automated Ejection Fraction Software model card (K173780)

  3. AI processing

    Source context, not route validation: The exact FDA package describes EchoMD AutoEF operating as a microservice background function running as part of a PACS system, with ultrasound systems and PACS workstation systems providing the user interface. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "EchoMD AutoEF operates as a microservice background function communicating with ultrasound systems and PACS workstation systems, which provide the user interface." … "Other minor differences arise due to the design of the EchoMD running as part of a PACS system, rather than as a fully stand-alone application like the predicate.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

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

    Field checked 2026-11-14 · FDA K173780: EchoMD Automated Ejection Fraction Software

  4. Returned objects

    Source context, not route validation: An ejection-fraction percentage sent to PACS plus qualitative and quantitative image-quality feedback.

    Scope: Exact FDA submission. FDA packet output scope.

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

    Field checked 2026-09-15 · FDA K173780: EchoMD Automated Ejection Fraction Software

  5. Viewer/worklist/report

    Unresolved route: An ejection-fraction percentage sent to PACS plus qualitative and quantitative image-quality feedback.

    Scope: Exact FDA submission. FDA packet output scope.

    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-15 · FDA K173780: EchoMD Automated Ejection Fraction Software

  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

Deployment
The exact FDA package describes EchoMD AutoEF operating as a microservice background function running as part of a PACS system, with ultrasound systems and PACS workstation systems providing the user interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "EchoMD AutoEF operates as a microservice background function communicating with ultrasound systems and PACS workstation systems, which provide the user interface." … "Other minor differences arise due to the design of the EchoMD running as part of a PACS system, rather than as a fully stand-alone application like the predicate.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-09-01

Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

Security
GE HealthCare's Product Security Portal is described as a credentialed global portal giving customers security updates, vulnerability status and required actions for GE HealthCare products potentially impacted by critical vulnerabilities, plus historical patch views; GE HealthCare references its Cybersecurity Risk Management System and publishes a Coordinated Vulnerability Disclosure Statement for reporting vulnerabilities in GE HealthCare products.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. Identity bridge: Caption Health's own press page states Bay Labs renamed to Caption Health (2019), and GE HealthCare's own press release announces the acquisition of Caption Health, Inc.; Caption AI is sold as a GE HealthCare product. Corporate program statement; portal content is credentialed; exact-release scope is not established.

Monitoring
GE HealthCare's product security page states that it provides a credentialed Product Security Portal offering security updates, vulnerability status and actions, and patch views for GE HealthCare products under its Cybersecurity Risk Management System, and links its Coordinated Vulnerability Disclosure Statement.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. The page names GE HealthCare generally and does not scope these commitments to any specific product release; exact-release scope is not established. Portal access is credentialed; contents were not read.

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.

Result destination

PACS is explicitly referenced as a result destination.

exact submission · checked 2026-09-01

Confirm supported products, versions, routing behavior, and display requirements during local evaluation.

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for EchoMD Automated Ejection Fraction Software; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
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
K173780
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet transthoracic echocardiography scope.

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

FDA packet covers the heart and left ventricle.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2018-06-14
  • 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
25Fields reviewed
10Source 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, 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.

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

    No public price or quote for the exact K173780 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-09 - 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.

  • 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
  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-09 - Exact FDA submission

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

8 sources - 3 history items

Source ledger

  1. FDA K173780: EchoMD Automated Ejection Fraction Software

    U.S. Food and Drug Administration - Published 2018-06-14 - Accessed 2026-09-09

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

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. EchoMD Automated Ejection Fraction Software model card (K173780)

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

    Scope: intendedUsers, careSetting, output, limitations, 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 K173780

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

    Scope: postmarketSafety

  8. GE HealthCare: Product Security (portal and Cybersecurity Risk Management System)

    GE HealthCare - Accessed 2026-10-26

    Scope: security

Research history

  1. K173780 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 K260780

HeartFocus

Deski

Authorized purpose: Guides medical professionals acquiring ten standard 2D transthoracic echocardiographic views in adults requiring a cardiac ultrasound examination; acquired images require qualified clinical interpretation.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2026-06-03
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