There is a question that comes up in almost every meeting with a clinical team, usually right after the demo: what data do I actually get out of this?
It is the right question. And it deserves an answer in two halves — because what RVer records matters no more than what RVer, by design, refuses to do with it.
The rule that governs everything else
RVer's base product is a Class I Medical Device registered with Infarmed. That class is not an administrative footnote: it is what draws the boundary around what the system may do.
Under the European framework, health software falls, very broadly, into three bands:
- Not a device — wellness and lifestyle, with no medical purpose.
- Class I — has a medical purpose, but provides no information used for diagnostic or therapeutic decisions.
- Class IIa or above — provides information that feeds those decisions, or monitors physiological processes.
RVer is registered in the middle band, and that is where it intends to stay. A system that scored, compared against norms, flagged deviations or suggested courses of action would be supplying information for a clinical decision — a different device, in a different class, with a different conformity assessment and a different price for institutions.
So the internal rule is simple and not up for negotiation: RVer records; the team reads.
What the Companion app records
The Companion app is the panel the team uses to set up, follow and close each session. Every session leaves an objective record:
- who — the patient assigned to the headset for that session;
- when — date, start time and actual duration;
- what — the content chosen, and what was actually played;
- how it ended — completed, interrupted, or ended by the team;
- history — the same patient's sequence of sessions over time, so consistency and adherence are visible.
In practice this replaces "how did it go yesterday?" with a record that depends on neither memory nor report.
With a movement module active
When a headset has a movement module active, the record gains one more layer: hand position readings and, where the module applies, leg position readings. From those come repetition counts, range of movement and per-session performance.
It is worth being literal about what this is: these are position readings in space — movement numbers produced by the headset's sensors. They are not clinical measurements, they are not normalised against any population, they carry no thresholds, no grading and no judgement of any kind. They are raw material for the team to look at.
RVer Motion and RVer Neuro are modules under development, not yet covered by the Class I Medical Device registration, which covers the base product — the RVer video library. The base product bears the CE mark under MDR 2017/745.
The scales are yours — and that is how it has to be
This is usually the part that settles the conversation.
RVer provides no assessment instruments. It ships no built-in scales, does not administer them, does not score them and does not interpret them. What the platform provides is the field and the timeline: alongside the session record, the clinician logs the instrument they themselves chose, applied under their own rules and weighed by their own judgement.
The difference is the whole point: the instrument is the clinician's, the application is the clinician's, the reading is the clinician's. RVer's job is to make sure that record is stored, dated, attached to the right patient and there when the team needs it.
This is not a limitation dressed up as a virtue. It is what separates a system that helps a team organise its own work from a system that claims a clinical reading it has no business making.
What RVer does not do
So that nothing is left ambiguous — and because this is what teams need to be able to tell their own management and quality functions — RVer does not:
- score, grade or assign levels;
- compare the patient against norms, populations or reference values;
- flag deviations, raise clinical alerts or signal decline;
- suggest courses of action, exercises or therapeutic adjustments;
- assess function, capacity or status;
- diagnose, screen or triage.
RVer is not a diagnostic device and does not replace any clinical assessment or the team's decision.
Where the data stays
A patient's session record stays on the headset and inside the institution. It is not sent to RVer, it feeds no dashboard of ours, and it does not leave your perimeter. The institution is the controller of that data under its own GDPR framework; RVer keeps no copy of it.
What does travel is something else: technical information needed for updates and remote support of the equipment, and aggregated data about how the product behaves, which we use to improve it. None of that includes the clinical content of a session or the readings attached to a patient.
The short version, for the next meeting
RVer gives the clinical team an objective, dated record of what happened in each session — and, with a movement module active, hand and leg position readings. It also gives the clinician the right place to keep their own instruments alongside that record.
What it does not give is a reading. That is, and will remain, the team's.