TRV-2026-2079Certified recordPeer-reviewed

Feasibility of an Activity Control System in Patients with Type 2 Diabetes: Results from a Non-Randomised Controlled Pilot Study

Objective Diabetes mellitus (DM) is a disease that requires continuous, active management by the patient, encompassing lifestyle and activities of daily living (ADL). There is limited evidence and a scarcity of devices that monitor ADL in patients with DM using artificial intelligence-based technology. This study evaluates the feasibility of the AI2EPD home activity monitoring system, focusing on therapeutic adherence in the treatment of people with DM2. Methods A pilot-controlled study was conducted. Vibration…

Health · The Trace — both readings · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

Participants in the intervention group found the AI-based home monitoring system easy to use and safe, indicating high acceptance and feasibility for people with type 2 diabetes.

Current reading — problem

The pilot found no clinical benefit attributable to the monitoring system, and the only significant HbA1c improvement occurred in the control group.

What this doesn’t fix

The study was a small, non-randomised pilot with multiple exploratory comparisons, so its clinical findings must be interpreted with caution and need confirmation in adequately powered studies.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2079, v1: “Feasibility of an Activity Control System in Patients with Type 2 Diabetes: Results from a Non-Randomised Controlled Pilot Study.” Truvace, 2026-10-21. /record/TRV-2026-2079 (accessed at citation time). sha256 2e5cad8878f691b3…

Calibration history

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

  1. Certifiedv12e5cad8878f6…

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