Authorized purpose: Semi-automated measurement of left ventricular ejection fraction during cardiac ultrasound.
Clinical role
Assistive real-time/semi-automatic EF measurement during cardiac ultrasound, with clinician adjustment and final responsibility.
Images and patients
Ultrasound · Heart, specifically the left ventricle
Key limitation
Keep in mind: Adults only; not stand-alone software and limited to the listed Clarius scanner/app ecosystem and cleared transducers. Inadequate-quality images, incomplete anatomy/views, or failure to generate a measurement were excluded from the measurement comparison. The FDA packet also describes a PCCP for future scanner/input and algorithm changes, with data-skew and concept-drift risks requiring verification.
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: Semi-automated measurement of left ventricular ejection fraction during cardiac ultrasound.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart, specifically the left ventricle Input: Ultrasound image data acquired by Clarius phased-array or curvilinear scanners, including PLAX, PSAX, AP4, and AP2 views; the algorithm automatically captures ED/ES frames and is integrated into the Clarius App on iOS/Android.
Who uses it?Intended users: Healthcare professionals trained and qualified in ultrasound.
What does the software produce?Output: Semi-automatic LV EF measurement using Simpson single-plane/apical, fractional area change/PSAX, and Teicholz/PLAX methods; segmentation masks or landmark markers identify the LV, ED/ES frames are captured, and the user can manually adjust caliper measurements.
What is its most important limitation?Key limitation: Adults only; not stand-alone software and limited to the listed Clarius scanner/app ecosystem and cleared transducers. Inadequate-quality images, incomplete anatomy/views, or failure to generate a measurement were excluded from the measurement comparison. The FDA packet also describes a PCCP for future scanner/input and algorithm changes, with data-skew and concept-drift risks requiring verification.
Clinical takeaway. Clinical role: Semi-automated measurement of left ventricular ejection fraction during cardiac ultrasound.
Evidence takeaway. Evidence from the reviewed source record: FDA packet: retrospective clinical verification of 279 exams from a multi-center anonymized dataset, with three expert reviewers and separate clinical design validation in simulated use. The verification excluded inadequate/incomplete images and subjects for which the model failed to generate a measurement; it was a measurement comparison without follow-up clinical examination.
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
Semi-automated measurement of left ventricular ejection fraction during cardiac ultrasound.
Ultrasound image data acquired by Clarius phased-array or curvilinear scanners, including PLAX, PSAX, AP4, and AP2 views; the algorithm automatically captures ED/ES frames and is integrated into the Clarius App on iOS/Android.
Semi-automatic LV EF measurement using Simpson single-plane/apical, fractional area change/PSAX, and Teicholz/PLAX methods; segmentation masks or landmark markers identify the LV, ED/ES frames are captured, and the user can manually adjust caliper measurements.
Adults only; not stand-alone software and limited to the listed Clarius scanner/app ecosystem and cleared transducers. Inadequate-quality images, incomplete anatomy/views, or failure to generate a measurement were excluded from the measurement comparison. The FDA packet also describes a PCCP for future scanner/input and algorithm changes, with data-skew and concept-drift risks requiring verification.
FDA packet: retrospective clinical verification of 279 exams from a multi-center anonymized dataset, with three expert reviewers and separate clinical design validation in simulated use. The verification excluded inadequate/incomplete images and subjects for which the model failed to generate a measurement; it was a measurement comparison without follow-up clinical examination.
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 packet: retrospective clinical verification of 279 exams from a multi-center anonymized dataset, with three expert reviewers and separate clinical design validation in simulated use. The verification excluded inadequate/incomplete images and subjects for which the model failed to generate a measurement; it was a measurement comparison without follow-up clinical examination.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Clarius Ejection Fraction AI regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K253593
Samplen=270
IndependenceIndependence not established
K253593
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 K253593. 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: Ultrasound image data acquired by Clarius phased-array or curvilinear scanners, including PLAX, PSAX, AP4, and AP2 views; the algorithm automatically captures ED/ES frames and is integrated into the Clarius App on iOS/Android.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Integrated into the Clarius App and complete Clarius Ultrasound Scanner system, not a stand-alone device; compatible iOS/Android app versions and PA HD3, PAL HD3, and C3 HD3 transducers are listed in the packet. Generic DICOM/PACS integration is not established for the subject device.
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-08 ·
Returned objects
Source context, not route validation: Semi-automatic LV EF measurement using Simpson single-plane/apical, fractional area change/PSAX, and Teicholz/PLAX methods; segmentation masks or landmark markers identify the LV, ED/ES frames are captured, and the user can manually adjust caliper measurements.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Semi-automatic LV EF measurement using Simpson single-plane/apical, fractional area change/PSAX, and Teicholz/PLAX methods; segmentation masks or landmark markers identify the LV, ED/ES frames are captured, and the user can manually adjust caliper measurements.
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.
Integrated into the Clarius App and complete Clarius Ultrasound Scanner system, not a stand-alone device; compatible iOS/Android app versions and PA HD3, PAL HD3, and C3 HD3 transducers are listed in the packet. Generic DICOM/PACS integration is not established for the subject device.
Clarius's support article on cloud data security says Clarius Cloud data is stored in AWS data centers in a customer-chosen region (Canada, United States Oregon, EU Frankfurt or Australia), exams can be sent to PACS by DICOM with cloud storage disabled, activity logs are kept for six months, patient information is stored for seven years, backups run hourly and are kept 365 days, and an independent third party validates security. No certification is named, and the information security whitepaper it cites was not read.
Vendor-wide
Checked 2026-10-25
Vendor-wide statement, not an independent attestation. It does not establish certificate or report scope for this exact release, expiry, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.
Clarius' cloud security support article states 6-month log retention, 7-year patient data retention, and hourly backups kept for 365 days for its AWS-hosted cloud, with third-party security validation.
Vendor-wide
Checked 2026-10-27
Vendor statement, not an attestation. The article names Clarius' cloud generally and does not scope these commitments to any specific product release; exact-release scope is not established. These are logging, retention and backup commitments; the article states no alerting or response-time SLAs.
ACR AI Central provides an exact-submission model card for Clarius Ejection Fraction AI; 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
21Fields 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, acr ai central product, vendor documentation, fda decision summary, 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 K253593 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
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.
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.
Authorized purpose: Automated post-processing and measurement of adult transthoracic echocardiograms to support cardiologist/sonographer review and clinical decision-making.
Modality
Ultrasound
Anatomy
Heart, including left-ventricular structure and function
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.