TRV-2026-2337Certified recordPeer-reviewed

Real-time artificial intelligence-assisted assessment in a home-based pelvic floor muscle training device for pelvic organ prolapse and stress urinary incontinence: A single-center prospective study

Objective Pelvic floor muscle training (PFMT) is the first-line conservative treatment of pelvic organ prolapse (POP) and stress urinary incontinence (SUI), but its effectiveness is often limited by poor adherence and performance. We developed a third-generation home-based PFMT device incorporating real-time artificial intelligence (AI)-assisted assessment. This study aimed to evaluate the efficacy of this device in women with POP or SUI. Materials and methods This prospective single-arm study was conducted at T…

Health · Good Space — documented gain · certified 2026-11-02 · v1 · article view · machine-readable

Current reading — gain

Over two months of home training with an AI-assisted pressure-sensing device, women with mild prolapse or stress urinary incontinence reported fewer symptoms, leaked less urine, and had better muscle contraction quality.

What this doesn’t fix

The authors note the study was limited by a small sample size, short follow-up and a single-arm design, so the effect of the AI assessment cannot be separated from training itself.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2337, v1: “Real-time artificial intelligence-assisted assessment in a home-based pelvic floor muscle training device for pelvic organ prolapse and stress urinary incontinence: A single-center prospective study.” Truvace, 2026-11-02. /record/TRV-2026-2337 (accessed at citation time). sha256 d183584c0e2af365…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1d183584c0e2a…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2337 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.