AESORYX / Technology

A connected simulation architecture.

MediVerse connects patient state, operational logic and role-aware intelligence with an immersive presentation layer. Each layer has a defined responsibility.

In development · Orthopedics is the initial prototype focus. Other complexes and advanced capabilities are planned.

01 / Simulation architecture

Intelligent Logic Twin

An authoritative operational state connects the institution's people, patient locations, resources and events.

  • World state and validated actions
  • Orders, rooms and resources
  • Persistent encounter history
02 / Simulation architecture

Human Physiological Twin

The planned patient model relates body systems, conditions, injury, medications, mobility and recovery.

  • Connected patient parameters
  • State-derived observations
  • Explicit model assumptions
03 / Simulation architecture

Cognitive & Social Twin

Characters combine identity, role, permitted knowledge, relevant memories and the responsibilities of a care team.

  • Role-aware dialogue
  • Knowledge and authority boundaries
  • Relationships and continuing encounters
Architecture in context

Three twins. One continuing world.

Explore the physiological, operational and cognitive layers that refer to the same patient and care context.

Concept studyThree interconnected twins · planned architecture
Human physiology: Cardiovascular, Respiratory, Metabolic, Neurological, Musculoskeletal, Renal connect to patient state.CardiovascularRespiratoryMetabolicNeurologicalMusculoskeletalRenalTWIN / 01PATIENT STATEState → observation → consequence
Layer 01

One connected human state.

The planned physiological twin connects body systems, injury, disease and recovery. Observations are intended to follow the simulated patient state.

All three layers refer to the same persistent patient and medical world.
The wider platform

Fifteen connected capabilities.

The six foundations above combine with nine further development areas. Their scope is described here; a production-ready institutional platform is not claimed.

07 / Platform direction

Persistent memory

Separate a person's identity, relevant conversational memory and the authoritative clinical record. Memory should remain scoped to the role and encounter.

Explore this capability
08 / Platform direction

Generative patients

The roadmap combines history, active conditions, risk factors and communication context into internally consistent patient configurations.

Explore this capability
09 / Platform direction

Functional medical devices

Planned controls, alarms and readings have defined relationships with simulated patient state rather than serving only as visual equipment.

Explore this capability
10 / Platform direction

Medical knowledge

Relevant knowledge must support the task, identify its source and respect the difference between simulation context and real clinical guidance.

Explore this capability
11 / Platform direction

Scenario intelligence

Configure events, complications, difficulty and time progression around a continuing patient identity. Broad educator tooling remains planned.

Explore this capability
12 / Platform direction

Simulation analytics

The review roadmap links observations, actions, conversations, escalation and resource use to instructor-defined objectives.

Explore this capability
13 / Platform direction

Authoring

Educators are intended to shape patients, facilities, teams, events and rubrics without editing Unreal Engine source code.

Explore this capability
14 / Platform direction

Institutional deployment

Cloud, private cloud and on-premises options require infrastructure, governance, support and security decisions for each institution.

Explore this capability
15 / Platform direction

Self-hosted AI

Local inference is present in the prototype. Streaming speech, multimodal perception and a production private deployment package are further work.

Explore this capability
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
01What is AESORYX?

AESORYX is the product ecosystem of Gatai Inc. (g-atai.com), encompassing MediVerse, a persistent medical-world application. The platform is currently in development, with an orthopedic prototype as its initial focus.

02What is MediVerse?

MediVerse is the application through which users enter the simulated medical world. Its intended architecture connects patients, intelligent people, facilities, functional devices and clinical workflows.

03What is an Intelligent Logic Twin?

It is the operational model of the medical world: people, patient locations, resources, permissions, orders and events. It determines what is happening and which actions may change state.

04What is a physiological twin?

It is a computational representation of a simulated patient’s connected physiological and clinical state. The current prototype uses synthetic orthopedic proxies; multi-system and clinically validated models are future work.

05How does AI medical simulation work?

An agent receives role-appropriate context and can explain or propose an action. Authoritative simulation logic validates important actions before they alter patient state. Conversation alone does not commit a clinical intervention.

06Can 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.

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.