64/100

Moderate evidence

GainPublished recordHealthGood Space

Three-Dimensional Point-Cloud Learning for Patient-Specific Deep Brain Stimulation Motor Response Prediction in Parkinson Disease

Truvace record
TRV-2026-1202raw data (JSON)
Version
v2Revised
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
4e40275e3fc3…check it

Objective: To develop a patient-specific 3-dimensional (3D) point-cloud deep learning framework for predicting motor improvement after deep brain stimulation (DBS) in Parkinson's disease. Impact Statement: This study introduces an electric-field-aware point-cloud representation that preserves patient anatomy, electrode geometry, and local electric-field distributions for individualized DBS motor response prediction. Introduction: DBS response varies because of complex interactions among electrode location, anato…

The gain

On a fixed test set of 24 Parkinson patients, the 3D model predicted motor improvement after brain stimulation within 5 points for 15, versus 8 for a voxelized neural network baseline; authors say this does not show clinical utility.

What this doesn’t fix

Small fixed test set of 24 patients limits generalizability; authors state estimates do not support claims of superiority or clinical utility, and 37 patients were excluded for incomplete data.

Sources

1 on file
  1. BME Frontiersdoi:10.34133/bmef.0276
    Peer-reviewed2026-09-22

Cite this record

v2

Truvace Impact Record TRV-2026-1202, v2: “Three-Dimensional Point-Cloud Learning for Patient-Specific Deep Brain Stimulation Motor Response Prediction in Parkinson Disease.” Truvace, 2026-11-04. /record/TRV-2026-1202 (accessed on the day you copy it). sha256 4e40275e3fc30066…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv24e40275e3fc3…

    Editorial pass: sharper headline; gain/problem restated as concrete outcomes.

  2. Publishedv1f31b14d3d6a4…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1202 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.