Authorized purpose: Aid quantification of bladder volume from ultrasound images in patients aged two years or older.
Clinical role
Imported-image post-processing with image viewing, manual or semi-automatic landmark placement, bladder-volume quantification, and examination-report generation.
Images and patients
Ultrasound · Urinary bladder
Key limitation
Keep in mind: The FDA indication is limited to bladder-volume quantification in patients aged two years or older. Validation used 122 subjects, ultrasound frequencies from 1.3 to 9 MHz, and volumes of 11-645 mL; those study bounds should not be treated as an unrestricted performance claim.
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: Aid quantification of bladder volume from ultrasound images in patients aged two years or older.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Urinary bladder Input: DICOM single-frame and multi-frame bladder ultrasound images from cart-based or portable ultrasound devices; the FDA validation covered bladder volumes from 11 to 645 mL and patient ages from 2 to 95 years.
Who uses it?Intended users: Trained healthcare providers and qualified users.
What does the software produce?Output: Bladder dimensions and volume measurements, including dual-view volume calculated from transverse and sagittal views and single-view volume, with report creation.
What is its most important limitation?Key limitation: The FDA indication is limited to bladder-volume quantification in patients aged two years or older. Validation used 122 subjects, ultrasound frequencies from 1.3 to 9 MHz, and volumes of 11-645 mL; those study bounds should not be treated as an unrestricted performance claim.
Clinical takeaway. Clinical role: Aid quantification of bladder volume from ultrasound images in patients aged two years or older.
Evidence takeaway. Evidence from the reviewed source record: Clinical performance testing used 122 subjects with cart-based and portable ultrasound images and a test set separated from training and validation data. Reference bladder volume was the average measurement of three expert clinicians. Dual-view volume mean difference was 2 mL with limits of agreement -42 to 46 mL and ICC 0.98; single-view volume mean difference was 3 mL with limits of agreement -49 to 55 mL and ICC 0.97. These are measurement-error and reliability endpoints, not sensitivity, specificity, or AUC.
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
Aid quantification of bladder volume from ultrasound images in patients aged two years or older.
Imported-image post-processing with image viewing, manual or semi-automatic landmark placement, bladder-volume quantification, and examination-report generation.
DICOM single-frame and multi-frame bladder ultrasound images from cart-based or portable ultrasound devices; the FDA validation covered bladder volumes from 11 to 645 mL and patient ages from 2 to 95 years.
Bladder dimensions and volume measurements, including dual-view volume calculated from transverse and sagittal views and single-view volume, with report creation.
The FDA indication is limited to bladder-volume quantification in patients aged two years or older. Validation used 122 subjects, ultrasound frequencies from 1.3 to 9 MHz, and volumes of 11-645 mL; those study bounds should not be treated as an unrestricted performance claim.
Clinical performance testing used 122 subjects with cart-based and portable ultrasound images and a test set separated from training and validation data. Reference bladder volume was the average measurement of three expert clinicians. Dual-view volume mean difference was 2 mL with limits of agreement -42 to 46 mL and ICC 0.98; single-view volume mean difference was 3 mL with limits of agreement -49 to 55 mL and ICC 0.97. These are measurement-error and reliability endpoints, not sensitivity, specificity, or AUC.
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
Clinical performance testing used 122 subjects with cart-based and portable ultrasound images and a test set separated from training and validation data. Reference bladder volume was the average measurement of three expert clinicians. Dual-view volume mean difference was 2 mL with limits of agreement -42 to 46 mL and ICC 0.98; single-view volume mean difference was 3 mL with limits of agreement -49 to 55 mL and ICC 0.97. These are measurement-error and reliability endpoints, not sensitivity, specificity, or AUC.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Bladder AI (AIBV01) regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult and Pediatric
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K230497
Samplen=122
IndependenceIndependence not established
K230497
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 K230497. 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 single-frame and multi-frame bladder ultrasound images from cart-based or portable ultrasound devices; the FDA validation covered bladder volumes from 11 to 645 mL and patient ages from 2 to 95 years.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA packet describes imported DICOM images and a web-browser operating environment, including Google Chrome, for the standalone software; it does not establish PACS/RIS/EHR integration, current interface versions, or deployment configuration.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes Bladder AI as standalone software whose listed operating system is a web browser (Google Chrome), the same entry given for the predicate. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Web browser (Google Web browser (Google Web browser (Google Operating System Chrome) Chrome) Chrome) and Android" … "Feature/ Subject Device Predicate Device Reference Device Function Bladder AI (K230497) MEDO-Thyroid (K203502) LVivo Bladder (K200232) Single and Multi-frame Single and Multi-frame". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Bladder dimensions and volume measurements, including dual-view volume calculated from transverse and sagittal views and single-view volume, with report creation.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Bladder dimensions and volume measurements, including dual-view volume calculated from transverse and sagittal views and single-view volume, with report creation.
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 exact FDA package describes Bladder AI as standalone software whose listed operating system is a web browser (Google Chrome), the same entry given for the predicate. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Web browser (Google Web browser (Google Web browser (Google Operating System Chrome) Chrome) Chrome) and Android" … "Feature/ Subject Device Predicate Device Reference Device Function Bladder AI (K230497) MEDO-Thyroid (K203502) LVivo Bladder (K200232) Single and Multi-frame Single and Multi-frame". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The FDA packet describes imported DICOM images and a web-browser operating environment, including Google Chrome, for the standalone software; it does not establish PACS/RIS/EHR integration, current interface versions, or deployment configuration.
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.
ACR AI Central provides an exact-submission model card for Bladder AI (AIBV01); 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
24Fields 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, fda decision summary, acr ai central product, vendor documentation, 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 K230497 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.
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.
Authorized purpose: EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.
Authorized purpose: EdgeFlow UH10 is an ultrasound device intended to measure urine volume in the bladder noninvasively in professional healthcare facilities such as hospitals and clinics by qualified and trained healthcare professionals. The FDA indication describes B-mode and harmonic imaging modes.
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.
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.