Authorized purpose: Measures global longitudinal strain from apical four-chamber cardiac ultrasound images in adult patients with suspected disease as an aid to diagnostic analysis; users can accept or reject measurements.
Clinical role
Post-processing measurement of global longitudinal strain with user acceptance or rejection.
Images and patients
Ultrasound · Heart/Cardiovascular
Key limitation
Keep in mind: No built-in viewer; integration into a legally marketed ultrasound imaging device is required. Patient management must not rely solely on Strain AI analysis.
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: Measures global longitudinal strain from apical four-chamber cardiac ultrasound images in adult patients with suspected disease as an aid to diagnostic analysis; users can accept or reject measurements.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart/Cardiovascular Input: Multi-frame apical four-chamber cardiac ultrasound images from adults with suspected disease. Validation included routine clinical images from cart-based and portable systems at 1.2-4 MHz.
Who uses it?Intended users: Clinical end users of a legally marketed ultrasound imaging device into which the Strain AI module is integrated.
What does the software produce?Output: A quantitative global longitudinal strain measurement; end users may accept or reject it.
What is its most important limitation?Key limitation: No built-in viewer; integration into a legally marketed ultrasound imaging device is required. Patient management must not rely solely on Strain AI analysis.
Clinical takeaway. Clinical role: Measures global longitudinal strain from apical four-chamber cardiac ultrasound images in adult patients with suspected disease as an aid to diagnostic analysis; users can accept or reject measurements.
Evidence takeaway. Evidence from the reviewed source record: Regulatory GLS measurement agreement against a reference device; no independent clinical-outcome comparison was established.
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
Measures global longitudinal strain from apical four-chamber cardiac ultrasound images in adult patients with suspected disease as an aid to diagnostic analysis; users can accept or reject measurements.
Multi-frame apical four-chamber cardiac ultrasound images from adults with suspected disease. Validation included routine clinical images from cart-based and portable systems at 1.2-4 MHz.
Exact FDA submission
Checked 2026-09-05
The validation frequency range is not a universal compatibility guarantee.
No built-in viewer; integration into a legally marketed ultrasound imaging device is required. Patient management must not rely solely on Strain AI analysis.
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
Regulatory GLS measurement agreement against a reference device; no independent clinical-outcome comparison was established.
1 unlinked candidate evidence record is retained for source review and excluded from this evidence display.
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
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
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: Multi-frame apical four-chamber cardiac ultrasound images from adults with suspected disease. Validation included routine clinical images from cart-based and portable systems at 1.2-4 MHz.
Scope: Exact FDA submission. The validation frequency range is not a universal compatibility guarantee.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: A software module integrated by another programmer into a legally marketed ultrasound imaging device; it uses that device's user interface rather than a built-in viewer.
Scope: Exact FDA submission. The earlier baseline's generic DICOM/PACS claim was not substantiated in this summary. Current Exo Iris interoperability is recorded only as product-family context.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: A quantitative global longitudinal strain measurement; end users may accept or reject it.
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.
A software module integrated by another programmer into a legally marketed ultrasound imaging device; it uses that device's user interface rather than a built-in viewer.
Exact FDA submission
Checked 2026-09-05
The earlier baseline's generic DICOM/PACS claim was not substantiated in this summary. Current Exo Iris interoperability is recorded only as product-family context.
Exo's trust center security page describes an information security program with policies based on ISO/IEC 27001, a software development lifecycle program, ongoing penetration testing, continuous monitoring, incident response and multi-zone cloud redundancy. Vendor-wide; it does not state a certification.
Vendor-wide
Checked 2026-10-25
Vendor statement, not an attestation; exact-release scope is not established.
Exo's security trust center describes its security program, including penetration testing and monitoring.
Vendor-wide
Checked 2026-10-27
Vendor statement, not an attestation. The page names Exo generally and does not scope these practices to any specific product release; exact-release scope is not established.
The official Iris specifications list DICOM worklist, store and send and PACS/VNA integration. EHR integration requires Exo Works Enterprise; the listed workflow worksheets and 1 TB cloud storage require Exo Works Connect.
product family · checked 2026-09-06
Host-platform package context only; this page does not establish these interfaces for every SAI001 installation.
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.
Human reviewedStatus
2026-09-06Last searched
19Fields reviewed
11Source classes checked
14Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
All 14 stored titles screened and excluded as exact-product evidence: 40055942 is a computer vision syndrome review; the other 13 concern microbiology, microbial strains or veterinary virology. None establishes Exo SAI001 cardiac GLS. No trials were stored. The current discovery snapshot contains 14 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, vendor documentation, vendor technical page, vendor product page, 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 publicly available - checked 2026-10-25 - Exact product version
Checked 2026-10-25: Exo's public Iris pricing page lists plan tiers (Iris, Iris Connect, Iris Enterprise) and names SweepAI, not Strain AI SAI001. The Exo store lists Exo Iris hardware and Exo Works Essential software plan prices, none described as a Strain AI price. No standalone SAI001 license price was found, so no price is stated. A device or plan price would not establish this module's price.
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-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "Exo Strain AI reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. This records what was found, not that none exists.
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-05 - Exact product version
Host-device onboarding and competency requirements for reviewing or rejecting GLS measurements were not established.
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.
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.
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.