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