FDA-cleared profile

Lung AI (LAI001)

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

Authorized purpose: Lung AI LAI001 assists trained healthcare professionals performing point-of-care lung ultrasound by detecting and visualizing pleural effusion and consolidation or atelectasis in lung ultrasound cine clips.

Clinical role
Frame-level visualization aid for lung-ultrasound findings at the PLAPS point.
Images and patients
Ultrasound · Lung; pleural effusion and consolidation or atelectasis at the PLAPS point
Key limitation
Keep in mind: The FDA labeling states that Lung AI is not a clinical diagnosis, does not replace provider judgment or standard tests, and was not designed or tested for EMTs or military medics. CT or X-ray remains required when standard of care calls for it.

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: Lung AI LAI001 assists trained healthcare professionals performing point-of-care lung ultrasound by detecting and visualizing pleural effusion and consolidation or atelectasis in lung ultrasound cine clips.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Lung; pleural effusion and consolidation or atelectasis at the PLAPS point Input: Lung ultrasound cine clips acquired during the BLUE protocol PLAPS point.
  • Who uses it?Intended users: Trained and qualified healthcare professionals performing point-of-care ultrasound in emergency-department workflows; the FDA labeling does not include EMTs or military medics.
  • What does the software produce?Output: One region of interest per clip frame showing the largest detected finding for visualization; no patient-level aggregation is provided.
  • What is its most important limitation?Key limitation: The FDA labeling states that Lung AI is not a clinical diagnosis, does not replace provider judgment or standard tests, and was not designed or tested for EMTs or military medics. CT or X-ray remains required when standard of care calls for it.

Clinical takeaway. Clinical role: Lung AI LAI001 assists trained healthcare professionals performing point-of-care lung ultrasound by detecting and visualizing pleural effusion and consolidation or atelectasis in lung ultrasound cine clips.

Evidence takeaway. Evidence from the reviewed source record: K243239 FDA decision material reports the exact evidence metrics included below for Lung AI LAI001; values are limited to the stated endpoint, population, and operating point.

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
Lung AI LAI001 assists trained healthcare professionals performing point-of-care lung ultrasound by detecting and visualizing pleural effusion and consolidation or atelectasis in lung ultrasound cine clips.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Frame-level visualization aid for lung-ultrasound findings at the PLAPS point.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Lung ultrasound cine clips acquired during the BLUE protocol PLAPS point.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
One region of interest per clip frame showing the largest detected finding for visualization; no patient-level aggregation is provided.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Emergency-department point-of-care lung-ultrasound workflows.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Trained and qualified healthcare professionals performing point-of-care ultrasound in emergency-department workflows; the FDA labeling does not include EMTs or military medics.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
The FDA labeling states that Lung AI is not a clinical diagnosis, does not replace provider judgment or standard tests, and was not designed or tested for EMTs or military medics. CT or X-ray remains required when standard of care calls for it.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
K243239 FDA decision material reports the exact evidence metrics included below for Lung AI LAI001; values are limited to the stated endpoint, population, and operating point.
  • Exact FDA submission
  • Checked 2026-09-04

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
K243239 FDA decision material reports the exact evidence metrics included below for Lung AI LAI001; values are limited to the stated endpoint, population, and operating point.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Reported sensitivity
Pleural Effusion: 97% (95% CI: 94%, 99%) , Consolidation/Atelectasis: 97% (95% CI: 94%, 99%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

Reported specificity
Pleural Effusion: 91% (95% CI: 87%, 96%) , Consolidation/Atelectasis: 94% (95% CI: 90%, 98%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model specificity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

Pleural-effusion detection sensitivity

97 percent

  • EndpointFinding detection sensitivity
  • PopulationLung ultrasound scans in the FDA bench dataset
  • Tested versionLung AI LAI001

Pleural-effusion detection specificity

91 percent

  • EndpointFinding detection specificity
  • PopulationLung ultrasound scans in the FDA bench dataset
  • Tested versionLung AI LAI001

Consolidation/atelectasis detection sensitivity

97 percent

  • EndpointFinding detection sensitivity
  • PopulationLung ultrasound scans in the FDA bench dataset
  • Tested versionLung AI LAI001

Consolidation/atelectasis detection specificity

94 percent

  • EndpointFinding detection specificity
  • PopulationLung ultrasound scans in the FDA bench dataset
  • Tested versionLung AI LAI001

K243239 FDA evidence package for Lung AI (LAI001)

  • DesignFDA 510(k) bench detection and localization validation.
  • Population465 lung-ultrasound scans from 359 unique patients at six U.S. and Canadian centers.
  • Scopeexact submission
  • Tested versionLung AI LAI001
  • Samplen=465
  • Sites6
  • IndependenceSponsor or vendor study

K243239

FDA-reported detection results for the exact LAI001 configuration; reader-aided results are not generalized here.

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
No record matched K243239 by exact native submission identifier in the 2026-09-02 openFDA snapshot; this does not exclude product-family, later-version, or adverse-event information.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-04
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

No product-specific code

No exact-product reimbursement determination identified in reviewed public material

Centers for Medicare & Medicaid Services · United States

This public-policy review is not a coverage determination. Verify payer, site-of-service, coding, and local value assumptions independently.

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: Lung ultrasound cine clips acquired during the BLUE protocol PLAPS point.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K243239: Lung AI (LAI001)

  2. Routing

    Source context, not route validation: The FDA package describes post-processing integrated by a programmer into a third-party ultrasound device and displayed in the existing ultrasound interface without a built-in viewer.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K243239: Lung AI (LAI001)

  3. AI processing

    Source context, not route validation: The FDA package describes integration into a third-party ultrasound device; current device configuration, hosting, security, availability, and service boundaries remain unknown.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K243239: Lung AI (LAI001)

  4. Returned objects

    Source context, not route validation: One region of interest per clip frame showing the largest detected finding for visualization; no patient-level aggregation is provided.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K243239: Lung AI (LAI001)

  5. Viewer/worklist/report

    Unresolved route: One region of interest per clip frame showing the largest detected finding for visualization; no patient-level aggregation is provided.

    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.

    Field checked 2026-09-04 · FDA 510(k) decision material K243239: Lung AI (LAI001)

  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
The FDA package describes integration into a third-party ultrasound device; current device configuration, hosting, security, availability, and service boundaries remain unknown.
  • Exact FDA submission
  • Checked 2026-09-04
Integration
The FDA package describes post-processing integrated by a programmer into a third-party ultrasound device and displayed in the existing ultrasound interface without a built-in viewer.
  • Exact FDA submission
  • Checked 2026-09-04
Security
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.

Training
Use by trained and qualified healthcare professionals performing point-of-care ultrasound in emergency-department workflows; the fda labeling does not include emts or military medics. Follow the exact labeling, local training, supervision, and escalation requirements.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor labeled population, acquisition quality, exclusions, reviewer overrides, failures, and downstream workflow effects for K243239.
  • Exact FDA submission
  • Checked 2026-09-04

Release and scope verification

Map installed build, options, population, anatomy, inputs, outputs, and enabled functions to K243239.

exact submission · checked 2026-09-04

Deployment boundary

The FDA package describes integration into a third-party ultrasound device; current device configuration, hosting, security, availability, and service boundaries remain unknown.

exact submission · checked 2026-09-04

Interoperability acceptance

The FDA package describes post-processing integrated by a programmer into a third-party ultrasound device and displayed in the existing ultrasound interface without a built-in viewer.

exact submission · checked 2026-09-04

Clinical acceptance

Test labeled population, acquisition quality, exclusions, failed inputs, reviewer overrides, and downstream effects for K243239.

exact submission · checked 2026-09-04

Economic evaluation

Exact-product price, implementation cost, reimbursement, and total-cost evidence remain to be obtained; do not infer them from FDA clearance.

product family · checked 2026-09-04

Lifecycle monitoring

Monitor labeling, software version, complaints, recalls, failed inputs, overrides, and postmarket signals against the exact submission and installed configuration.

exact submission · checked 2026-09-04
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
K243239
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Lung; pleural effusion and consolidation or atelectasis at the PLAPS point
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2025-04-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.

Human reviewedStatus
2026-09-04Last searched
27Fields reviewed
12Source classes checked
6Screened PubMed leads
3Screened trial leads
0Unreviewed FDA recall leads

No evidence was promoted. All records concern unrelated cancer, CT, animal, or lung-ultrasound products from other vendors and do not identify Exo Lung AI LAI001 or K243239. The current discovery snapshot contains 6 PubMed and 3 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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-04 - Exact FDA submission

    No public list price or commercial contract for the exact submission and version was identified.

  • 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-04 - Exact FDA submission

    No exact-product payer coverage or reimbursement determination was identified in reviewed public material.

  • 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

8 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K243239: Lung AI (LAI001)

    U.S. Food and Drug Administration - Published 2025-04-24 - Accessed 2026-09-04

    Scope: identity, submission_linkage, modality, anatomy, clinical_use, intended_users, care_setting, workflow_role, input, output, limitations, evidence

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. Lung AI (LAI001) model card (K243239)

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

    Scope: intendedUsers, careSetting, output, reportedSensitivity, reportedSpecificity, evidenceSummary, anatomy, evidenceStudies

  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. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  8. Exo Trust Center: Security

    Exo - Accessed 2026-10-25

    Scope: security

Research history

  1. K243239 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K260234

MSK Go

Smart Alfa Teknoloji San. Ve Tic. A.S.

Authorized purpose: Assist qualified MSK-ultrasound professionals by highlighting supported joint anatomy and detection completeness on compatible adult ultrasound images; it is not a diagnostic device.

Modality
Ultrasound
Anatomy
Musculoskeletal joints: shoulder, elbow, wrist/hand, knee, and ankle/foot.
Decision
2026-05-21
FDA-cleared K252433

Sonio Detect (v3)

Sonio

Authorized purpose: Sonio Detect v3 analyzes fetal ultrasound images and clips to detect views and anatomical structures and to check labeled image-quality characteristics during acquisition or interpretation.

Modality
Ultrasound
Anatomy
Fetal anatomy
Decision
2026-03-16
FDA-cleared K250959

BioticsAI

Bioticsai, Inc.

Authorized purpose: BioticsAI assists healthcare professionals during and after fetal ultrasound acquisition and interpretation by detecting views and anatomical structures and facilitating quality-criteria verification on DICOM images and frames; it is a concurrent reading aid for the labeled GE ultrasound and prenatal population.

Modality
Ultrasound
Anatomy
Obstetric/Fetal
Decision
2025-12-22

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