aceUtility of Augmented Reality Glasses With Waveguide Optics and Facial Recognition Technology for Patient Verification in a Simulated Outpatient Setting: Physician Questionnaire Survey Study
Background Augmented reality (AR) glasses with waveguide optics and facial recognition may enhance patient identification and clinical workflows. However, their usability among physicians has not yet been evaluated. Objective The objective of this study was to assess the usability and acceptability of prototype AR glasses with facial recognition in a simulated outpatient setting. Methods In May 2025, 14 urologists from a single institution tested prototype AR glasses developed by Cellid Inc. The device incorpora…
In a simulated outpatient setting, most urologists who tested the prototype said it helped with clinical procedures and improved patient safety, and many would use it in future practice.
Some physicians reported eye fatigue, heaviness, difficulty wearing the device over prescription glasses, and hard-to-read patient information on the display.
This was a small pilot with 14 urologists from a single institution in a simulated setting, relying on self-reported questionnaire responses, so the authors say further refinement and larger clinical evaluations are needed.
Evidence
- Peer-reviewedJMIR Human Factors2026-10-02
How should this claim be treated?
Truvace Impact Record TRV-2026-1368, v1: “Utility of Augmented Reality Glasses With Waveguide Optics and Facial Recognition Technology for Patient Verification in a Simulated Outpatient Setting: Physician Questionnaire Survey Study.” Truvace, 2026-10-14. /record/TRV-2026-1368 (accessed at citation time). sha256 0638611e0c9edd47…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-1368 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.