Research institutions

Explore models. Examine assumptions.

Study how persistent patient state, role-aware agents and immersive presentation can be connected in reproducible simulations.

Research collaboration sought · no published validation claimed

Discuss your use case Explore the complexes

01 / Simulation architecture

Questions before claims.

Research priorities include state consistency, agent grounding, human factors, learning outcomes and the fidelity of patient and procedure models.

Reproducible simulation experiments
Transparent model assumptions
Independent clinical and educational review

02 / Simulation architecture

Medical-device development.

Functional-device simulation is a planned pathway for evaluating workflows, interface concepts and training interactions. It is not a substitute for device testing or certification.

Device-to-patient-state contracts
Usability and workflow experiments
Procedure-specific test environments

03 / Simulation architecture

Build evidence together.

AESORYX is seeking partners to help define protocols and evaluate relevant outcomes. No institutional customers or peer-reviewed results are represented here.

Scope a research question
Specify measures and comparators
Document limitations and findings

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

Make the model's assumptions visible.

A connected architecture creates testable questions about state consistency, observations and care context.

Concept studyThree interconnected twins · planned architecture

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.

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