How are patient handoff procedures modeled between CASEVAC and Role 2 facilities?

Patient handoff simulation models the structured transfer of medical authority and information between echelons of care using the MIST (Mechanism, Injuries, Signs, Treatment) and SBAR (Situation, Background, Assessment, Recommendation) frameworks. When a simulated patient arrives at the Role 2 battalion aid station node in the simulation, the trainee who conducted the evacuation must deliver a structured verbal handoff report to the receiving medical officer simulation character. The simulation evaluates completeness of the MIST report against the injury and treatment data recorded during the point-of-injury and en route care phases: omitting the treatment given field (which medications were administered, tourniquet time) is a specific error that the simulation flags because it directly affects Role 2 treatment decisions. Documentation simulation requires the trainee to complete the DD Form 1380 (TCCC Card) or NATO equivalent at the point of injury and to transfer it with the patient -- the simulation checks that the documentation was completed before the evacuation phase and that the handoff verbal report is consistent with the written record.

What C2 data formats does MEDEVAC simulation software use for interoperability?

MEDEVAC simulation platforms designed for integration with broader command and control environments typically use MIL-STD-2525 symbology for casualty and medical unit symbols on the COP layer, Variable Message Format (VMF) or NATO message catalogue (APP-11) medical message types for machine-to-machine casualty reporting, and HL7 FHIR military profile extensions for electronic patient record exchange between Role 1 and Role 2 simulation nodes. The 9-line MEDEVAC request is modeled in some platforms as a structured data message (rather than only a voice format) to enable automated parsing and COP update, reflecting the direction of operational MEDEVAC C2 systems toward digital request transmission. Simulation environments that federate across distributed training locations use DIS or HLA interfaces to synchronize casualty state between nodes -- when a MEDEVAC simulation node at one training location accepts a patient, the corresponding entity in the federated COP disappears from the requesting unit's display at the remote location.

What after-action review metrics does MEDEVAC simulation automatically compute?

Automatic AAR metrics computed by MEDEVAC simulation platforms include: time to first tourniquet from time of injury (T1TK), time to 9-line transmission from time of injury, 9-line field error rate by line number, triage category accuracy rate (percentage of casualties correctly categorized versus ground truth), LZ selection score (composite of slope, obstacle, and threat exposure criteria), TCCC task sequence error rate per task type, time from casualty event to evacuation departure (EVAC delay time), and patient handoff completeness score. These metrics are computed per trainee and per scenario run, enabling comparison across training cohorts and longitudinal tracking of individual improvement. The simulation generates a training transcript for each run that annotates the timeline with decision point markers -- moments where the trainee deviated from the optimal decision path -- and links each deviation to the relevant doctrine, standard operating procedure, or training objective. The transcript is exportable for integration with learning management systems and unit training records.

How does night and degraded visibility MEDEVAC simulation differ from daylight scenarios?

Night and degraded visibility MEDEVAC simulation introduces sensor-dependency constraints that are absent from daylight scenarios. LZ marking procedures shift from visual panel placement to IR strobe, IR chemlight, and laser marking methods visible only through night vision or FLIR systems, and the simulation requires the trainee to select and execute the appropriate method for the aircraft equipment profile specified in the scenario. Casualty assessment in low-visibility conditions models the reduced accuracy of visual triage cues -- skin color, wound appearance -- and requires the trainee to rely more heavily on tactile assessment, pulse palpation, and the capillary refill test rather than visual signs. Communication procedures in night scenarios include coordination of aircraft approach timing to minimize the window during which the LZ is exposed, and the simulation scores whether the trainee sequenced the ground-to-air communication to reduce the aircraft's exposure time. FLIR-guided approach simulation -- where the aircraft crew is using thermal imaging rather than visual reference -- models the additional LZ preparation requirements: hot spots from fires or vehicle engines adjacent to the LZ can mask the patient heat signature and must be managed before the aircraft arrives.

What certification standards does MEDEVAC training simulation support?

MEDEVAC training simulation platforms developed for Western military use are typically aligned to Tactical Combat Casualty Care (TCCC) guidelines published by the Committee on Tactical Combat Casualty Care (CoTCCC), NATO STANAG 2068 (Medical Support to Operations) for interoperability standards, FM 4-02.2 (Medical Evacuation) for US Army evacuation doctrine, ATP-10(B) Allied joint doctrine for medical support, and Joint Theater Trauma System clinical practice guidelines for care-under-fire, tactical field care, and tactical evacuation care phases. Some platforms support NAEMT TCCC course competency verification by mapping simulation task completions to the NAEMT competency checklist and generating a training record suitable for submission to unit training management systems. Military occupational specialty (MOS) qualification maintenance for 68W (Combat Medic Specialist) and equivalent roles in partner nations increasingly accepts structured simulation hours as part of the continuing education requirement between annual skills verification events.

How does MEDEVAC simulation train the requesting unit versus the medical crew?

MEDEVAC simulation software typically operates in two distinct training modes targeting different audience roles. Requesting unit mode trains the combat medic or non-medic CLS (Combat Lifesaver) in the point-of-injury care sequence, casualty assessment, 9-line request composition, LZ preparation, and patient loading procedures -- the ground side of the MEDEVAC mission. Medical crew mode trains flight medics and crew members in the flight planning inputs derived from 9-line content, approach and departure route selection, onboard patient assessment, en route care protocols, and handoff at the receiving facility. Some platforms support simultaneous multi-role simulation where a ground team trainee and a crew trainee interact through the simulated radio net and share the patient data record in real time, enabling the full communication loop between requesting unit and MEDEVAC element to be exercised. The ground-crew interaction is where the most common procedural errors occur in real operations -- mismatched LZ coordinates, ambiguous marking method descriptions, failure to confirm patient count before aircraft commitment -- and the multi-role simulation mode is the only training format that reliably surfaces these coordination failure modes before they occur operationally.

What role does AI play in generating adaptive MEDEVAC training scenarios?

AI-driven scenario generation in MEDEVAC simulation applies adaptive difficulty adjustment based on the trainee's performance history. The system tracks error patterns across multiple simulation runs -- if a trainee consistently misclassifies tension pneumothorax as a standard chest wound during triage, the scenario generator increases the frequency of chest injury scenarios and varies the presentation to require discrimination between pneumothorax, hemothorax, and open chest wound presentations. Casualty generation parameters that adaptive systems can modulate include injury severity distribution, time pressure (number of casualties arriving per unit time), information completeness (degraded or fragmented initial casualty reports), environmental complexity (simultaneous threats requiring care-under-fire protocols), and communication disruption (simulated radio interference requiring procedural adaptation). The AI system also generates after-action scenario briefs that explain the clinical decision rationale behind each scenario's optimal solution path, providing the trainee with a learning explanation rather than just a performance score. This moves the simulation toward formative assessment -- supporting learning during practice -- rather than purely summative assessment that measures competency at a point in time.

How does pickup zone security assessment get simulated in MEDEVAC scenarios?

Pickup zone (PZ) security assessment simulation models the threat geometry evaluation required before a unit commits to activating a PZ for rotary-wing operations. The trainee is presented with a tactical situation map showing the PZ location, the positions of known and suspected threat elements, the terrain masking available for approach and departure corridors, and the approximate engagement ranges of the threat weapons systems in the scenario. They must assess whether the PZ is secure (no threat within direct fire range), threatens are suppressed, or the PZ is hot (active threat engagement). Each assessment drives a different subsequent action: a secure PZ proceeds with standard MEDEVAC procedures, a suppressed-threat PZ requires coordination of a fire support plan to maintain suppression during the approach window, and a hot PZ requires either a shift to CASEVAC using organic platforms or a request for armed escort for the MEDEVAC aircraft -- both of which have their own simulation branches. Line 6 of the 9-line request (security at PZ) is specifically evaluated for accuracy against the simulated threat picture, and trainees who report a secure PZ when threat elements are within engagement range receive a flagged error that cascades into the outcome model as increased aircraft vulnerability during the simulated approach.

What MEDEVAC simulation features support distributed training across multiple locations?

Distributed MEDEVAC simulation features support training events where requesting unit trainees, medical crew trainees, and exercise control staff are at separate geographic locations connected over a wide-area network. The federated casualty data model ensures that when a requesting unit trainee at Location A creates a casualty record and initiates a 9-line request, the MEDEVAC crew trainee at Location B receives the request on the simulated MEDEVAC net with appropriate propagation delay and radio quality degradation applied. Shared synthetic environment rendering ensures that both parties see geometrically consistent representations of the LZ, the approach corridor, and the casualty location. Exercise control staff at a third location have visibility into all simulation nodes simultaneously and can inject scenario modifications -- change the threat picture, add new casualties, degrade communications -- that affect all participants simultaneously. Network synchronization latency below 200 milliseconds is typically required for the voice and data exchange in MEDEVAC simulation to remain tactically realistic; higher latency values distort the communication timing patterns that trainees are expected to learn.

How does medical logistics simulation integrate with MEDEVAC training?

Medical logistics integration in MEDEVAC simulation generates consumption events from the treatment actions performed during training scenarios. When a trainee administers a simulated blood product, tourniquet, hemostatic agent, or airway adjunct during a TCCC task sequence, the simulation records the class VIII (medical materiel) consumption and feeds it to the medical logistics planning module. This integration allows the medical logistics section to practice resupply request generation -- DA Form 2765 class VIII requests or logistics status reports -- based on the consumption generated by ongoing simulated medical operations rather than from a static scenario inject. Mass casualty scenarios that generate high consumption rates in a short time window create shortage conditions in the logistics simulation that require the S4 medical officer to prioritize resupply and manage allocation across the task force's medical elements. The integration connects MEDEVAC operational training with the medical supply chain planning cycle, which is typically trained in isolation from the point-of-injury and evacuation procedures it supports.

What data outputs does MEDEVAC simulation produce for training management systems?

MEDEVAC simulation platforms produce structured training data exports for integration with unit training management systems and learning management platforms. Standard export formats include xAPI (Experience API, also called Tin Can) statements that describe each significant training event -- task initiated, task completed, error committed, skill score achieved -- in a format compatible with LRS (Learning Record Store) backends used by military training management systems. Per-scenario completion records include trainee identifier, scenario identifier, start and end time, all task scores, error log, and a composite competency rating against the defined standard for each training objective. Aggregate training reports summarize performance trends across a training cohort over a defined period, identifying tasks where the cohort consistently performs below standard and generating recommended additional training prescriptions. These outputs enable medical readiness officers to track individual medic certification status, identify training gaps at the unit level, and allocate simulator time to the highest-priority skill areas -- replacing the manual tracking approaches that historically relied on instructor recall and paper training records.

How does MEDEVAC simulation software model care-under-fire versus tactical field care phases?

The TCCC three-phase model -- Care Under Fire (CUF), Tactical Field Care (TFC), and Tactical Evacuation Care (TACEVAC) -- is implemented in simulation as distinct scenario phases with different permitted intervention sets and time constraints. The CUF phase simulation applies an ongoing fire suppression event that restricts the trainee to the minimum safe intervention set: direct the casualty to return fire if able, apply tourniquet to life-threatening extremity hemorrhage, move the casualty to cover. The simulation flags any attempt to perform interventions outside the CUF-permitted set as a doctrinal error -- attempting a full wound assessment while under simulated fire is recorded as a task failure because it increases exposure time without sufficient clinical benefit to justify the risk. The TFC phase simulation removes the immediate fire threat and expands the permitted intervention set to the full TCCC assessment and treatment protocol, including airway management, hemorrhage control reassessment, IV access, fluid resuscitation, and hypothermia prevention. Phase transition in the simulation is driven by scenario events -- a simulated suppression report, an objective secured message -- that the trainee must recognize and act on to transition their care approach, testing situational awareness alongside clinical skill.

How is the simulation clock managed for MEDEVAC time-critical standards?

MEDEVAC simulation time management implements two clock modes: real-time mode where simulation events unfold at actual elapsed time (used for full-scenario immersive training), and accelerated time mode where the scenario progresses faster than real time (used for table-top review and decision training where the physical procedures are not being practiced). In real-time mode, the simulation tracks elapsed time from the time-of-injury event for each casualty and computes running survival probability adjustments based on the time-dependent wound models. The instructor console displays a per-casualty countdown showing the clinical window for each priority intervention -- time-to-exsanguination for uncontrolled hemorrhage patients, time-to-airway compromise for airway-injury patients -- giving the instructor visibility into whether the trainee is recognizing urgency correctly. Standard benchmarks enforced by the simulation include the ten-minute Platinum period from injury to hemorrhage control, the one-hour Golden hour from injury to surgical care for penetrating abdominal trauma, and the MEDEVAC response time standards by evacuation precedence (15 minutes for Urgent, one hour for Priority, four hours for Routine) that are measured from time of 9-line transmission to simulated aircraft arrival at the PZ.

What does MEDEVAC coordination simulation train differently from tabletop exercises?

Simulation-based MEDEVAC coordination training differs from tabletop exercises in three operationally significant ways. First, simulation applies realistic time pressure: a tabletop exercise can pause to discuss a decision, whereas the simulation continues accumulating casualty deterioration time while the trainee deliberates, creating the cognitive load associated with real MEDEVAC decision-making. Second, simulation generates information fidelity problems -- degraded radio communications, incomplete initial casualty reports, conflicting grid references from different observers -- that tabletop discussions typically eliminate by providing clean, complete scenario information. Third, simulation captures individual performance data at the task level rather than producing a group-level discussion record. A tabletop exercise reveals how a team reasons through MEDEVAC coordination; simulation reveals what each individual actually does under time and information pressure. The two training modalities are complementary: tabletop exercises develop shared mental models and team coordination procedures; simulation develops individual procedural competency and stress inoculation for the time-pressure and information-overload conditions that characterize actual MEDEVAC operations.

How does simulation handle the MEDEVAC request authentication process?

MEDEVAC request authentication simulation models the challenge-and-response authentication procedures used on military radio nets to prevent spoofed MEDEVAC requests. The simulation requires the trainee to authenticate with the controlling headquarters before the MEDEVAC request is accepted, using the authentication table format specified in the scenario communications plan. Authentication simulation covers both sides of the process: trainees practicing as the requesting unit must correctly respond to the authentication challenge from the MEDEVAC net control station; trainees practicing as the MEDEVAC net control station must correctly issue the challenge and verify the response before relaying the request to the aircraft. The simulation records authentication failures -- incorrect responses, failure to authenticate when required, or transmission of the 9-line before authentication is complete -- as security procedure errors that are reported in the AAR. In real operations, a failed authentication may cause a MEDEVAC request to be refused or delayed while the requesting unit re-establishes identity, directly affecting patient outcome; the simulation makes this consequence visible by modeling the delay and its effect on the casualty survival curve.

How are CASEVAC vehicle loading procedures trained in simulation software?

CASEVAC vehicle loading simulation models the patient preparation, loading sequence, and en route care procedures for evacuation using organic tactical vehicles -- wheeled and tracked -- rather than dedicated medical aircraft. Vehicle-specific modules model the physical constraints of each platform type: the loading angle and ramp approach for wheeled ambulances, the hatch and interior space limitations of armored personnel carriers configured for casualty carry, the tie-down point locations and litter configuration options for different vehicle types. The simulation requires the trainee to select the correct patient positioning for each wound type -- head-elevated for head injuries, recovery position for unconscious patients, flat with legs elevated for hemorrhagic shock -- and to secure the patient to the vehicle's litter system using the appropriate restraint method. En route care simulation for CASEVAC models the limited intervention capability of non-medical crew during movement: the trainee must decide which monitoring and treatment actions are feasible during vehicle movement on degraded terrain and which must wait until the vehicle stops or the patient reaches the Role 1 aid station. Documentation during CASEVAC -- completing and transferring the TCCC card with the patient -- is enforced by the handoff simulation at the receiving facility.

What language and communication training does MEDEVAC simulation support for multinational operations?

Multinational MEDEVAC simulation supports language training in two ways. First, standardized terminology training enforces the use of NATO-standard MEDEVAC terminology and phonetic alphabet across all communication simulation exercises, ensuring that trainees from different national contingents use a common vocabulary that is unambiguous across language backgrounds. Second, some platforms include scenario variants where a simulated MEDEVAC control station or aircraft crew operates in a different national military communication culture, requiring the requesting unit trainee to adapt their request format to the receiving element's expectations -- a training challenge that reflects the real coordination complexity in multinational task forces. STANAG 2068 and APP-10 Allied joint logistic doctrine define the minimum interoperability standards for multinational medical support, and simulation platforms aligned to these standards include scenario validation that checks 9-line format against the STANAG-compliant format rather than a single national standard. This is particularly relevant for training combined joint task force medical staff who will coordinate MEDEVAC assets from multiple contributing nations, each with slightly different communication procedures and medical capability declarations.

What are the primary fidelity requirements for a MEDEVAC training simulation platform?

Primary fidelity requirements for MEDEVAC training simulation fall into four categories. Procedural fidelity requires that the simulation accurately represent the step sequences, decision algorithms, and communication procedures defined in current TCCC guidelines, evacuation doctrine, and medical SOP -- an outdated tourniquet application sequence or a deprecated 9-line format will train incorrect procedures that must be unlearned operationally. Temporal fidelity requires that time-critical standards -- tourniquet application within three minutes of injury, 9-line transmission within ten minutes, aircraft response time by precedence -- be enforced by the simulation in real time during immersive training modes. Information environment fidelity requires that the simulation present the same quality of information available in actual MEDEVAC operations: incomplete initial casualty reports, radio interference, conflicting grid references, and degraded communications that require adaptive procedures. Consequence fidelity requires that trainee decisions produce outcomes that accurately reflect clinical reality -- a delayed tourniquet application must produce a visibly worse survival probability for the simulated patient, not just a score deduction on a checklist, so trainees develop appropriate urgency for each procedure. The combination of these four fidelity dimensions determines the degree to which trained behavior transfers to operational MEDEVAC performance.

How does MEDEVAC simulation software handle mass casualty triage discipline validation?

Mass casualty triage discipline validation in simulation requires the trainee to complete an initial global sort of all casualties before committing to treatment of any individual patient -- and the simulation enforces this sequentially. When the MASCAL scenario initiates, the trainee is presented with the full casualty set and must conduct a rapid sort, categorizing each patient as immediate (Red), delayed (Yellow), minor (Green), or expectant (Black) based on a 30-to-60 second assessment. The simulation blocks the trainee from initiating treatment on Patient A until the sort of all other patients in the scenario is complete or until the trainee explicitly accepts a simulation prompt acknowledging they are deviating from the sort sequence. After the sort phase is complete, the simulation releases the treatment phase and evaluates the trainee's treatment prioritization against the optimal sequence -- a trainee who correctly sorted all patients but then began treatment on a delayed (Yellow) patient before addressing immediate (Red) patients receives a triage discipline error for the treatment phase. The AAR report shows the trainee's actual treatment sequence against the optimal sequence and computes the aggregate survival outcome difference between the two sequences, making the cost of prioritization errors visible in clinical terms.

What integration patterns connect MEDEVAC simulation to joint fire support coordination?

MEDEVAC and joint fire support coordination simulation integration addresses the fire coordination requirements that govern when and how MEDEVAC aircraft can transit a fire support coordination line (FSCL) or cross a coordinated fire line (CFL). When a trainee submits a 9-line request that requires an aircraft approach through an active fire support coordination area, the simulation requires the trainee or the medical officer trainee to submit a coordination request to the fires element simulation node -- halt or shift fires for the duration of the MEDEVAC approach and departure window. The fires coordination module models the approval workflow and the time required to implement a fire mission halt, introducing a delay variable that affects MEDEVAC response time in the scenario outcome calculation. SEAD (Suppression of Enemy Air Defenses) coordination for MEDEVAC aircraft operating in a threat environment models the additional planning requirement to request SEAD support before the aircraft transits a known air defense threat envelope -- a planning step that adds to the evacuation timeline and must be factored into the urgency assessment when the trainee determines whether to request MEDEVAC or accept the delay and transition to CASEVAC using ground platforms.

How do simulation platforms model the MEDEVAC aircraft capability declaration process?

Aircraft capability declaration simulation models the information exchange between the requesting unit and the MEDEVAC scheduling authority that determines which aircraft asset is tasked to a specific MEDEVAC request. The simulation requires the requesting unit trainee to correctly transmit Line 4 (special equipment required) because this field drives asset selection -- a request for hoist capability, blood products, or a ventilator-equipped aircraft must be correctly specified or the simulated scheduling authority tasks an aircraft without the required capability. The simulation generates a capability mismatch error when Line 4 is incorrect relative to the clinical requirements of the patient set described in Lines 3 and 5. Aircraft capability profiles in the simulation reflect actual rotary-wing medical platforms: UH-60L Black Hawk (MEDEVAC configured), CH-47F Chinook (heavy casualty carry), and equivalent platforms from partner nations for multinational exercise scenarios. Crew composition simulation models the medical qualification of the crew -- whether a flight physician, flight nurse, or flight medic is on board -- and adjusts the en route care capability accordingly, affecting the outcome model for patients requiring advanced interventions during transport.

What user interface design principles apply to field-use MEDEVAC simulation clients?

Field-use MEDEVAC simulation client interfaces apply the same ruggedized-use design principles as operational medical field applications. Sunlight-readable high-contrast display modes ensure the interface remains usable in direct sunlight without display brightness that compromises night adaptation in low-light scenarios. Glove-compatible touch targets are sized to at least 10mm x 10mm to support accurate input while wearing standard patrol gloves. Offline operation with background synchronization allows trainees to conduct scenario exercises in radio-denied or network-denied environments, with the simulation state synchronizing to the central AAR server when connectivity is restored. Audio feedback supplements visual indicators for critical events -- casualty deterioration alerts, aircraft arrival notifications -- because the trainee's visual attention should be on the simulated patient and environment rather than on the device screen. Single-hand operable navigation supports scenarios where the trainee's second hand is simulating a treatment task on a mannequin. These interface requirements are validated against actual field use conditions by deploying the client to training events in realistic outdoor environments before operational release, following the same field-validation process applied to operational medical field applications.

How does blood type and compatibility matching appear in MEDEVAC training simulation?

Blood type and compatibility simulation in MEDEVAC training addresses the administration of blood products at point of injury and en route, particularly low-titer group O whole blood (LTOWB) administration that is now included in forward TCCC protocols for hemorrhagic shock management. The simulation presents each simulated casualty with an assigned blood type as part of the casualty data, and when a trainee selects a blood product administration intervention, the simulation requires the trainee to select the appropriate product and verify compatibility against the casualty's blood type record. Incompatibility errors -- administering an ABO-incompatible product -- are recorded as critical errors that directly invoke the simulation's adverse outcome model for that patient. Walking Blood Bank (WBB) coordination scenarios train the additional procedural step of soliciting pre-screened donors from the unit's non-medical personnel when typed blood products are unavailable: the simulation presents a roster of unit members with their pre-screened blood type and infectious disease screening status, and the trainee must identify compatible donors, conduct the brief donor history screening, and manage the collection and administration workflow -- a coordination task that requires communication with the unit leadership simultaneously with the patient care simulation.

How does MEDEVAC simulation handle the decision between requesting air versus ground evacuation?

Air versus ground evacuation decision simulation trains the clinical and tactical factors that determine the appropriate evacuation platform. Clinical factors modeled by the simulation include patient injury type and stability -- patients with head injuries requiring minimal movement, patients in respiratory distress who benefit from altitude restrictions, patients with penetrating abdominal trauma who need the fastest available transit to surgical care. Tactical factors include threat density along ground routes, LZ availability and security, weather conditions affecting rotary-wing operations, and the availability of organic ground platforms. The simulation presents scenarios where air evacuation is the clear optimal choice (accessible LZ, high clinical urgency, available aircraft), scenarios where ground evacuation is appropriate (air threat precludes rotary-wing operations, stable patient with nearby Role 2 access), and scenarios where the decision is genuinely ambiguous and requires the trainee to weigh multiple competing factors. The AAR review for these decision scenarios presents the trainee's reasoning alongside the clinical and tactical factors, using the outcome model to show whether the chosen platform provided better or worse patient outcome than the alternative -- training the decision framework rather than establishing a fixed rule.

What are the key differences in simulation requirements between Role 1 and Role 2 training?

Role 1 (unit-level, point-of-injury) and Role 2 (battalion aid station / forward surgical) simulation training address different competency sets with different platform requirements. Role 1 simulation focuses on time-critical intervention skills (tourniquet, airway, wound packing), the 9-line request workflow, LZ coordination, and patient packaging for evacuation -- tasks performed by combat medics and CLS personnel in forward environments with minimal equipment. The simulation interface for Role 1 must support high task throughput at the individual patient level and real-time communication simulation for MEDEVAC request procedures. Role 2 simulation focuses on patient reception and triage of multiple casualties arriving from multiple evacuation platforms simultaneously, surgical prioritization under resource constraints, blood product management, and mass casualty surge capacity -- tasks performed by medical officers and senior medics in a more resource-rich but operationally chaotic environment. Role 2 simulation requires a multi-patient simultaneous management interface, integration with the medical logistics simulation for blood product and supply tracking, and after-action reporting at the population level rather than the individual patient level. Some platforms model both roles in a linked simulation where Role 1 trainee actions directly affect the patient state that the Role 2 trainee receives, creating a continuous chain-of-survival simulation that spans from point of injury to surgical care.

How does simulation software train the pick-up zone (PZ) to aircraft crew communication loop?

PZ-to-aircraft communication simulation models the sequential information exchange between the ground element and the inbound MEDEVAC aircraft from initial contact to patient loading. The exchange sequence follows a standard protocol: initial contact call from the aircraft to the ground element on the pre-briefed frequency, ground element confirmation of frequency and PZ status, initial assessment report from the ground element (PZ status, number of patients, marking method active), aircraft confirmation of PZ marking acquisition, ground element heads-down notification (personnel clear of rotor arc), patient loading coordination, and departure confirmation with destination handoff brief. The simulation evaluates each step in the sequence, timing the interval between the aircraft's marking acquisition call and the ground element's response (a delay here indicates the ground element is not monitoring the radio while preparing patients), and flagging any deviation from the protocol sequence. Common errors modeled include activating PZ marking before the aircraft is within acquisition range -- increasing the exposure time of the PZ marking -- and transmitting the heads-down notification before all patients are positioned for loading, forcing the aircraft to extend its on-ground time. These protocol timing errors are invisible in tabletop training but surface clearly in simulation where the aircraft's simulated approach and dwell time is modeled against the communication sequence the trainee executes.

Training & Wargaming

MEDEVAC and CASEVAC training simulation software

Q: How does MEDEVAC simulation integrate with command post exercise and COP feeds?

Integration between MEDEVAC simulation and broader command post exercise (CPX) environments occurs through a casualty status feed that updates the unit's medical tracking layer on the common operational picture. When a simulated casualty event is generated by the CPX scenario engine, the MEDEVAC simulation module receives the event and creates a casualty record with the patient's simulated grid location, wounding mechanism, and time of injury. This record appears in the medical tracking layer visible to the S4 medical section and the battalion aid station simulation node. As the trainee progresses through the MEDEVAC request workflow, triage, and evacuation simulation, the casualty record status updates in the COP: from 'wounded' to 'triaged' to 'MEDEVAC requested' to 'en route' to 'at Role 2.' The logistics module simultaneously generates a blood product consumption event and a resupply request that feeds the medical logistics planning simulation. This integration ensures that MEDEVAC training does not occur in isolation from the tactical and logistical context that drives medical evacuation decisions in actual operations.

By Corvus Intelligence Engineering Team · About the team →

June 24, 2026 10 min read

Medical evacuation training occupies an unusual position in military readiness programs: the skills it develops are life-critical, the procedures are tightly standardized, and the consequences of procedural failure are irreversible. Yet training those skills at realistic fidelity -- coordinating helicopter approaches under simulated threat, executing 9-line MEDEVAC requests on degraded radio nets, applying tourniquet and wound packing interventions in time-constrained environments -- requires either live aircraft, live patients, and live radio networks, or simulation software capable of approximating those conditions with enough fidelity to produce genuine skill transfer. This article examines how MEDEVAC and CASEVAC training simulation software addresses that challenge: how it models the 9-line MEDEVAC request workflow, implements triage algorithms for single-casualty and mass casualty scenarios, integrates with Tactical Combat Casualty Care (TCCC) task trainers, simulates helicopter and ground vehicle coordination procedures, feeds medical status data into broader C2 simulation environments, and produces after-action review packages that connect individual performance to simulated patient outcome.

The training problem: realistic MEDEVAC without live aircraft

The foundational challenge of MEDEVAC training simulation is fidelity: what must the simulation reproduce accurately to produce skill transfer, and what can be simplified without undermining training value? The literature on simulation-based medical training identifies three fidelity dimensions that most influence transfer: procedural fidelity (whether the simulation requires the trainee to execute the correct sequence of steps), temporal fidelity (whether the simulation enforces the time constraints that govern real MEDEVAC decisions), and information environment fidelity (whether the simulation presents the same quality and completeness of information available in actual operations).

Live aircraft training satisfies all three dimensions but introduces cost, availability, and safety constraints that limit training volume. A medical evacuation helicopter crew logs a finite number of training flight hours per year; the requesting unit's medics may interact with live MEDEVAC assets only a handful of times before deployment. The procedural repetition required to build reliable skill -- dozens of 9-line requests, dozens of LZ coordination exercises -- cannot be achieved at the frequency needed through live flight training alone.

Simulation software fills the volume gap by allowing the requesting unit to execute hundreds of MEDEVAC scenarios against a simulated aircraft, simulated communications environment, and simulated casualty population. The critical design question is where to invest simulation fidelity. Virtual reality military training platforms demonstrate that visual immersion improves stress inoculation but does not necessarily improve procedural accuracy more than well-designed screen-based simulation -- the limiting factor for MEDEVAC skill transfer is typically the communication protocol and the decision algorithm, both of which screen-based simulation can represent with high fidelity at much lower cost than full immersive environments.

Role-player versus AI casualty is a specific design choice that affects training outcomes. Human role-players who portray casualties can respond adaptively to trainee actions, ask questions that the script did not anticipate, and model physiological deterioration in ways that require the trainee to re-evaluate. AI-driven casualty simulation applies a defined injury model that responds deterministically to interventions -- tourniquet applied at three minutes produces outcome X; applied at ten minutes produces outcome Y -- which enables automated scoring but reduces the adaptive richness of the training interaction. Most production platforms use AI casualty models for high-volume solo training and reserve human role-players for capstone exercises where the adaptive interaction is the primary training value.

9-line MEDEVAC request workflow simulation

The 9-line MEDEVAC request is the primary instrument by which ground forces communicate casualty information to evacuation authorities. Its nine fields encode the minimum information a MEDEVAC crew needs to plan an approach, prepare for the patient load, and coordinate the mission: pickup zone location, radio contact parameters, patient count and precedence, special equipment requirements, patient mobility status, PZ security assessment, marking method, patient nationality and status, and contamination information. Errors in any field impose real operational cost -- an incorrect grid reference sends the aircraft to the wrong location; an omitted hoist requirement causes an aircraft without the capability to arrive at a site where it cannot extract the patient.

Simulation of the 9-line workflow presents the trainee with a scenario briefing that includes all the information needed to compose a correct request, and then requires the trainee to compose and transmit the request without referencing a template. The evaluation module scores each field independently:

LINE  FIELD                      EVAL CRITERIA
----  -------------------------  -----------------------------------------------
 1    PZ grid (8-digit MGRS)     Grid accuracy ≤ 100m; correct grid zone designator
 2    Radio freq / callsign      Freq in valid range; callsign matches scenario CEOI
 3    Patient count by prec.     Correct U/P/R count; precedence classifications accurate
 4    Special equipment          Correct code for hoist/ventilator/blood products
 5    Patient type (L/A)         Litter vs ambulatory count matches casualty data
 6    Security at PZ             N/P/E/X code matches scenario threat picture
 7    PZ marking method          Method code valid; compatible with day/night conditions
 8    Nationality / status       Correct combination code (US/coalition/EPW/civilian)
 9    NBC contamination          Correct contamination category or "None" if clean

The simulation enforces the radio authentication exchange before accepting the request, requiring the trainee to correctly respond to the authentication challenge issued by the simulated MEDEVAC net control station. Read-back simulation covers Lines 1, 3, 5, and 9 at minimum -- the trainee must confirm or correct the read-back before the request is marked as transmitted. Time-to-transmission is measured from the time-of-injury event and displayed in the AAR as a performance metric against the ten-minute standard for Urgent-precedence requests.

Encryption procedure simulation requires the trainee to transmit Line 1 (the PZ grid) in encrypted format when operating on a non-secure net, and to switch to a secure net or use the brevity code system for full request transmission when the scenario communications plan requires it. Trainees who transmit the grid in clear text on a simulated non-secure net receive a communications security error that is flagged in the AAR independently of their field content accuracy.

Triage algorithm modeling

Triage simulation trains the decision algorithm that determines which casualty receives care first when demand exceeds immediate treatment capacity. Three algorithms are modeled in current platforms:

START triage (Simple Triage and Rapid Treatment) applies a 30-second per-patient assessment protocol. The simulation presents each patient with respiration rate, radial pulse, and mental status parameters. The trainee applies the START algorithm:

  START DECISION TREE
  ─────────────────────────────────────────────────
  Respirations?
    Absent → reposition airway
      Still absent → BLACK (Expectant)
      Present after reposition → RED (Immediate)
    <10 or >30 breaths/min → RED (Immediate)
    10–30 breaths/min → assess perfusion

  Radial pulse / cap refill?
    Absent or cap refill >2 sec → RED (Immediate)
    Present + cap refill ≤2 sec → assess mental status

  Mental status (obey simple commands)?
    Cannot obey → RED (Immediate)
    Can obey → YELLOW (Delayed)

  Ambulatory? → GREEN (Minor) [assessed before above]

SALT triage (Sort, Assess, Lifesaving Interventions, Treatment/Transport) adds a global sorting step before individual assessment. The simulation presents the full casualty population and requires the trainee to direct all walk-able patients to a collection point, then direct wave-responsive patients, then assess still patients -- a population-level sort before any individual assessment begins. SALT also permits specific lifesaving interventions (tourniquet application, opening the airway) during the triage pass that can change a patient's category before the treatment phase begins.

MIST handoff format is not a triage algorithm but a patient transfer communication standard used when passing casualties between care echelons. The simulation requires the trainee to deliver a MIST brief -- Mechanism of injury, Injuries found, Signs and symptoms, Treatment given -- to the simulated Role 2 receiving medical officer. MIST simulation evaluates completeness: omitting the treatment given field (tourniquet time, medications administered) is scored as a handoff error because it directly affects receiving facility treatment decisions.

Mass casualty (MASCAL) scenarios are designed specifically to test triage discipline under resource-scarcity conditions. The simulation generates more casualties than can be treated simultaneously, presents some patients with compelling injuries that create an instinct to treat immediately, and evaluates whether the trainee completes the full triage sort before committing treatment resources. The MASCAL AAR report compares the trainee's actual treatment sequence against the optimal sequence and shows the aggregate survival outcome difference -- making the population-level cost of triage discipline failures visible.

TCCC task simulation: tourniquet, airway, wound packing

Tactical Combat Casualty Care task simulation addresses the three intervention categories responsible for the majority of preventable battlefield deaths: hemorrhage control (tourniquet application and wound packing), airway management, and hypothermia prevention. The simulation can operate in screen-based mode, in haptic manikin-integrated mode, or in a combined mode where decision-tree responses drive a physical mannequin that provides procedural feedback.

In screen-based mode, each TCCC task is modeled as a decision sequence requiring the trainee to select the correct intervention, specify the correct parameters, and complete the documentation step. Tourniquet application simulation requires the trainee to identify the correct anatomical placement zone (2-5 cm proximal to the wound margin, never at or below the wound), select the appropriate device, specify the tightening method, and enter the time of application -- the NATO standard requires tourniquet time to be documented on the casualty's body or TCCC card at the time of application, not reconstructed later. The simulation enforces this documentation step before allowing the scenario to progress.

Airway management simulation steps through the TCCC airway algorithm: positioning (recovery position for unconscious patients), nasopharyngeal airway sizing (diameter selection based on the nostril size heuristic, length selection from nostril to tragus), and surgical airway indications (when NPA is contraindicated or fails). The simulation models the contraindication set for NPA -- suspected basilar skull fracture with CSF leak, severe midfacial trauma -- and requires the trainee to recognize when the NPA route is not appropriate before selecting an alternative.

Wound packing simulation evaluates hemostatic agent selection, packing technique, and pressure duration. The simulation distinguishes between compressible and non-compressible hemorrhage and presents the appropriate intervention set for each: tourniquet for compressible extremity hemorrhage, wound packing with hemostatic gauze for junctional hemorrhage in locations where tourniquet cannot be applied (groin, axilla, neck), and the limitations of both approaches for non-compressible truncal hemorrhage where damage control surgery is the only definitive intervention.

Haptic manikin integration connects the physical task execution to the simulation's assessment engine. The manikin's sensors record tourniquet placement accuracy (within the correct anatomical zone or outside it), tourniquet tension (above the minimum threshold required to stop arterial flow or below it), wound packing depth (gauze into the wound cavity to the required depth or superficial packing only), and airway device position. The simulation scores the physical execution against these thresholds and reports procedural errors in the TCCC task report alongside the decision-tree responses, giving the instructor a combined view of whether the trainee chose the right intervention and executed it correctly.

Helicopter and ground vehicle coordination

Helicopter LZ coordination simulation models the sequence of actions that prepare a pickup zone for rotary-wing approach and patient loading. LZ selection simulation presents the trainee with a terrain analysis display and a set of candidate sites, each with parameterized attributes:

LZ ASSESSMENT PARAMETERS

  Slope:         ≤7° (wheeled platforms) / ≤15° (skid platforms)
  Dimensions:    min 30m × 30m for UH-60 single-ship; 50m × 50m for Chinook
  Obstacles:     no obstacles within 50m of center at rotor height
  Surface:       grass / hardpan: GO / loose sand / marsh: NOGO
  Approach axis: aligned into wind; min 60° clearance arc
  Threat:        direct fire standoff ≥300m from known threat positions
  Marking:       VS-17 panel / smoke / IR strobe / laser per light conditions

The simulation evaluates the trainee's LZ selection against each criterion and produces a composite suitability score. Scenarios include disqualifying sites (slope exceeding the aircraft limit, tall vegetation in the approach corridor) and marginal sites that require the trainee to weigh competing factors.

PZ marking simulation covers all standard marking methods. Daytime scenarios train VS-17 panel placement orientation (display to the aircraft, not at the aircraft), smoke employment (deploy smoke at final approach, not before, to prevent wind dissipation; report color to aircraft rather than specifying in advance to prevent threat exploitation), and the direction-finding signal for aircraft that lose radio contact. Night scenarios train IR strobe placement (visible to NVG-equipped aircraft and FLIR sensors), IR chemlight pattern (X-pattern for landing, L-pattern for approach direction), and laser designation parameters for FLIR-equipped platforms.

The PZ-to-aircraft communication simulation runs the full exchange protocol: initial contact, PZ status report, marking acquisition confirmation, heads-down notification, patient loading coordination, and departure confirmation with Role 2 destination handoff. The simulation scores the interval between each communication step and flags deviations from the protocol sequence. A common error modeled is activating IR marking before the aircraft is within sensor acquisition range -- increasing the exposure time of the PZ signature -- and the simulation measures the duration between marking activation and aircraft acknowledgment as a security exposure metric in the AAR.

Ground vehicle CASEVAC coordination simulation models the loading, en route care, and handoff procedures for evacuation using organic tactical platforms. Vehicle-specific modules address the loading procedures and patient positioning constraints for wheeled ambulance, APC, and unmodified tactical vehicle configurations. En route care simulation models the intervention restrictions during vehicle movement and the documentation completion requirement before patient handoff at the Role 1 aid station.

Integration with broader C2 simulation

MEDEVAC simulation does not operate in isolation from the broader tactical training environment. Observer-controller trainer software that manages the exercise scenario injects the casualty events that initiate MEDEVAC training sequences, and the medical status updates produced by the MEDEVAC simulation must feed back into the unit's COP so that the medical officer and S4 section have current patient visibility.

The casualty status feed interface maps the MEDEVAC simulation's patient state machine to the medical tracking layer on the COP. Status transitions -- wounded, triaged, MEDEVAC requested, en route, delivered to Role 2 -- appear in the COP medical layer as the simulation progresses through each phase. This integration ensures that the tactical operations cell simulation sees the same casualty picture that the medical simulation is tracking, enabling the combined training event to model the coordination between the medical and tactical command functions that is a frequent friction point in actual operations.

Medical logistics integration connects MEDEVAC simulation to the class VIII supply chain planning simulation. Treatment actions performed during TCCC task sequences generate consumption events -- tourniquet, combat gauze, IV fluid, blood products -- that are transmitted to the medical logistics module as materiel consumption data. The medical logistics military planning simulation uses this consumption data to generate resupply requirement calculations, enabling the S4 medical section to practice the resupply request workflow against demand generated by actual simulated casualties rather than from a static scenario inject.

Data format standards for the integration include VMF message types for casualty status reporting, MIL-STD-2525 symbology for COP medical layer display, and HL7 FHIR military profile extensions for electronic patient record exchange between Role 1 and Role 2 simulation nodes. Platforms designed for multinational exercise use support NATO message catalogue (APP-11) medical message formats for interoperability with partner nation simulation nodes.

After-action review for MEDEVAC scenarios

The after-action review package produced by MEDEVAC simulation software is structured differently from conventional exercise AAR packages because it must communicate performance in clinical terms -- patient outcomes -- as well as procedural compliance terms. A trainee who correctly formatted the 9-line request but delayed tourniquet application by four minutes needs to see both the procedural error (delay beyond standard) and its clinical consequence (reduced survival probability for the simulated patient) in the same AAR display.

The timeline reconstruction presents every significant event in the scenario chronologically: casualty event, first care initiation, each intervention with timestamp, 9-line transmission, aircraft dispatch, PZ arrival, patient loading, and Role 2 handoff. Decision point markers highlight moments where the trainee deviated from the optimal decision path, and each marker links to the relevant TCCC guideline, evacuation doctrine reference, or training objective that the decision point is designed to test.

Survival outcome modeling applies a probabilistic survival function to each simulated casualty based on the care timeline and interventions performed. The model is parameterized by wound type and mechanism, time to each intervention relative to time of injury, and quality-of-care assessments from the TCCC task evaluation. The survival probability is displayed as a curve that shows where each intervention improved or degraded the simulated patient's condition -- when a trainee delayed tourniquet application, the curve shows the specific probability decrement associated with that delay against the same wound type managed to standard.

9-line performance reporting breaks out error rates by line number across multiple scenario runs, revealing systematic errors that a single-session review would not identify. If a trainee consistently errors on Line 4 (special equipment) but performs well on all other lines, the AAR trend report identifies this as a focused remediation need. MASCAL AAR reports show the aggregate population outcome of the trainee's triage sequencing decisions -- not just whether individual patients were correctly categorized, but whether the prioritization order maximized the simulated population's survival.

Export formats for training records include xAPI statements compatible with military learning management systems, per-scenario PDF reports for unit training files, and aggregate trend data in structured formats for medical readiness officer review. The combination of individual-session AAR data and longitudinal trend data enables training managers to track competency development over multiple simulation iterations and identify when a trainee has achieved the training standard -- or when additional training is required before certification.

Design principle: The most common failure mode in MEDEVAC simulation design is optimizing for scenario realism at the expense of skill repetition volume. A high-fidelity immersive scenario that takes 45 minutes to complete limits a trainee to eight to ten repetitions in a training day. A screen-based scenario that captures the procedural and decision essentials in five minutes enables 30+ repetitions in the same period. For skills that require repetition to become automatic under stress -- tourniquet application sequence, 9-line field composition -- repetition volume typically produces better transfer than single-session immersive fidelity. Use high-fidelity simulation for capstone assessment; use efficient procedural simulation for the repetition phase of training.

Medical evacuation and TCCC training simulation in a unified platform

Corvus WARG provides integrated scenario generation, MEDEVAC request workflow simulation, TCCC task evaluation, and after-action review tools, enabling medical readiness training at scale without live aircraft or dedicated simulation range infrastructure.

Explore Corvus WARG → Book a Briefing

This analysis was prepared by Corvus Intelligence engineers who build mission-critical training and field applications for defense and government organizations. Learn about our team →

Frequently Asked Questions

What is the difference between MEDEVAC and CASEVAC in simulation software?

MEDEVAC (Medical Evacuation) refers to evacuation conducted by dedicated medical platforms -- typically rotary-wing aircraft staffed with flight medics -- that fall under medical command authority and are protected under the Geneva Convention. CASEVAC (Casualty Evacuation) refers to evacuation of casualties by any available platform, medical or otherwise, typically driven by tactical necessity rather than medical planning. Simulation software models both: MEDEVAC scenarios train the formal 9-line request workflow, MEDEVAC net radio procedures, aircraft coordination, and patient preparation for aeromedical transport. CASEVAC scenarios train improvised vehicle loading, care en route without dedicated medical personnel, and handoff to the next echelon of care without the established handoff protocols of a formal MEDEVAC system. The distinction matters for training because the decision calculus, communication procedures, and patient care expectations differ significantly between the two.

How does simulation software generate and evaluate 9-line MEDEVAC requests?

A 9-line MEDEVAC request simulator presents the trainee with a simulated casualty scenario -- including location, number of patients, type of wounds, and battlefield conditions -- and requires them to compose and transmit a correctly formatted 9-line request. The software evaluates the submitted request field by field: Line 1 (grid coordinate), Line 2 (radio frequency and call sign), Line 3 (patients by precedence: Urgent, Priority, Routine), Line 4 (special equipment), Line 5 (patients by type: litter or ambulatory), Line 6 (security at pickup zone), Line 7 (marking method), Line 8 (patient nationality and status), Line 9 (NBC contamination). Each field is scored independently so the trainee receives granular feedback on which elements were correct and which contained errors. Time-to-transmission is recorded and compared against the standard; errors in high-urgency fields (Line 1, Line 3) are flagged at higher severity than formatting deviations in lower-stakes lines.

What triage algorithms does MEDEVAC training simulation software model?

Current simulation platforms model three primary triage algorithms. START (Simple Triage and Rapid Treatment) uses a 30-second per-patient assessment protocol evaluating respirations, perfusion, and mental status to assign Red (immediate), Yellow (delayed), Green (minor), or Black (expectant/deceased) categories. SALT (Sort, Assess, Lifesaving Interventions, Treatment/Transport) adds a global sorting step before individual assessment and explicitly models lifesaving interventions -- tourniquet application, opening the airway -- that can change a patient's category during the triage pass. MIST (Mechanism of injury, Injuries, Signs and symptoms, Treatment given) is used for handoff rather than initial sorting and models the structured casualty report format required when passing a patient between care echelons. Mass casualty (MASCAL) scenario modules test whether trainees can maintain triage discipline when the number of casualties exceeds immediate treatment capacity.

How does TCCC task simulation work without haptic feedback devices?

Screen-based TCCC task simulation represents each intervention as a decision tree. The trainee is presented with a simulated casualty description -- injury type, mechanism, vital signs -- and must select the correct intervention sequence. Tourniquet scenarios require the trainee to identify the correct anatomical placement zone, select appropriate tightening technique, and document the application time. Airway management scenarios step through the TCCC airway algorithm: positioning, nasopharyngeal airway insertion, surgical airway indications. Wound packing scenarios require selection of hemostatic agent, packing depth and direction, and pressure duration. The simulation evaluates the sequence, timing, and completeness of each step and provides immediate corrective feedback. Haptic manikin integration layers physical task execution onto the same decision framework, with the simulation recording procedural errors detected by the manikin's sensors -- incorrect tourniquet position, insufficient packing depth -- alongside decision-tree responses.

What parameters does helicopter LZ coordination simulation model?

Landing zone (LZ) coordination simulation models the full set of factors that determine whether a chosen site is suitable for rotary-wing operations. Terrain analysis parameters include slope gradient (typically 7-degree maximum for wheeled aircraft, up to 15 degrees for skid-configured), obstacle clearance in the approach and departure corridors, and surface assessment for weight-bearing capacity. Weather parameters include wind speed and direction relative to the planned approach axis, visibility and ceiling restrictions, and density altitude effects at high-elevation sites. Threat parameters model the exposure geometry of the LZ and the duration of exposure during approach, hover, and departure. The simulation presents trainees with LZ options that include disqualifying and marginal factors, requiring them to apply the selection criteria systematically. PZ marking simulation covers VS-17 panel placement, smoke employment sequence, IR strobe placement for NVG operations, and laser designation for FLIR-equipped aircraft.

How does MEDEVAC simulation integrate with command post exercise and COP feeds?

Integration between MEDEVAC simulation and broader CPX environments occurs through a casualty status feed that updates the unit's medical tracking layer on the common operational picture. When a simulated casualty event is generated by the CPX scenario engine, the MEDEVAC simulation module creates a casualty record with the patient's simulated grid location, wounding mechanism, and time of injury. This record appears in the medical tracking layer visible to the S4 medical section and battalion aid station simulation node. As the trainee progresses through the MEDEVAC request workflow, triage, and evacuation simulation, the casualty record status updates in the COP: from 'wounded' to 'triaged' to 'MEDEVAC requested' to 'en route' to 'at Role 2.' The logistics module simultaneously generates a blood product consumption event and a resupply request that feeds the medical logistics planning simulation.

How does survival outcome modeling work in MEDEVAC after-action review?

Survival outcome modeling applies a probabilistic survival function to each simulated casualty based on the care timeline and interventions performed. The model is parameterized by wound type and mechanism, injury severity score from the simulated wounding event, time to each intervention (tourniquet, hemorrhage control, IV access, airway management), time to definitive care at Role 2 or Role 3, and quality of care assessments from the TCCC task evaluation. The survival probability is computed at each stage of the evacuation chain and displayed in the AAR timeline as a curve showing where each intervention improved or degraded the simulated patient's outcome. When a trainee delayed tourniquet application by four minutes, the survival curve shows the specific probability decrement associated with that delay. This outcome modeling makes the consequence of procedural errors or timeline delays visible in a way that communicates directly in the terms that matter to medical personnel.

What radio procedure elements does 9-line MEDEVAC net simulation train?

MEDEVAC net radio simulation trains the complete communication protocol for requesting and coordinating evacuation, not just the content of the 9-line format. The simulation models call sign management -- the requesting unit calls on the MEDEVAC net frequency, not on the tactical net -- and requires the trainee to conduct the initial call correctly before transmitting the 9-line. Read-back procedures are simulated: the MEDEVAC element reads back critical lines (Lines 1, 3, 5, and 9 at minimum), and the trainee must confirm or correct the read-back before the request is accepted. Encryption simulation covers the use of authentication tables and the requirement to transmit Line 1 (grid location) encrypted on non-secure nets. The simulation also trains the MEDEVAC status call -- the periodic update from the requesting unit to the inbound aircraft confirming that the LZ is still secure and patients are prepared -- a procedural step frequently omitted in training but critical for flight crew decision-making during the approach.

How does MASCAL scenario simulation differ from single-casualty MEDEVAC training?

Mass casualty (MASCAL) simulation is architecturally distinct from single-casualty MEDEVAC training because it introduces resource constraint as the primary training variable. In single-casualty scenarios, the trainee has a manageable number of tasks to sequence against a single patient. In MASCAL scenarios, the simulation generates more casualties than the available evacuation and treatment capacity can handle simultaneously, forcing the trainee to make prioritization decisions under time pressure with incomplete information. The triage sorting phase requires the trainee to complete an initial sort across all simulated casualties before committing treatment resources to any individual patient. The simulation records whether the trainee violated triage discipline, which patients received care first, and how these decisions affected the overall population survival outcome compared to an optimal triage sequence. MASCAL AAR reporting shows the aggregate outcome of the trainee's prioritization decisions, not just individual patient care quality.

What makes simulation software more effective than mannequin-only TCCC training?

Simulation software complements but does not replace mannequin-based TCCC training: the two modalities address different learning objectives. Mannequin-based training builds the psychomotor skills -- hand placement, tourniquet tension, airway tube insertion angle -- that cannot be developed through a screen interface. Simulation software trains the cognitive and procedural dimensions: the decision algorithm that determines which intervention to apply first, the communication procedures for requesting evacuation, the triage sorting logic under MASCAL conditions, and the documentation discipline required for patient handoff. Software simulation also enables scenario volume and variety that is impractical with physical mannequins: a single instructor can run many trainees through varied casualty scenarios in a day, with each scenario automatically scored and recorded. The combination sequences screen-based simulation first to establish the decision framework, then transitions to mannequin tasks to develop physical skills, then integrates both in full-scenario exercises.