Your VR Pilot Worked. Will a Hospital Buy It?

A successful study can show that a VR health solution is safe and performs as intended – while leaving its strongest selling point untested. At IHT Conference’26, VR Health Champions brought experts and participants together to explore what developers need to prove before a promising technology becomes part of everyday care.

Imagine a VR rehabilitation solution designed to reduce therapists’ workloads. The pilot goes well. Safety and performance targets are met. The team has evidence that the technology works.

Then a hospital asks: how much staff time does it save? Is it easy to integrate into existing workflows? What impact is it going to have on patient reported outcomes?

The study cannot answer. Nobody measured it.

This example captured a central problem discussed during the VR Health Champions Thematic Group Meeting at IHT Conference’26 in Lisbon: a pilot can succeed on its own terms and still leave the case for adoption unfinished.

Held on 28 October 2026, in Lisbon, the session was titled “From Innovation to Adoption: Market Access and Reimbursement for Digital Health Solutions – Lessons from VR/XR”.

Michael Barngrover of XR4Europe moderated the discussion, with expert contributions from András Perényi of Syreon Research Institute and Maria Nascimento of Instituto Pedro Nunes. Through expert insights, practical examples and questions from participants, the meeting explored market access pathways, reimbursement strategies, evidence requirements and the barriers slowing the uptake of digital health solutions.

The format mattered. Designed around discussion and peer exchange, the Thematic Group Meeting gave participants space to examine how these challenges affect their own development decisions.

A recurring message emerged: developers need to think about the decisions their evidence will support while they can still shape the study.



The benefit you promise is the benefit you need to measure

For the rehabilitation solution in the example, reducing workload is part of the reason a hospital might introduce it. If the pilot measures safety and performance without examining staff time or workflow, that practical benefit remains an assumption.

The same issue applies to other claims. A solution intended to improve patient engagement needs evidence of engagement. A technology promising better treatment outcomes needs measures that can test that promise.

These questions affect what a healthcare provider can reasonably conclude from a study.

Safety and performance evidence addresses essential requirements. Evidence about time, workflows and patient experience helps explain what introducing the technology would mean for the people delivering and receiving care.

That is why the choice of endpoints matters so much. Before asking whether a pilot met its targets, developers should ask whether those targets capture the value they expect the technology to deliver.



No clinical investigation does not mean no validation

An early exchange addressed a question with direct consequences for development planning: if a formal clinical investigation is not required, how should a manufacturer validate its technology?

Maria Nascimento explained that the need for validation evidence remains.

“The technical documentation must still contain evidence of validation. Validation needs to show that the technology meets its intended purpose when used by the intended users in the intended environment. This requirement remains relevant whether or not a clinical investigation is mandatory.”



The discussion explored how appropriately designed usability studies could also collect endpoints relevant to validation, depending on the technology and applicable requirements.

For teams working with limited resources, that creates an important planning opportunity. A study may be able to answer several relevant questions if those questions are defined early enough.

The distinction requires care: usability work is not a universal substitute for clinical investigation. The practical lesson is to understand what evidence is needed before deciding how to collect it – i.e. one should start with the evidence gap, not with the study. So the clinical validation is not about doing more studies, but having a clear strategy about generating the right evidence, at the right time, for the right claims.



Who needs to be convinced – and of what?

A participant’s question about whether a new device must be better than products already on the market opened up a broader issue.

“Better” needs a reference point. Better for which patients? Compared with which treatment? Measured through which outcomes? And relevant to whose decision?

A manufacturer establishing safety and performance, a payer considering reimbursement and a hospital deciding whether to purchase a technology are assessing different aspects of the same product.

In publicly funded healthcare, the discussion also concerns how limited resources should be allocated. Clinical benefit, comparisons with current care, costs and wider value can all become part of that assessment.

Even a positive reimbursement decision leaves further work. Clinicians and institutions still need to integrate the solution into practice. User acceptance and practical implementation remain consequential.

For developers, this makes adoption a sequence of decisions that each need a convincing answer. Evidence collected for one stage may help with another, but that connection needs to be planned.



Digital technology does not automatically mean digital reimbursement

András Perényi introduced the VR Health Champions Market Access Landscape Report, developed to help innovators navigate reimbursement routes across European healthcare systems.

Its starting point was a practical information gap.

“Developers need to know whether reimbursement is possible in a particular country and, if so, which pathway, eligibility conditions and evidence requirements apply. The report aims to make that landscape easier to understand.”

Germany, France and Belgium featured in the discussion as examples of countries with more established dedicated approaches. Yet the existence of a digital health pathway does not establish that a particular VR/XR product is eligible.

Perényi highlighted three recurring considerations:

  • What delivers the therapeutic effect? Software may be the main therapeutic component, or the intervention may depend on specialised hardware.

  • Where is the technology used? Home use and use within a clinical service can lead to different access considerations.

  • How does it fit into treatment? A standalone intervention may be assessed differently from a tool embedded in a broader care pathway.

For immersive health developers, these distinctions can have substantial consequences. A hardware-dependent solution or a tool used within a clinical workflow may need to follow a traditional medical-device reimbursement route.

The access strategy therefore has to reflect the actual product and its intended use. Calling a solution “digital” does not resolve the question of how a healthcare system will fund it.

The costly question is the one asked after the study

Towards the close, the discussion returned to a familiar development pressure: teams concentrate on building the technology and postpone regulatory or market access questions.

The consequences may only become visible once a study is complete.

A team can have a substantial dataset and still lack an outcome or comparison needed for the next assessment. Collecting that missing evidence may require further work, additional funding and another opportunity to study the intervention.

A question about comparators brought the conversation to PICO: population, intervention, comparator and outcomes. Considering these elements early helps connect the study to its eventual purpose, including assessment against the current standard of care.

The experts acknowledged that startups cannot do everything at once. Their recommendation was to involve regulatory and market access expertise early where resources allow, while important choices can still be changed.

For a resource-constrained team, the value of that advice is concrete: make the evidence budget answer the questions that will matter later.



Key takeaways for VR/XR health innovators

  1. Design the pilot around the next decision. Identify who will assess, fund, purchase or use the solution, and what they need to know.

  1. Turn the value proposition into measurable outcomes. Claims about staff time, workflow, engagement or treatment benefit need evidence that tests them.

  1. Plan validation explicitly. When a clinical investigation is not required, determine which validation evidence is still needed to be generated and how it should be performed.

  1. Investigate reimbursement eligibility early. Software, hardware, setting of use and the product’s role in treatment can influence the available route.

  1. Choose the comparator before collecting the data. The relevant standard of care should inform the study design when future decisions require a comparison.

  1. Bring specialist advice in while it can change the plan. Early input can help prevent a completed study from leaving a critical question unanswered.

The VR Health Champions meeting connected these challenges through practical examples and participant questions. It showed why evidence planning, reimbursement and implementation need to be considered together, while developers still have room to act.

For the next VR pilot, that leaves one useful question:

If this study succeeds, what will a hospital know that makes it ready to say yes?

Comments