Study type · Virtual reality and digital therapeuticsUpdated October 12, 2026

VR therapeutic clinical trial data capture that joins headset use to patient outcomes

A VR trial has two data streams that rarely meet: what the headset logged and what the participant reported. Capture holds the clinical record, the outcome scales, the safety events and the session-adherence data you enter or import from your product team in one audited study. Build it free.

  • Session and adherence records
  • Sham VR arm kept blinded
  • Pain, mood and function scales by phone

Free sandbox · No credit card · 21 CFR Part 11 aligned

Demo 8-week home VR program: data collected
AssessmentBaselineWk 1Wk 2Wk 4Wk 8Wk 12
Headset sessions (usage summary)UUUU
Primary outcome scale (participant)PPPP
Function and mood scales (participant)PPPP
Cybersickness and discomfort checkPPPP
Clinic visit and adverse event review

U = usage summary entered per protocol, P = participant task, x = site form

Illustrative schedule. Program length and assessments follow your protocol.

What a VR therapeutic trial needs from its data system

  • Exposure is software use: sessions, minutes and module completion matter, and the headset data usually lives with the product team.
  • A sham that controls for the hardware: published home VR trials used a non-immersive, 2D sham experience on the same headset to control for novelty.
  • Patient-reported primary outcomes: pain intensity, interference, mood or anxiety scores completed repeatedly on the participant's phone.
  • VR-specific tolerability: dizziness, nausea, eye strain and falls risk need structured fields.
  • Two teams, one record: engineers hold usage logs, clinicians hold outcomes, and the analysis needs them joined by a participant ID.

The study design

What is different about a VR trial

Virtual reality interventions are used in pain, anxiety, phobias, rehabilitation and cognitive training, and a trial is typically a randomized comparison of an immersive program against a sham, an active comparator or usual care. In published home-based chronic low back pain trials, for instance, the control was a sham VR experience on the same type of headset that was two-dimensional and non-immersive, intended to control for the novelty and hardware rather than the skills content. That design logic matters for data capture, because the sham arm also generates usage data that must look the same in structure as the active arm.

Exposure in a VR trial is software use. The headset or companion app records sessions started, minutes of use and modules completed; the study needs those numbers per participant, aligned with the outcome schedule. Capture does not integrate with headsets or product backends. A product team exports usage summaries, which the study team transcribes into a usage form or loads into the dataset in the analysis stage, matched on the coded participant ID. Define that interface in the data management plan and test it before enrollment. The data management plan template is a starting point.

This page is about the trial design side. If you are a digital therapeutics company deciding how to build a clinical evidence programme, see clinical validation software for digital therapeutics. For broader digital designs, EDC for digital health clinical trials and EDC for mobile health studies apply.

Outcomes and tolerability

Patient-reported outcomes, usage data and cybersickness

Most VR therapeutic trials are won or lost on patient-reported outcomes: pain intensity and interference, mood, anxiety, sleep or function. Participants answer on their phone from a secure link in the browser, with reminders and completion windows you set, which suits a home-based program. See how to capture patient-reported outcomes digitally and BYOD ePRO with no app download. Template pages for the structure of common measures include the numeric pain rating scale, brief pain inventory and GAD-7. They show structure and scoring only, and you remain responsible for licences.

VR brings its own tolerability profile. Dizziness, nausea and disorientation, often grouped under cybersickness or simulator sickness, and eye strain or headache, are regular concerns, and there are questionnaires developed to rate them. Record them with a short check after sessions, plus the standard adverse event form for events that meet the protocol threshold. A fall at home while wearing a headset is a different severity than a mild headache, and the protocol should define the safety rules. Because cybersickness may unblind a participant who knows their sham has no motion, the participant blinding question at the end of the study is worth collecting.

A VR trial that is a regulated software or device study also needs the right documentation. See FDA digital health technologies guidance for clinical trials for the guidance on using digital health technologies to collect data, and digital biomarker validation study software if headset-derived measures are being validated.

Protocol to build

VR trial needs and where they live in Capture

NeedWhat the data looks likeWhere it lives in Capture
RandomizationActive VR or sham VR, stratification factorsRandomization in the system; blinded roles never see arm values
Usage / adherenceSessions, minutes, modules, last useUsage form entered by staff from the product team's summary, or merged at analysis by coded ID
Primary outcomePain, mood or function scale at set weeksePRO tasks with reminders and windows
TolerabilityDizziness, nausea, eye strain, fallsShort post-session check and adverse event form
Concomitant careMedicines and physiotherapy during the programConcomitant medications form
Remote consentConsent without a site visiteConsent; see econsent for decentralized trials
ExportOne row per submission, with data dictionaryCSV and Excel; see export to R, SAS and SPSS

Capture does not integrate with VR headsets, apps or product backends. Usage data is entered or merged by your team.

Test the participant schedule on a real phone

Build the outcome tasks and the usage form in the free sandbox, then open a task link on your own phone to feel the participant experience. No credit card.

Build your VR trial free

Build sequence

From program protocol to a live study

  1. 1

    Define exposure

    Decide which usage metrics are the dose (sessions, minutes, modules) and who supplies them.

  2. 2

    Build participant tasks

    Primary and secondary scales, with a short post-session discomfort check.

  3. 3

    Build the site and usage forms

    Screening, adverse events, concomitant medicines and a usage summary form.

  4. 4

    Configure blinding

    Randomization and roles, with the sham arm masked from raters and outcome analysts.

  5. 5

    Test and go live

    Run practice participants through the program, test the export and the usage merge, then approve forms.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Can Capture pull usage data from the VR headset?

No. Capture does not integrate with headsets or product backends. Usage summaries are entered by staff or merged at analysis using the coded participant ID.

How do we blind a sham VR arm?

Randomization is held in the system and blinded roles never receive treatment-arm values. Whether the sham experience is convincing is a design question for the protocol.

Can participants answer outcome scales at home?

Yes. Questionnaires open from a secure link in the phone browser with reminders and windows you set. No app install is needed.

Does this page claim regulatory clearance for VR products?

No. Regulatory status of a VR product depends on its intended use and the regulator. Check current guidance for your product.

Is this a page for digital therapeutic companies?

It is about trial data capture. For the company-level view of building clinical evidence, see the clinical validation software for digital therapeutics page.

Start building your study free

Free sandbox with every feature. No credit card, and you pay only when you go live with real participants.

Build your VR trial free