# Preventive Medicine And Force Health Protection

> Identify operational health threats and recommend prevention controls for deployed forces. Use when disease, environment, sanitation, or vector risk can degrade combat power.

- Skill: `zwright8/preventive-medicine-and-force-health-protection` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zwright8/preventive-medicine-and-force-health-protection`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/preventive-medicine-and-force-health-protection/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/preventive-medicine-and-force-health-protection

---


# Preventive Medicine And Force Health Protection

## Mission Scope

- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in its domain.
- Start by confirming echelon, operating environment, available authorities, time horizon, and required decision points.
- Keep products unclassified by default unless the user provides handling guidance and controlled data.

## Workflow

1. Frame the mission problem using these core inputs: unit disposition, climate and sanitation conditions, medical surveillance trends, immunization status.
2. Identify assumptions, decision thresholds, and what intelligence or reporting would invalidate the current plan.
3. Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk.
4. Integrate dependencies across joint functions: command and control, movement/maneuver, fires/effects, intelligence, protection, sustainment, and information.
5. Produce commander-facing outputs and a staff-action version with owners, suspense dates, and branch triggers.

## Required Output Format

Deliver results in this order:

1. Situation snapshot: current conditions and key changes since last update.
2. Recommended option: one clearly stated recommendation and rationale.
3. Alternative options: at least two alternatives with pros, cons, and trigger conditions.
4. Decision points: what must be decided now, later, or pre-delegated.
5. Staff tasking: who does what by when.

## Domain Products

Primary products for this skill: force health risk brief, preventive control plan, surveillance watchlist.

## External Tools and Protocol Integration

- Use the integration baseline in ../_shared/references/external-tools-protocols.md.
- Include a domain toolchain profile selection and rationale (primary, alternate, and degraded-mode stack).
- Prioritize these tools or tool families for this domain: public health surveillance systems, environmental monitoring tools, medical readiness dashboards.
- Specify outbound exchange format for recommendations and tasking (for example USMTF, VMF, Link 16 J-series, CoT, STIX/TAXII, OGC WMS/WFS/WMTS).
- Include provenance metadata in outputs: source system, refresh time (UTC), assumptions, and confidence.

## Interoperability Validation Checklist

- Run the mission assurance workflow in `../_shared/references/mission-assurance-checklist.md` before final release.
- Validate that each product includes source provenance, protocol/message format, UTC refresh time, confidence, and known gaps.
- If interoperability checks fail, provide a degraded-mode plan and required staff coordination actions.

## Tool Invocation Contract

- For each external tool recommendation, include: objective, required inputs, query/action template, expected output schema, transport protocol, and fallback path.
- Explicitly map tool outputs to decision points so operators can validate mission relevance quickly.
- If a tool is unavailable, provide a manual workaround with expected time and confidence impact.

## Guardrails

- Flag gaps where assumptions exceed evidence.
- Identify legal, policy, ROE, safety, and coalition interoperability constraints early.
- Separate facts, assessed judgments, and unknowns.
- Do not fabricate classified sources, authorities, or approvals.

## Tool Protocol Playbooks

- Use protocol examples in ../_shared/references/tool-protocol-playbooks.md to produce operator-ready tool invocation packets.
- Use adapter contract guidance in ../_shared/references/external-tool-endpoints-and-adapters.md to define endpoint schemas, transport, and fallback behavior.
- Add at least one machine-ingestible packet and one commander-readable summary for each critical recommendation.

## Domain Tool Packet Library

- Use scenario packets in ../_shared/references/domain-tool-packet-library.md for domain-specific external tool selections and message templates.
- Include a `packet_id` and `protocol_profile` from the library for each critical recommendation.
- If no packet matches, define a provisional packet using the same schema and note the validation owner.

## Domain Data Contract

- Use mapping guidance in ../_shared/references/joint-mission-data-contracts.md to define required fields, validation gates, and releasability tags for this mission domain.
- Ensure every mission recommendation references a data contract profile and identifies required schema checks before publication.

## Operational Learning Loop

- Use `../_shared/references/operational-learning-and-after-action-loop.md` to generate after-action deltas, corrective actions, and readiness metrics for this domain.
- Include an `aar_id`, effect delta assessment, and owner/suspense for each high-impact recommendation.
- If post-action data is incomplete, issue a provisional learning note with confidence and revalidation deadline.

## Readiness Certification Evidence Pack

- Use `../_shared/references/readiness-certification-evidence-pack.md` to define mission-essential task evidence, evaluator triggers, and certification confidence scoring.
- Include `met_id`, `evidence_packet_id`, and `cert_confidence` for each recommendation that changes unit readiness posture.
- If required evidence is missing, mark status as `provisional` and assign closure actions with suspense.

## Protocol Execution Sequence

- Execute the Core Integration Protocol from `../_shared/references/external-tools-protocols.md` as an explicit step sequence, not as guidance only.
- For each critical dependency, include `invoke_order`, `adapter_contract_id`, `packet_id`, `protocol_profile`, and timeout/retry settings.
- Record acknowledgment status for each tool call and publish a degraded-mode branch when any dependency misses SLA.
- Require a human command check before acting on outputs that can materially change force posture, mission risk, or escalation.

## Domain Toolchain Profile Binding

- Use `../_shared/references/domain-toolchain-profiles.md` and select a required `toolchain_id` for each critical recommendation.
- Include `primary_system`, `cross_check_system`, `protocol_binding`, `credential_scope`, and `fallback_path` fields in every tool invocation packet.
- Mark recommendations as `provisional` when toolchain authority, credential scope, or cross-check data freshness is incomplete.

## Tool Health and Trust Monitoring

- Use `../_shared/references/tool-health-and-trust-monitoring.md` to include pre-mission tool health checks, trust score updates, and failover timing evidence.
- Add `tool_health_id`, `trust_score`, `last_probe_utc`, and `failover_executed` fields for every critical external dependency.
- If tool trust posture drops below mission threshold, publish a no-go or degraded recommendation with explicit commander decision prompts.

## U.S. Joint Protocol Assurance Drill

- Use `../_shared/references/us-joint-protocol-assurance-drill.md` to run a mandatory pre-release drill for protocol conformance, cryptographic trust, and message acknowledgment integrity.
- Include `assurance_drill_id`, `interop_score`, `crypto_posture`, and `ack_chain_status` fields for each critical recommendation.
- If the drill fails any gate, publish a constrained-employment recommendation with specific remediation owners and suspense.

## Joint Operations External Toolchain Profiles

- Use `../_shared/references/joint-operations-external-toolchain-profiles.md` to select a mission-fit `toolchain_profile_id` and bind each recommendation to concrete primary/cross-check tools.
- Include `refresh_sla_minutes`, `degraded_trigger`, and `degraded_fallback` fields for each critical dependency.
- If no profile fits, create a provisional profile and assign a `validation_owner` with suspense before release.

## Human-Agent Command Escalation Matrix

- Use `../_shared/references/human-agent-command-escalation-matrix.md` to assign authority tier, impact level, approval role, and escalation triggers for each critical recommendation.
- Include `authority_tier`, `decision_impact_level`, `requires_human_approval`, `approval_role`, and `audit_record_id` in outputs that influence mission posture.
- If authority, legal basis, or acknowledgment integrity is uncertain, downgrade to advisory-only with explicit commander decision prompts.

## Mission Tool Authority Gates

- Apply escalation requirements in `../_shared/references/warfighter-tool-authority-gates.md` for high-consequence recommendations.
- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for recommendations that can alter mission posture.
- If authority, legal basis, or data provenance is uncertain, downgrade to advisory-only and require human command review.

## Cross-Domain Integration Playbook

- Use `../_shared/references/cross-domain-integration-playbook.md` to synchronize dependencies across land, maritime, air, space, cyber, electromagnetic, and civil-support domains.
- Include `integration_id`, `domains`, `protocol_binding`, `refresh_sla_minutes`, and `staleness_trigger` fields for each critical cross-domain dependency.
- If cross-domain authority, translation fidelity, or releasability is uncertain, downgrade to advisory-only and require explicit human command approval.

## Mission Tool and Protocol Catalog Binding

- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` to select concrete tool suites and protocol stacks for this domain.
- Include `tool_suite_id`, `protocol_stack_id`, `interop_standard_set`, `endpoint_security_profile`, and `degraded_exchange_method` for each critical recommendation.
- If no suite matches, define a provisional suite and assign `validation_owner` and `revalidation_utc` before release.

## Domain Toolchain Override (2026-03-15, Expansion Wave LIII Addendum)

- Add `tool_suite_id=ts-expeditionary-vector-control-field-epidemiology-v1` + `protocol_stack_id=ps-expeditionary-vector-control-field-epidemiology-stack-v1` when force-health posture depends on vector suppression, habitat denial, or outbreak-investigation timing.
- Add `tool_suite_id=ts-expeditionary-barracks-hvac-mold-indoor-air-quality-v1` + `protocol_stack_id=ps-expeditionary-barracks-hvac-mold-indoor-air-quality-stack-v1` when readiness depends on restoring habitability, respiratory safety, or mold containment inside expeditionary housing.
- Add `tool_suite_id=ts-theater-reproductive-health-contraception-sti-readiness-v1` + `protocol_stack_id=ps-theater-reproductive-health-contraception-sti-readiness-stack-v1` when protected pharmacy continuity, STI diagnostic throughput, or privacy-safe reproductive care drives readiness risk.
- Add `packet_id=DPL-VECTOR-CONTROL-FIELD-EPI-001`, `packet_id=DPL-BARRACKS-HVAC-MOLD-IAQ-001`, and `packet_id=DPL-REPRODUCTIVE-HEALTH-STI-READINESS-001` for branches that materially alter outbreak response, housing posture, or protected care access.

## Domain Toolchain Override (2026-03-15, Expansion Wave LIV Addendum)

- Add `tool_suite_id=ts-expeditionary-industrial-hygiene-occupational-exposure-v1` + `protocol_stack_id=ps-expeditionary-industrial-hygiene-occupational-exposure-stack-v1` when commander risk depends on sampling confidence, PPE posture, confined-space controls, or safe work continuation.
- Add `tool_suite_id=ts-theater-occupational-toxicology-solvent-fuel-heavy-metal-v1` + `protocol_stack_id=ps-theater-occupational-toxicology-solvent-fuel-heavy-metal-stack-v1` when solvent, fuel, propellant, or heavy-metal exposure drives surveillance expansion, isolation, or notification thresholds.
- Add `tool_suite_id=ts-expeditionary-food-protection-inspection-sanitation-v1` + `protocol_stack_id=ps-expeditionary-food-protection-inspection-sanitation-stack-v1` when food-source pedigree, cold-chain integrity, or sanitation breakdown materially affects force-health posture.
- Add `tool_suite_id=ts-theater-hazardous-waste-burn-pit-ash-exposure-v1` + `protocol_stack_id=ps-theater-hazardous-waste-burn-pit-ash-exposure-stack-v1` when waste backlog, emissions, or ash exposure changes habitability, compliance, or medical-surveillance decisions.
- Add `packet_id=DPL-INDUSTRIAL-HYGIENE-OCCUPATIONAL-EXPOSURE-001`, `packet_id=DPL-OCCUPATIONAL-TOXICOLOGY-EXPOSURE-001`, `packet_id=DPL-FOOD-PROTECTION-INSPECTION-SANITATION-001`, and `packet_id=DPL-HAZARDOUS-WASTE-BURN-PIT-ASH-001` for branches that materially alter exposure controls, feeding posture, or environmental-health protection.

## Domain Toolchain Override (2026-03-15, Expansion Wave LXVI Addendum)

- Add `tool_suite_id=ts-expeditionary-wastewater-graywater-vector-control-v1` + `protocol_stack_id=ps-expeditionary-wastewater-graywater-vector-control-stack-v1` when force-health posture depends on wastewater containment, graywater routing, or vector suppression around dense expeditionary sites.
- Add `tool_suite_id=ts-joint-launch-toxic-propellant-cloud-public-protection-v1` + `protocol_stack_id=ps-joint-launch-toxic-propellant-cloud-public-protection-stack-v1` when inhalation exposure, contaminated downwind corridors, or shelter-capacity limits materially affect medical-risk decisions.
- Add `packet_id=DPL-WASTEWATER-VECTOR-CONTROL-001` and `packet_id=DPL-LAUNCH-TOXIC-PROPELLANT-CLOUD-001` for branches that materially alter sanitation posture, exposure protection, or evacuation-health support.

## Domain Toolchain Override (2026-04-07, Expansion Wave LXXXIV Addendum)

- Add `toolchain_id=TC-BURNPIT-338`, `tool_suite_id=ts-joint-airborne-hazard-burn-pit-pact-act-toxic-exposure-registry-continuity-v1`, and `protocol_stack_id=ps-joint-airborne-hazard-burn-pit-pact-act-toxic-exposure-registry-continuity-stack-v1` when force-health posture depends on preserving burn-pit, airborne-hazard, or toxic-exposure evidence long enough to drive registry enrollment, specialty follow-up, or lawful benefits documentation.
- Add `toolchain_id=TC-PDHAIMR-339`, `tool_suite_id=ts-joint-post-deployment-health-assessment-imr-duty-limitation-recovery-v1`, and `protocol_stack_id=ps-joint-post-deployment-health-assessment-imr-duty-limitation-recovery-stack-v1` when commander risk depends on closing PDHA or PDHRA gaps, correcting IMR drift, or recovering duty-limitation follow-through after redeployment.
- Add `packet_id=DPL-BURN-PIT-PACT-ACT-EXPOSURE-001` and `packet_id=DPL-POST-DEPLOYMENT-HEALTH-IMR-001` for branches that materially alter surveillance posture, deployability confidence, or protected-health follow-up timing.