ACR exact-submission catalog context
ACR AI Central provides an exact-submission model card for Ligence Heart; FDA labeling remains controlling for clinical use, limitations, and performance.
exact submission · checked 2026-09-08FDA-cleared profile
Ligence Uab · Ultrasound · FDA-cleared (510(k))
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.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Evidence context not reviewed for this FDA record.
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.
The available FDA packet is a clearance letter without usable indication detail; this wording comes from the exact-submission ACR model card and does not replace FDA labeling.
Conservative normalization of explicit wording in an exact-submission source.
Conservative normalization of explicit wording in an exact-submission source.
Clinical output reported in the exact-submission ACR model card.
Intended-user text reported in the exact-submission ACR model card.
Limitations and supported-acquisition details reported in the exact-submission ACR model card.
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.
The exact FDA decision document was reviewed on 2026-11-14 and reports no performance testing results for the subject device. Request the vendor's validation evidence.
This field has not been curated yet.
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
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Price not public here; enter your quote
Not verified: Pricing information is recorded but not verified against a resolving source.
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.
Source context, not route validation: Ultrasound images or data involving Heart/Cardiovascular; consult the FDA labeling for exact protocol, series, and quality requirements.
Scope: Exact FDA submission. Conservative normalization of explicit wording in an exact-submission source.
Confirm scanner/model, protocol, series completeness and both software builds.
Field checked 2026-08-31 · FDA K253535: Ligence Heart
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision document was reviewed on 2026-11-14 and does not state the subject device's DICOM, PACS, RIS, or EHR interfaces. Confirm supported DICOM services and PACS, RIS, EHR, and interface versions with the vendor.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-11-14 ·
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 ·
Source context, not route validation: The software automatically produces a full report with measurements of several key cardiac structural and functional parameters from transthoracic cardiac ultrasound images, intended to support clinical decision making by cardiologists or sonographers.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Field checked 2026-09-01 · Ligence Heart model card (K253535)
Unresolved route: The software automatically produces a full report with measurements of several key cardiac structural and functional parameters from transthoracic cardiac ultrasound images, intended to support clinical decision making by cardiologists or sonographers.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
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-01 · Ligence Heart model card (K253535)
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
ACR AI Central provides an exact-submission model card for Ligence Heart; FDA labeling remains controlling for clinical use, limitations, and performance.
exact submission · checked 2026-09-08Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
Anatomy normalized from explicit exact-submission ACR model-card wording.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA scope controls clinical claims. ACR provides bounded exact-submission catalog context. Candidate literature metadata remains a discovery queue until full-text identity, endpoint, population, and version review is completed. 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, acr ai central product, fda decision summary, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall
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.
The exact FDA decision document was reviewed on 2026-11-14 and reports no performance testing results for the subject device. Request the vendor's validation evidence.
No public price or quote for the exact K253535 configuration was established in this review.
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
The exact FDA decision document was reviewed on 2026-11-14 and does not state the subject device's DICOM, PACS, RIS, or EHR interfaces. Confirm supported DICOM services and PACS, RIS, EHR, and interface versions with the vendor.
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
7 sources - 2 history items
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation
Scope: regulatoryIdentity, modalityContext
Scope: intendedUsers, careSetting, output, limitations, anatomy
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: postmarketSafety
Regulatory record
510(k)
Research record
fda record reviewed
Alternatives
eko.ai Pte. Ltd. d/b/a Us2.ai
Authorized purpose: Us2.v1 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 licensed primary care providers for clinical decision-making. Us2.v1 is indicated for use in adult patients. Us2.v1 has not been validated for the assessment of congenital heart disease, valve disease, pericardial disease, and/or intra-cardiac lesions (e.g. tumors, thrombi). Please note the following 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, use of suboptimal settings (e.g. gain, contrast, depth), or lack of electrocardiogram capture may lead to lower accuracy of the 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.
Mycardium AI Limited
Authorized purpose: Transthoracic echocardiography view classification, cardiac structure segmentation, functional measurements and Doppler review and report support.
DiA Imaging Analysis Ltd.
Authorized purpose: Automated echocardiographic LV and RV function, wall-motion and strain, bladder-volume and image-quality measurements for clinician review.
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 destinationPermission 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.
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