Notice. Illustration and research prototype. Not clinically validated, not a medical device, not for patient care. Example data are fictional.
Critical care simulator scenario shell · example content —

—

—

Run it plain first. Once the derived layer has been seen it cannot be unseen, so a second run with the dashboard is only informative in that order.

This scenario is an example, not validated content. The engine below — clock, physiology, rule checks, debrief — is general and carries no clinical claim. The scenario file asserts how a patient behaves and what the correct actions are, which is a clinical assertion and must be authored and approved by a clinician before any teaching use.
—

The patient

What has happened

What will you do?

The clock does not wait. This patient changes whether or not you act, which is the difference between a simulator and a case discussion.

—
of the rules met
—
to the first correct action
—
actions that made it worse

What the rules expected, and what you did

The debrief is the product, not the scenario. Every line above is a stated threshold with a timestamp — the same rules the clinical engines use, applied to what you actually did and when. Where you disagree with a rule, that disagreement is the useful output: it is captured, not corrected, because a rule deviated from repeatedly with consistent reasoning is telling you something about the rule.