Authorized purpose: EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.
Clinical role
EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.
Images and patients
Ultrasound · Urinary bladder
Key limitation
Keep in mind: The labeled adult population, BMI threshold, acquisition mode, and facility setting limit applicability; a bladder-volume estimate is not a broader diagnostic 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: EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Urinary bladder Input: Ultrasound echo data acquired with the supported transducers, exam modes, and labeled patient or anatomy scope.
Who uses it?Intended users: Qualified healthcare professionals within the exact labeled use.
What does the software produce?Output: Ultrasound images, measurements, flow information, or clinician-reviewed analyses described in the exact FDA labeling.
What is its most important limitation?Key limitation: The labeled adult population, BMI threshold, acquisition mode, and facility setting limit applicability; a bladder-volume estimate is not a broader diagnostic claim.
Clinical takeaway. Clinical role: EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench testing with bladder phantoms, a prospective single-center in-vivo study of acoustic coupling during 24-hour wearable use, and AI software validation. Volume estimation, tested on a held-out set of 1,902 images from 32 subjects against catheter-derived bladder volume, gave MAE 14.43 mL (10.62–18.26) for 0–100 mL and MAPE 10.71% (7.49–13.91) for 101–999 mL. Segmentation Dice was 0.936 (0.931–0.940); image-level bladder presence classification sensitivity was 0.976 and specificity 0.919. Results are as reported in the FDA submission, not independent validation.
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
EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.
The labeled adult population, BMI threshold, acquisition mode, and facility setting limit applicability; a bladder-volume estimate is not a broader diagnostic claim.
The exact FDA document reports bench testing with bladder phantoms, a prospective single-center in-vivo study of acoustic coupling during 24-hour wearable use, and AI software validation. Volume estimation, tested on a held-out set of 1,902 images from 32 subjects against catheter-derived bladder volume, gave MAE 14.43 mL (10.62–18.26) for 0–100 mL and MAPE 10.71% (7.49–13.91) for 101–999 mL. Segmentation Dice was 0.936 (0.931–0.940); image-level bladder presence classification sensitivity was 0.976 and specificity 0.919. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Bench testing was performed using bladder phantoms representing nominal volumes of 30, 50, 100, 500, and 1000 mL." … "A prospective, single-center in-vivo study was conducted at Severance Hospital to evaluate acoustic coupling stability during 24-hour wearable use of the EdgeFlow UW20.". Read from the exact FDA decision document on 2026-11-14.
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 exact FDA document reports bench testing with bladder phantoms, a prospective single-center in-vivo study of acoustic coupling during 24-hour wearable use, and AI software validation. Volume estimation, tested on a held-out set of 1,902 images from 32 subjects against catheter-derived bladder volume, gave MAE 14.43 mL (10.62–18.26) for 0–100 mL and MAPE 10.71% (7.49–13.91) for 101–999 mL. Segmentation Dice was 0.936 (0.931–0.940); image-level bladder presence classification sensitivity was 0.976 and specificity 0.919. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Bench testing was performed using bladder phantoms representing nominal volumes of 30, 50, 100, 500, and 1000 mL." … "A prospective, single-center in-vivo study was conducted at Severance Hospital to evaluate acoustic coupling stability during 24-hour wearable use of the EdgeFlow UW20.". Read from the exact FDA decision document on 2026-11-14.
No exact-product, version-specific sensitivity endpoint was established for this submission in the evidence set.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact-product, version-specific specificity endpoint was established for this submission in the evidence set.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K252237 FDA evidence package for EdgeFlow UW20
DesignFDA submission-level decision material with device, software, performance, safety, and/or usability verification as applicable; not independent clinical validation.
PopulationPopulation and workflow are limited to the exact FDA labeling summarized for this submission.
Scopeexact submission
Tested versionExact FDA submission release; version not separately stated in the public decision material
IndependenceSponsor or vendor study
K252237
Evidence submitted for the exact FDA decision is not independent clinical validation. Local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K252237 by native exact submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, dental, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
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 echo data acquired with the supported transducers, exam modes, and labeled patient or anatomy scope.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The wearable patch communicates through the described Bluetooth Low Energy module; facility integration and data export details remain to be confirmed.
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. Deployment details for the exact cleared configuration are not established in the public FDA decision material.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Ultrasound images, measurements, flow information, or clinician-reviewed analyses described in the exact FDA labeling.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Ultrasound images, measurements, flow information, or clinician-reviewed analyses described in the exact FDA labeling.
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 wearable patch communicates through the described Bluetooth Low Energy module; facility integration and data export details remain to be confirmed.
Use by the qualified healthcare professionals identified for the exact labeled workflow; site-specific competency and training requirements remain to be established locally.
The wearable patch communicates through the described Bluetooth Low Energy module; facility integration and data export details remain to be confirmed.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The labeled adult population, BMI threshold, acquisition mode, and facility setting limit applicability; a bladder-volume estimate is not a broader diagnostic claim.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in the evidence set; productivity or value claims require local evidence.
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes; exact monitoring thresholds and vendor commitments are unknown.
exact submission · checked 2026-09-04
Establish ownership for data quality, overrides, drift, incidents, recalls, and change control.
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-20Last searched
27Fields reviewed
12Source 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 material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, literature index, trial registry, fda decision summary, 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 for the exact cleared configuration was found in the evidence set. Obtain a written quote covering license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, downtime, and exit costs.
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
Deployment: Not verified - checked 2026-09-04 - Exact FDA submission
Deployment details for the exact cleared configuration are not established in the public FDA decision 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
Security: Not publicly available - checked 2026-09-04 - Exact FDA submission
Security controls, hosting boundaries, audit behavior, identity management, and incident commitments for the exact configuration are not established in the public FDA decision material.
Installation timeline: Not yet reviewed
Monitoring: Not verified - checked 2026-09-04 - Exact FDA submission
Post-deployment monitoring, drift thresholds, alerting, and revalidation commitments for the exact configuration require vendor and site confirmation.
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.