Spatial interaction

Medicine at human scale.

High-fidelity Unreal Engine environments, people and equipment form the immersive presentation layer of MediVerse.

Desktop exploration and Meta hand-interaction foundation · hardware testing pending

Discuss your use case Explore the complexes

01 / Simulation architecture

Enter the environment.

The fresh prototype places three hospital campuses within a shared city and connects people to the simulation backend.

Desktop exploration and local dialogue
Shared geometry for a lighter environment
Selected medical equipment with grab components

02 / Simulation architecture

Designed for more than one interface.

The platform direction accommodates VR, controllers, hand tracking and supported specialist inputs. Availability depends on the integration and connected hardware.

Room-scale and spatial interaction
Controller and hand-input foundations
Body, gaze and specialist device integrations planned

03 / Simulation architecture

Presence serves the task.

Fine-grained interaction must connect to procedure logic and patient state. Visual fidelity alone does not establish procedural fidelity.

Explicit object and task contracts
Accessible desktop alternatives
Calibration and device-specific validation

A clear development boundary

Orthopedics is the initial prototype focus. Specialty scope, advanced physiology, institutional authoring and multiplayer describe the platform direction. No clinical validation or regulatory approval is claimed.

See what exists today

Architecture in context

A shared place to practice.

Connected departments give spatial interactions a workflow context. The schematic illustrates the intended facility architecture.

Concept studyMediVerse · connected facility schematic

Department 01

Emergency

Arrival → assessment

Triage, observation and escalation connect the arrival of a patient with the next appropriate team.

Care teams · assessment spaces · handovers

Illustrative layout. Department workflows are part of the planned specialty complex architecture.

Questions for an evaluation

Scope the model before deployment.

Define the clinical task, available hardware, intended learners and required evidence before deciding which capabilities belong in an institutional evaluation.

01Can multiple clinicians train together?

Mixed human and AI teamwork is part of the design. A synchronized multiplayer experience is planned; the current prototype provides shared-backend foundations rather than a completed multi-user product.

02Can hospitals create custom scenarios?

Educator authoring is planned for patients, conditions, objectives, teams, complications and rubrics. It is intended to reduce reliance on Unreal source changes, but a production authoring interface is not yet available.

03Can AESORYX run privately or on-premises?

Local inference is used in the current prototype. Private cloud and on-premises delivery are deployment directions to assess with institutions; a production deployment package has not been established.

04Is AESORYX clinically validated or a medical device?

No clinical validation, regulatory approval or clinical decision-support status is claimed. The current work is a simulation prototype. Clinical judgment, patient care and regulated device use require separate governance and evidence.

For institutions building what comes next

Build the next generation
of medical simulation.

Start with your specialty, your team and a concrete learning or research objective.

Request a demo Contact AESORYX