Medical schools & universities

A connected curriculum. A continuing patient.

Explore a simulation approach that links examination, interpretation, decision-making and follow-up across disciplines.

Institutional evaluation and co-design

Discuss your use case Explore the complexes

01 / Simulation architecture

Build continuity into learning.

Follow a patient through assessment, treatment and rehabilitation instead of treating each teaching session as an unrelated encounter.

Undergraduate and postgraduate learning objectives
Multimorbidity and multidisciplinary discussion
Patient communication and clinical handover

02 / Simulation architecture

Make reasoning visible.

The proposed review tools relate recorded actions to observations and modeled patient progression. Rubrics and outcome measures require educational validation.

Case-specific objectives and assessment design
Instructor review of actions and conversations
Repeatable cases with controlled variation

03 / Simulation architecture

Evaluate an initial specialty.

Orthopedics is the current prototype focus. Scope a limited pilot before extending to additional specialties or curriculum-wide deployment.

Define the learner group and objectives
Review technical and validation requirements
Agree an evaluation plan and success measures

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

Examine the sequence of care.

Synthetic observations and a recorded action timeline illustrate how after-action review could support a teaching discussion. This is an interface study, not a validated assessment instrument.

Concept studySynthetic observations · educational website illustration

14:02 / After-action view

Patient arrival

92bpm

The initial observations enter the illustrative record.

Fixed synthetic data, not a physiological model or clinical reference. Patient-state-derived analytics are a planned capability.

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