TRV-2026-1984Version 1 · Certified

Written 2026-10-20 06:54:52 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1984
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-20T06:54:52.182924Z
status: published
lens: p_space
sector: health
headline: Willingness to undergo autonomous robotic surgery in Jordanian medical students: a national multicenter cross-sectional survey
dek: Surgical robots in clinical use operate under continuous human control, yet research systems now perform surgical tasks on their own. Patient willingness may limit adoption, and to our knowledge no study has measured willingness across defined levels of autonomy while holding performance constant. To estimate the willingness of Jordanian medical students to undergo high-autonomy robotic surgery with immediate surgeon oversight and to quantify how willingness changes as autonomy increases. We conducted a national…
gain_title: (none)
problem_title: Willingness to undergo autonomous robotic surgery dropped steeply as AI took over surgical steps and surgeon rescue was removed, which may limit adoption of high-autonomy systems.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: Willingness to undergo autonomous robotic surgery dropped steeply as AI took over surgical steps and surgeon rescue was removed, which may limit adoption of high-autonomy systems.
problem_evidence: Patient willingness may limit adoption
quick_read: A national survey of 574 undergraduate medical students at eight Jordanian schools asked how willing they would be to have their own operation done under five levels of robotic autonomy. Regulatory approval and equal outcomes were held constant. About 39.7% were willing at stage 4, where AI performs the whole operation with a surgeon in the room able to take over.

The results suggest that acceptance of autonomous surgery depends on keeping a surgeon present and able to intervene, so a supervised, stepwise rollout fits these students' stated preferences. The sample is of medical students rather than patients, so how patients themselves would respond is still unknown.
limitation: The sample was a convenience sample of medical students, and the authors state that patients' views remain untested.
tag: Evidence-backed problem
key_points: Willingness was 76.0% for surgeon-controlled robotic surgery and 18.6% when AI operated with no surgeon available. | The largest declines followed AI performing surgical steps (-30.5 percentage points) and loss of immediate surgeon presence (-21.1 points). | Trust in autonomous systems was associated with willingness (adjusted odds ratio per SD 2.75), while surgical career intention was not. | Stage 4 willingness ranged from 34.9% to 41.7% across analyses of university representation and response quality.
rundown: The study was a cross-sectional online survey run between 31 August and 17 September 2026 at eight Jordanian medical schools, using a convenience sample. Students read a standardized vignette and then rated willingness on a five-point scale for each of five arrangements.

The primary endpoint was willingness at stage 4. The gradient across stages was a prespecified secondary analysis, and cumulative link mixed models handled the repeated ratings. The odds of willingness fell by a factor of 0.40 per stage.

Willingness declined in steps rather than smoothly: about 76-78% at stages 1 and 2, 47.2% at stage 3, and 18.6% at stage 5. The decline was steeper among higher-quality respondents.
sources:
- peer_reviewed | Journal of Robotic Surgery | https://doi.org/10.1007/s11701-026-04075-0 | 2026-10-15
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
8c4e6feade9c6a52ef96440774b3db534e29f4f9a0d2844b1db48903bbcd4966
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1984 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.