A Mechanistic Resuscitation Framework.
Built to Execute Under Pressure.
The platform teaches clinicians to recognize threatening physiologic states, rank likely mechanisms, begin empirical stabilization, and continue assessing in parallel — first through organized written frameworks, then through real-time high-fidelity simulation.
Written Frameworks
The current product foundation. Structured clinical reasoning frameworks organized around state recognition, mechanism ranking, and encounter execution logic.
View DocumentsHigh-Fidelity Simulation
The execution layer. Connects the written framework logic to real-time patient encounter scenarios with timing, perceptual constraints, and realistic consequences. Not yet available.
See roadmap statusClinical knowledge and clinical performance are not the same thing.
Traditional medical education organizes content by diagnosis, body system, or protocol. Real resuscitation does not arrive in that order. Clinicians encounter destabilizing patients before diagnostic certainty exists, with incomplete information, under time pressure, while the patient continues to deteriorate and tasks accumulate faster than they can be completed.
What traditional teaching provides
- —
Isolated facts and disease scripts
- —
Algorithm fragments and protocol steps
- —
Topic-organized memorized content
- —
Knowledge assessed in controlled, low-pressure settings
What real acute care actually demands
- —
Action before diagnostic certainty exists
- —
Prioritization under time pressure with incomplete information
- —
Parallel task management while the patient continues to deteriorate
- —
Reasoning that adapts across staff, tools, and resource availability
State → Mechanism → Stabilization → Diagnosis
The platform is built around a specific clinical reasoning sequence. This sequence is not how most education is organized. It is how effective resuscitation actually works.
What physiologic state is threatening life?
Before diagnosis, before mechanism — identify what is destabilizing the patient right now. Respiratory failure, circulatory shock, neurologic deterioration, or a combination. The state drives the tempo.
What is most likely producing that state?
Rank the mechanisms generating the threatening state. This is not diagnosis — it is mechanism-based reasoning that allows stabilization to begin before certainty exists.
Begin low-regret empirical stabilization.
Initiate interventions that buy time across the ranked mechanisms. Continue assessment and intervention in parallel. The patient does not wait for the differential to narrow.
Narrow toward diagnosis and definitive care.
Only after the patient has an organized stabilization path does the model shift toward definitive diagnosis and pathway selection. Recognition and stabilization come first.
Written Frameworks
The written framework layer is not a reference library. It is the didactic compression of the platform's operating system — the organized clinical reasoning architecture that governs how the simulation layer is eventually executed. These frameworks are the current executable cognitive layer.
State recognition
Identify the threatening physiologic state across presentations, settings, and resource levels.
Mechanism ranking
Organize the most likely mechanisms producing that state — before certainty, without waiting.
Encounter organization
Structure the full encounter from doorway impression through disposition — not just the assessment phase.
Prioritization logic
Determine what acts first, what waits, and what can run in parallel as time and acuity evolve.
Resource-scalable reasoning
The framework logic applies whether the clinician is in an ED, ICU, transport environment, or austere setting.
Reassessment structure
Recognize whether interventions are improving or worsening the patient. The encounter continues after the first action.
High-Fidelity Simulation
Simulation is not a visual add-on to the framework layer. It is the executable form of the model — a perceptual-temporal clinical reasoning environment where the framework schema is tested under realistic constraints. Learners must perceive cues, act under time pressure, manage competing tasks, and detect whether their interventions are working.
Intended encounter elements — patient placed on monitor, vascular access obtained, medications drawn up and administered, assessments completed, team members coordinated, and task priority managed as the clinical picture evolves in real time.
Real-time execution
Medications drawn up. Lines placed. Equipment applied. Interventions take time. Time is not abstracted away.
Cue recognition before certainty
Subtle physiologic changes appear as they would clinically — not labeled, not flagged. Learners must perceive and interpret.
Action and information latency
Interventions do not produce instant feedback. Labs return. Responses develop. The encounter continues while waiting.
Parallel task management
Assessment, communication, intervention, and documentation compete for attention simultaneously.
Team coordination
Rescue, diagnostic, logistics, and communication lanes all operate in shared space with other team members.
Consequence modeling
Delay, misprioritization, and missed cues produce realistic physiologic consequences. Decisions have weight.
How Each Component Contributes
The platform is not a collection of disconnected products. Each component addresses a specific layer of the training model — from foundational schema through real-time execution and performance review.
Current — Available Now
Written Frameworks / Documents
- —
Compressed clinical reasoning architecture
- —
State and mechanism organization by domain
- —
Foundational encounter schema
- —
System-specific physiology, assessment, and treatment reasoning
- —
Bridge materials where systems interact
- —
Reusable reference layer across provider levels
In Development
Simulation / Phylux PathoSim
- —
Real-time execution of the framework operating logic
- —
Timing, logistics, and perceptual constraints
- —
Physiology-driven consequence modeling
- —
Team workflow and communication environment
- —
Telemetry-based performance measurement
- —
Structured debrief and replay
Applied Encounter Tools
Phylux Apps
- —
Encounter management and organization at the point of care
- —
Assessment structure and documentation support
- —
Framework logic operationalized for mobile use
- —
Designed to extend the written framework layer into encounter execution
This is not documents alone. It is not simulation alone.
The strongest educational result requires layering. Each layer addresses something the others cannot. Written frameworks build the schema. Simulation tests whether the schema holds under time and perceptual pressure. Hands-on components address tactile skills. Debrief closes the learning loop with measurable performance data.
Didactic Framework Layer
Written frameworks compress the platform's operating logic into organized, referenceable material. This is where the schema is built — the cognitive architecture that governs encounter thinking.
Digital Simulation Layer
Simulation translates the schema into real-time execution under perceptual and temporal constraints. This is where the schema is tested — where timing, cues, and consequences become the teacher.
Targeted Hands-On Components
Tactile procedural skills still require physical practice. Hands-on components address the elements that digital simulation cannot fully replicate — line placement, airway techniques, physical assessment.
Debrief & Telemetry
Simulation telemetry captures time to state declaration, time to first stabilizing action, mechanism ranking changes, and response-recognition latency. Structured debrief closes the learning loop.
Why the Combination Matters
Knowing what to do in a high-acuity encounter is not the same as being able to do it when time is short, information is incomplete, the team needs direction, and the patient is still deteriorating. The hybrid model exists to close that gap — to move from mechanistic schema to executable real-time clinical action.
Frameworks provide
The invariant operating logic — the clinical reasoning architecture that governs how a high-acuity encounter should be structured, regardless of setting or resource level.
Simulation provides
Execution under realistic constraints — timing, perceptual demands, logistics, team communication, and the consequences of delay or misprioritization.
Together they
Move the learner from knowing the correct sequence to being able to execute it in real time, under pressure, with an actual patient deteriorating in front of them.
Not a clinical reference library. Not a simulation for its own sake.
Organized around states and mechanisms — not diagnoses
Diagnosis is the destination, not the starting point. The model teaches clinicians to identify threatening states and rank mechanisms first, so stabilization can begin before certainty.
Low-regret stabilization before certainty
The framework teaches interventions that hold across multiple ranked mechanisms. Clinicians act without waiting for a confirmed diagnosis — because real patients do not wait either.
Time treated as a first-class variable
The simulation layer makes timing, delay, and information latency teachable. Response time, time to first stabilizing action, and recognition latency are measurable outcomes.
Resource-scalable across care environments
The framework logic is designed to work in the ED, ICU, rapid response, EMS, transport, and austere environments. The operating model does not change — the resources available do.
Physiology-driven rather than protocol-driven
Protocols compress reasoning for high-frequency scenarios. This platform teaches the underlying physiologic reasoning so clinicians can apply it when protocols do not cover the situation.
Team-based by design
The platform models care as it actually occurs — with rescue, diagnostic, logistics, and communication lanes operating simultaneously. Team structure is part of the educational model.
Transparency
See what's live, what's in progress, and what's planned.