Authorized purpose: Quantification and reporting of cardiovascular function to support physician diagnosis in adult populations.
Clinical role
Sequential operator-assisted quantification: automatic view classification, operator confirmation or relabeling, left-ventricular contour approval, frame selection, metric calculation, and report review.
Images and patients
Ultrasound · Heart; cardiovascular function and left ventricle
Key limitation
Keep in mind: The operator must confirm or relabel views, approve contours and frame selection, and review the report and cautions; the packet establishes adult cardiovascular-function quantification and reporting, not an autonomous diagnosis or unreviewed measurement workflow.
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: Quantification and reporting of cardiovascular function to support physician diagnosis in adult populations.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart; cardiovascular function and left ventricle Input: DICOM echocardiogram clips from apical two-, three-, and four-chamber views, with heart-rate information or operator-supported selection when ECG is unavailable.
Who uses it?Intended users: Accredited echocardiographers and sonographers, with interpreting-physician review.
What does the software produce?Output: Secondary-capture DICOM files and/or a structured DICOM report containing left-ventricular length, ED/ES volume, ejection fraction, stroke volume, cardiac output, global and segmental longitudinal strain, indexed values, and related visualizations.
What is its most important limitation?Key limitation: The operator must confirm or relabel views, approve contours and frame selection, and review the report and cautions; the packet establishes adult cardiovascular-function quantification and reporting, not an autonomous diagnosis or unreviewed measurement workflow.
Clinical takeaway. Clinical role: Quantification and reporting of cardiovascular function to support physician diagnosis in adult populations.
Evidence takeaway. Evidence from the reviewed source record: A retrospective validation study used 214 previously unseen studies from multiple ultrasound manufacturers, with training and test data segregated. RMS error versus a comparator ranged from 3.06%-4.59% for LV length, 8.57%-16.59% for ED/ES volume, 6.69%-8.50% for ejection fraction, 10.57%-13.68% for stroke volume, 3.36%-4.79% for GLS, and 5.51%-9.98% for systolic segmental strain. Inter- and intra-operator Deming RMSE were reported as 0 for all report metrics. These are measurement-error and repeatability endpoints, not sensitivity or specificity.
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
Quantification and reporting of cardiovascular function to support physician diagnosis in adult populations.
DICOM echocardiogram clips from apical two-, three-, and four-chamber views, with heart-rate information or operator-supported selection when ECG is unavailable.
The operator must confirm or relabel views, approve contours and frame selection, and review the report and cautions; the packet establishes adult cardiovascular-function quantification and reporting, not an autonomous diagnosis or unreviewed measurement workflow.
A retrospective validation study used 214 previously unseen studies from multiple ultrasound manufacturers, with training and test data segregated. RMS error versus a comparator ranged from 3.06%-4.59% for LV length, 8.57%-16.59% for ED/ES volume, 6.69%-8.50% for ejection fraction, 10.57%-13.68% for stroke volume, 3.36%-4.79% for GLS, and 5.51%-9.98% for systolic segmental strain. Inter- and intra-operator Deming RMSE were reported as 0 for all report metrics. These are measurement-error and repeatability endpoints, not sensitivity or specificity.
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
A retrospective validation study used 214 previously unseen studies from multiple ultrasound manufacturers, with training and test data segregated. RMS error versus a comparator ranged from 3.06%-4.59% for LV length, 8.57%-16.59% for ED/ES volume, 6.69%-8.50% for ejection fraction, 10.57%-13.68% for stroke volume, 3.36%-4.79% for GLS, and 5.51%-9.98% for systolic segmental strain. Inter- and intra-operator Deming RMSE were reported as 0 for all report metrics. These are measurement-error and repeatability endpoints, not sensitivity or specificity.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
EchoGo Core (2.0) regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K213275
Samplen=214
IndependenceIndependence not established
K213275
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 K213275. 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: DICOM echocardiogram clips from apical two-, three-, and four-chamber views, with heart-rate information or operator-supported selection when ECG is unavailable.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The device operates on DICOM echocardiogram clips and produces secondary-capture and/or structured DICOM reports; exact PACS, RIS, EHR, interface, and version compatibility are not established.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
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-09 ·
Returned objects
Source context, not route validation: Secondary-capture DICOM files and/or a structured DICOM report containing left-ventricular length, ED/ES volume, ejection fraction, stroke volume, cardiac output, global and segmental longitudinal strain, indexed values, and related visualizations.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Secondary-capture DICOM files and/or a structured DICOM report containing left-ventricular length, ED/ES volume, ejection fraction, stroke volume, cardiac output, global and segmental longitudinal strain, indexed values, and related visualizations.
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.
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 device operates on DICOM echocardiogram clips and produces secondary-capture and/or structured DICOM reports; exact PACS, RIS, EHR, interface, and version compatibility are not established.
Ultromics announces it has received ISO 27001 certification for information security management, covering secure management of personal healthcare information and other data to the standard's requirements.
Vendor-wide
Checked 2026-10-27
Vendor statement (press release dated 2020-01-16); the certificate was not read. A SafeBase trust center exists at trust.ultromics.com. Applicant variants 'Ultromics Ltd' and 'Ultromics Limited' are the same distinctive name. Exact-release scope is not established.
ACR AI Central provides an exact-submission model card for EchoGo Core (2.0); 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
23Fields reviewed
9Source classes checked
0Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 0 PubMed and 1 ClinicalTrials.gov candidate record. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 0 PubMed and 1 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-09 - Exact FDA submission
No public price or quote for the exact K213275 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.
Deployment: Not verified - checked 2026-09-09 - 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
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.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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: Provides AI-assisted cardiac, lung and abdominal quality feedback and measurements; users remain responsible for scan quality and diagnosis and must not rely solely on the software.
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.