The Medical Plan Must Move

A valid medical plan can expire before the briefing does

A medical plan begins with a relationship among expected demand, staffed capability, evacuation capacity, route and transfer windows, and the materiel needed to sustain care. Every part can change after the plan is approved.

A surge increases modeled demand. A treatment location reports fewer staffed capabilities than its nominal bed count suggests. A transport asset becomes unavailable or ineligible. A route closes. A transfer window narrows. A resupply is delayed. None of those changes, by itself, determines what should happen to a particular patient. Together, however, they can make the represented plan infeasible.

The familiar failure is not necessarily an absent report. It is a plan assembled from reports that were valid at different times, reconciled manually, and briefed as one current answer. The medical common operating picture can show that conditions changed while the evacuation, capacity, and resupply calculations remain attached to an earlier state.

This paper separates two claims. Public doctrine and research establish that medical movement and sustainment require continuing coordination across capacity, transport, time, and resources. Grid enters only as a proposition: qualified owners can represent selected planning relationships as an executable, reactive model and evaluate that model in a controlled exercise. The public sources do not describe, endorse, or validate Grid.

What the public record establishes

DoD Instruction 6000.11, Patient Movement, assigns specific institutional responsibilities for global patient movement and joint theater patient evacuation. It says regulation is based on released medical-capability and bed-availability information; destination and transport mode depend on clinical and bed-capacity considerations, resource use, and other factors. It also describes patient-movement organizations synchronizing and deconflicting transport-to-bed plans. That is a coordinated operating function, not a simple vehicle schedule.

The same relationship appears in civil emergency planning. The 2024 National Disaster Medical System Federal Coordinating Center Guide describes medical regulating as identifying people awaiting movement, locating available beds, and coordinating transportation. Its planning factors include medical condition, transport availability, facility capability, bed status, throughput, hubs, and communications. The institutional settings differ, but both records show why a capacity count cannot be separated from capability, movement, and time.

Resupply adds another governed system. DoD Instruction 5101.15, DoD Medical Materiel Management assigns responsibilities across medical materiel acquisition, forecasting, standardization, theater support, and distribution. It directs planners to compute requirements from operational planning factors and clinical treatment protocols, account for assumptions and constraints, and use common modeling and computation processes where possible. The instruction defines responsibilities and direction. It does not prove that any particular software accurately forecasts demand or safely allocates medical materiel.

The Defense Department also treats medical modeling as a governed capability. DoD Instruction 6000.18 establishes requirement development and approval for medical modeling and simulation used in planning, decision-making, education, and training. A model is therefore not credible merely because it produces an answer. Its requirements, intended use, owners, validation, and evidence matter.

A 2025 peer-reviewed proof-of-concept report on the Automated Battlefield Trauma System provides a narrower research signal. The authors describe existing casualty-planning tools as producing static estimates without predictive capability for evacuation and medical resupply. During Warfighter Exercise 25-02, their system automated casualty categorization, resource estimation, and reporting from exercise data. The authors also identify remaining work in casualty modeling, data integration, and joint and allied interoperability. The Joint Trauma System journal watch labels the publication Level V, proof-of-concept evidence. It is evidence that this planning problem is active and that a particular prototype was exercised—not evidence of generalized performance, clinical effect, or Grid capability.

Clinical knowledge remains a separate authority. The Joint Trauma System clinical practice guideline directory presents guidelines as standards for casualty care grounded in clinical evidence and operational data. A planning platform may consume an approved aggregate produced under qualified clinical rules. It does not author those care rules, turn them into universal truth, or replace the professionals responsible for applying them.

The planning object is not a patient record

A safe design starts by naming what the planning model may represent and what it must not decide.

The bounded planning object can include:

• Modeled demand: time-phased aggregate demand classes produced by an external, qualified method, with source, revision, and uncertainty.
• Staffed capacity: declared capability available in a time window after staffing, equipment, space, and sustainment assumptions are applied—not nominal beds alone.
• Transport and route state: authored mode eligibility, capacity, origin, destination, handoffs, route status, and operating windows.
• Time: observation time, valid-through time, modeled duration or range, transfer-window boundaries, and decision deadlines.
• Medical materiel: aggregate on-hand, in-transit, consumption, shelf-life, cold-chain, substitution, and resupply constraints as defined by responsible medical-logistics owners.

That object does not diagnose, determine triage, set clinical priority, direct treatment, decide whether an individual is stable for movement, select a destination for a named patient, or allocate a scarce intervention. It does not convert command intent into clinical authority. Those decisions remain with appropriately qualified and authorized people and processes.

This distinction is more than data minimization. It prevents a planning feasibility result from being mistaken for clinical direction. “Represented capacity is available” means only that the authored aggregate conditions pass. “This person should move” is a different claim that this proposition does not make.

The Grid proposition

Grid proposes representing the permitted planning object as a set of connected, versioned models rather than reimplementing it in separate capacity boards, evacuation trackers, resupply workbooks, and command briefings.

Configured sources publish only the aggregates the composition is authorized to consume. A capacity model can publish staffed capability by window. A movement model can publish transport eligibility and route state. A medical-logistics model can publish supported resupply quantities and timing assumptions. A demand model can publish clinically neutral planning units. Each value retains its source identity, observation time, revision, validity condition, and any uncertainty supplied by its qualified owner.

The dependency graph connects those inputs to a bounded plan. When one accepted input changes, only the affected conclusions recalculate. Authored constraints reject alternatives that exceed represented capacity, use an ineligible mode, miss a route window, or rely on unsupported resupply. Explanation identifies the material inputs and reasons. Role-specific surfaces can show the same model revision to medical planners, logisticians, and command reviewers without creating separate calculations.

Then the model stops. It presents represented alternatives as feasible, infeasible, conditional, or unresolved within declared bounds. Medical and command authorities review the evidence, uncertainty, and tradeoffs and make any consequential decision outside the model. An integrated system may record an authenticated external authorization and downstream receipt. A receipt proves only that a named revision was reported received; it does not prove understanding, execution, transport, treatment, or outcome.

This is an architecture proposition. Grid does not claim a shipped or clinically validated medical-planning product, a live deployment, an authorized interface, or measured operational effect.

Uncertainty is part of the plan state

Medical planning data can be precise in format and weak in fact. A facility's capacity may omit an expired credential, unavailable equipment, a staffing transition, a supply constraint, or the time needed to turn over a capability. A transport may be present but not medically eligible. A route report may be old. Demand may be an exercise estimate rather than an observation. Two sources may disagree because their update cycles or definitions differ.

Each material input should therefore carry, where applicable, source, revision, observed time, valid-through time, definition, and uncertainty or quality state. A modeled duration, range, or percentile remains an assumption or external model output until separately validated; the composition should preserve its provenance rather than present it as a promised arrival.

Missing, stale, and contradictory facts should change the answer. An expired capacity input may make an option unresolved. A disagreement between route sources may require review. A missing resupply confirmation may remove an alternative from the bounded feasible set. The model should not silently impute a favorable value to keep the plan green.

Sensitivity analysis can show which assumptions consume the remaining margin. It cannot make unknown facts true. The useful output may be a clear refusal to conclude until a named source is refreshed.

A bounded exercise scenario

Consider fictional Exercise MED-27. Twelve abstract modeled care units begin allocated 4 / 5 / 3 across Care North, Care Central, and Care South. They are aggregate planning tokens, not patients, acuity classes, diagnoses, or treatment recommendations.

Three exercise facts then change. The demand model publishes six additional units. A transfer window closes. Care Central's reported staffed capacity changes from eight to three. Care Reserve appears as an authored four-unit planning option, not an assumed physical asset.

The exercise model evaluates three predefined aggregate allocation alternatives. Alternative A exceeds represented staffed capacity. Alternative B exceeds another represented capacity and fails the authored route window. Alternative C distributes the 18 abstract units 6 / 3 / 6 / 3 across North, Central, South, and Reserve. It is the only alternative in this fixture that satisfies the represented demand, capacity, transport-eligibility, route-window, and time constraints.

“Feasible” is deliberately narrow. It does not mean globally optimal, clinically appropriate for any person, physically executable, or likely to improve an outcome. The model has not created staff, opened a route, activated Reserve, secured transport, or confirmed resupply. Qualified reviewers may reject the recommendation, revise an input, request more evidence, or evaluate another authored option.

The plan remains MEDICAL COMMAND AUTHORIZATION REQUIRED until an external authority decides on that exact revision. Configured receipts can then record that Care North, Care South, Mobility, and Medical Logistics report receipt. The exercise ends there. It depicts an externally authorized modeled-plan revision, not patient movement or care.

The Medical Plan Must Move visualizes this deterministic exercise. From a Changed Fact to Coordinated Action places the same coordination pattern beside logistics and mission-planning examples without treating the domains as interchangeable.

Clinical, security, and accreditation limits

The responsible medical organization must define and validate every demand, capability, transport, time, and materiel semantic. DoD Instruction 6025.13 assigns clinical quality-management, credentialing, and privileging responsibilities within the Military Health System. Grid neither grants clinical privileges nor validates scope of practice. A modeled planning result cannot override clinical judgment, professional standards, facility policy, or command responsibility.

Facility accreditation is also external. The Military Health System's accreditation overview describes survey, findings, and corrective-action processes conducted against recognized standards. A software evaluation does not accredit a facility, care process, or medical model, and a facility's accreditation does not automatically validate a new computational composition.

Aggregate exchange is not a privacy, classification, or cross-domain control. The deployment owner must determine what may be collected, used, retained, and released; enforce identity, access, encryption, auditing, and approved interfaces; and test behavior under partial failure. DoD Instruction 8510.01 places the system-authorization decision with the designated authorizing official under the Risk Management Framework. Nothing in this paper establishes an authorization to operate, classified accreditation, cross-domain approval, HIPAA compliance, medical-device status, or suitability for a particular environment.

Evaluate coordination without claiming care outcomes

Start with one controlled exercise, one aggregate planning decision, a small source set, and an actual authority matrix. Record the current workflow before configuring Grid: update cadence, manual rekeying, reconciliation meetings, time to a revised planning answer, conflicting versions, and the point at which qualified authority acts.

Run clean, missing, stale, delayed, contradictory, and out-of-scope fixtures through both workflows. Include a capacity drop, route closure, transport ineligibility, resupply uncertainty, superseded revision, unauthorized release attempt, and delayed acknowledgment. Predefine the expected safe state for each case, including when the correct result is unresolved.

Measure only what the exercise can support:

• Time from accepted aggregate change to revised modeled-plan status in the controlled environment
• Manual transfers and reconciliation steps removed or retained
• Stale, missing, and contradictory inputs surfaced before recommendation
• Represented alternatives carrying explicit feasible, infeasible, conditional, or unresolved reasons
• Repeated execution of the same source and model revisions producing the same declared result
• Recommendations bound to source, model, constraint, and explanation revisions
• Unauthorized release attempts stopped within the tested boundary
• External decisions attributable to the role defined in the approved exercise authority matrix
• Downstream revision receipts, duplicates, delays, and partial failures made visible
• Reviewer ability to identify assumptions, remaining margin, and reasons for rejection

Do not translate those measures into casualty reduction, survival, quality of care, treatment effectiveness, patient-level destination appropriateness, forecast accuracy, or mission success. Those are different claims requiring appropriately designed clinical, operational, and independent evidence.

Use the decision evaluation worksheet to record the baseline, sources, model boundary, authority, and acceptance criteria. Grid Developers provides the implementation-level handoff for explaining and validating a changing decision and canonical examples.

A medical plan should move when its represented facts change. The discipline is making that movement fast enough to evaluate, narrow enough to trust, and accountable enough that computation never disguises who provides care or who has authority to act.