FDA-cleared profile

AI Platform 2.2 (AIP002)

Exo Imaging · Ultrasound · FDA-cleared (510(k))

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.

Clinical role
AI modules integrated into a legally marketed ultrasound imaging device let users detect, measure and calculate medical parameters from ultrasound images, and provide real-time frame and clip quality scores to assist healthcare professionals while acquiring ultrasound images.
Images and patients
Ultrasound · Heart/Cardiovascular; Lung; Abdomen/Pelvis
Key limitation
Keep in mind: The added abdominal indication is outside the predicate PCCP; users must use clinical judgment and independently assess diagnostic adequacy.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: 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.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart/Cardiovascular; Lung; Abdomen/Pelvis Input: Single- or multi-frame DICOM ultrasound images from software modules integrated into compatible ultrasound devices.
  • Who uses it?Intended users: Healthcare professionals trained and qualified to conduct echocardiography, abdominal, and lung ultrasound scans in the current standard of care while acquiring ultrasound images.
  • What does the software produce?Output: Lung A/B-line presence and count; cardiac LVEF, IVC and myocardial-wall measurements; image-quality feedback for cardiac, lung and added abdominal views.
  • What is its most important limitation?Key limitation: The added abdominal indication is outside the predicate PCCP; users must use clinical judgment and independently assess diagnostic adequacy.

Clinical takeaway. Clinical role: 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.

Evidence takeaway. Evidence from the reviewed source record: The FDA summary reports image-quality agreement in retrospective clip validation and real-time evaluation; no disease-detection sensitivity or specificity is reported.

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
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.
  • Exact FDA submission
  • Checked 2026-09-19

Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.

Workflow role
AI modules integrated into a legally marketed ultrasound imaging device let users detect, measure and calculate medical parameters from ultrasound images, and provide real-time frame and clip quality scores to assist healthcare professionals while acquiring ultrasound images.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "allows users to detect, measure, and calculate relevant medical parameters of structures and function of patients with suspected disease. In addition, it provides frame and clip quality score in real-time" … "The AI modules are provided as software components to be integrated by another computer programmer into their legally marketed ultrasound imaging device.". Read from the exact FDA decision document on 2026-11-14.

Required input
Single- or multi-frame DICOM ultrasound images from software modules integrated into compatible ultrasound devices.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Output and clinician action
Lung A/B-line presence and count; cardiac LVEF, IVC and myocardial-wall measurements; image-quality feedback for cardiac, lung and added abdominal views.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
Healthcare professionals trained and qualified to conduct echocardiography, abdominal, and lung ultrasound scans in the current standard of care while acquiring ultrasound images.
  • Exact FDA submission
  • Checked 2026-09-19

The exact indications for use identify the trained and qualified healthcare-professional scope.

Limitations
The added abdominal indication is outside the predicate PCCP; users must use clinical judgment and independently assess diagnostic adequacy.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Evidence summary
The FDA summary reports image-quality agreement in retrospective clip validation and real-time evaluation; no disease-detection sensitivity or specificity is reported.
  • Exact FDA submission
  • Checked 2026-09-05

Evidence

Performance 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.

Evidence summary
The FDA summary reports image-quality agreement in retrospective clip validation and real-time evaluation; no disease-detection sensitivity or specificity is reported.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-05
Reported sensitivity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-05
Reported specificity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-05

Clip-level quality ICC

0.95 ICC

  • EndpointAbdominal image-quality agreement
  • Population184 patients, 200 clips
  • Tested versionAI Platform 2.2

AI Platform 2.2 abdominal quality validation

  • DesignRetrospective clip validation with separate real-time usability evaluation.
  • Population184 patients / 200 clips in retrospective validation; 186 real-time scans by 12 users in separate evaluation.
  • Scopeexact submission
  • Tested versionAI Platform 2.2 (AIP002)
  • Samplen=184
  • IndependenceIndependence not established

K260217

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 & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Single- or multi-frame DICOM ultrasound images from software modules integrated into compatible ultrasound devices.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-19 · FDA K260217: AI Platform 2.2 (AIP002)

  2. Routing

    Source context, not route validation: Current Exo Iris specifications describe DICOM worklist/store/send and PACS/VNA connectivity; EHR access requires Exo Works Enterprise, and worksheets/1 TB cloud storage require Connect.

    Scope: Product family. Package requirements are family-level and do not establish that every AIP002 deployment includes them.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-06 · Exo Iris technical specifications

  3. AI processing

    Source context, not route validation: AI modules and APIs are integrated by the ultrasound-device programmer; current hosting details were not established.

    Scope: Exact FDA submission.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-05 · AI Platform 2.2: K260217 clearance and 510(k) summary

  4. Returned objects

    Source context, not route validation: Lung A/B-line presence and count; cardiac LVEF, IVC and myocardial-wall measurements; image-quality feedback for cardiac, lung and added abdominal views.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-19 · FDA K260217: AI Platform 2.2 (AIP002)

  5. Viewer/worklist/report

    Unresolved route: Lung A/B-line presence and count; cardiac LVEF, IVC and myocardial-wall measurements; image-quality feedback for cardiac, lung and added abdominal views.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    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-19 · FDA K260217: AI Platform 2.2 (AIP002)

  6. Support owner

    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.

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

Open the printable evaluation checklist

Deployment
AI modules and APIs are integrated by the ultrasound-device programmer; current hosting details were not established.
  • Exact FDA submission
  • Checked 2026-09-05
Integration
Current Exo Iris specifications describe DICOM worklist/store/send and PACS/VNA connectivity; EHR access requires Exo Works Enterprise, and worksheets/1 TB cloud storage require Connect.
  • Product family
  • Checked 2026-09-06

Package requirements are family-level and do not establish that every AIP002 deployment includes them.

Security
Exo's Security Trust Center describes a company-wide security program for its cloud and mobile applications: information security policies based on ISO/IEC 27001, software development lifecycle security practices covering the platform and all applications, ongoing penetration testing of cloud services and applications, continuous monitoring with incident response, and business continuity plans validated by third-party audits (SOC 2, HITRUST, ISO 27001).
  • Vendor-wide
  • Checked 2026-10-27

Vendor statements; no certificates or audit reports read. Exo's dated HITRUST/SOC 2 certification announcement is scoped to the Exo Works workflow product specifically. Applicant 'Exo Imaging' bridges to Exo (exo.inc). Exact-release scope is not established.

Monitoring
Exo's security trust center states ongoing penetration testing, continuous monitoring and incident response across its platform and applications, with business continuity validated by third-party audits.
  • 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. Audit reports were not read.

Family package caveats

EHR requires Works Enterprise; worksheets and 1 TB cloud storage require Connect.

product family · checked 2026-09-06
Sources & review details FDA 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.

FDA submission
K260217
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Anatomy
Heart/Cardiovascular; Lung; Abdomen/Pelvis
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2026-02-24
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-19Last searched
25Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

No stored literature or trial candidates; empty metadata snapshots were screened. 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, fda decision summary, vendor technical page, 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 publicly available - checked 2026-09-06 - Exact product version
  • 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 Iris reimbursement CPT coverage"; 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; eligibility depends on 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 publicly available - checked 2026-09-05 - Exact product version

9 sources - 3 history items

Source ledger

  1. FDA K260217: AI Platform 2.2 (AIP002)

    U.S. Food and Drug Administration - Published 2026-02-24 - Accessed 2026-09-19

    Scope: purpose, modality, anatomy, input, output, limitations, evidenceSummary, intendedUsers, clinicalUse

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. AI Platform 2.2 (AIP002) model card (K260217)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. Exo Iris technical specifications

    Exo - Accessed 2026-09-06

    Scope: product_family_implementation

  8. AI Platform 2.2: K260217 clearance and 510(k) summary

    US Food and Drug Administration - Accessed 2026-09-05

    Scope: identity, clinical, implementation, evidence

  9. Exo: Security Trust Center - Security

    Exo - Accessed 2026-10-27

    Scope: security

Research history

  1. K260217 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K253535

Ligence Heart

Ligence Uab

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.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2026-02-27
FDA-cleared K252235

PVAD IQ 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.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2025-12-18
FDA-cleared K252105

Ligence Heart

Ligence, UAB

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
Decision
2025-09-26

Correct this exact record

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 destination

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.

Correction policy and limits · Public repository change history