Quick-Start

Field-ready Offline-first MCMS training

TriageForce — Quick‑start Manual

TriageForce is an MCMS (mass casualty management) web app for triage, tracking and operational reporting, including degraded networks and offline acquisition.

This manual updates automatically when you deploy a new plugin build. Current build: 3.0.0-dev-3.2.9.
Online
Ops • Field mode • One-hand
Active event #1018 — Croix du Sud
Scan QR
+ New victim
Victims
Sync
Victims map • last positions
Field workflow: select event → scan ID → triage → track updates. Designed for mobile operations, with “one‑hand mode” and offline queuing.

Concrete scenarios (exercise‑ready)

Use the examples below as a training teaser and a quick reference for new users.

Scenario 1 — Field triage line (60 seconds)

On scene: identify, triage, and record the first tracking point fast — even with weak connectivity.

  1. Select the active event (or create one).
  2. Scan the victim ID (QR / Code128).
  3. Set triage: RED YELLOW GREEN BLACK
  4. Save — if offline, the action is stored locally as pending.
Tip: keep the main CTAs reachable with your thumb (one‑hand mode).
Scenario 2 — Command post view (live picture)

At the CP / OPS: review totals by gravity code and validate casualty locations.

  • Open Victims to see the list filtered on the active event.
  • Use the map to quickly spot clusters and outliers.
  • Verify last tracking updates before evacuation phases.
Objective: a common operational picture across teams.
Scenario 3 — RETEX / reporting (Excel export)

After the drill: export data to Excel for MCMS reporting, statistics and debrief.

  • Export includes: victim fields + last tracking + location + gravity code.
  • Use filters / pivot tables to build a quick RETEX.
  • Admins can also inspect plugin logs for debugging.
Deliverable: a clean XLS for the exercise timeline.

Victims view: list + map + last tracking

This is your operational picture: a fast list (IDs, gravity code, last update) combined with a live map. Tap a row or a pin to open the record and log a new tracking update.

  • List: filter by the active event, search by QR/ID, see the last tracking at a glance.
  • Map: pins represent the last known position; pin color = gravity code.
  • Status: offline entries appear as Pending local until synced.
Legend: Red Yellow Green Black
Reporting: the “Expert XLS” export includes victim fields + last tracking + location + gravity code for RETEX.
Offline
Victims • Active event
Search QR / ID / name
Pending local: 2
ID
Triage
Last track
Status
FR‑1018‑0005617
Triage
Synced
FR‑1018‑0005618
Evac
Pending
FR‑1018‑0005619
CP
Synced
Map • markers clustered

Victim record: fast edits + tracking timeline

When you open a victim, you get a simple record designed for speed: update triage, add tracking steps (Triage → CP → Evac → Hospital…), and keep the last known position.

  • Add tracking in one tap (one‑hand CTA).
  • Last tracking is always visible (location + time).
  • If offline, updates are queued and marked Pending local until synced.
RED
Victim • Record
Victim ID FR‑1018‑0005617
Gravity Last: Evac GPS ✓
Tracking timeline
Triage08:41
CP08:52
Evac09:05
+ Add tracking

PWA / install on phone (optional)

  • Android (Chrome): menu → Install app.
  • iOS (Safari): Share → Add to Home Screen.
  • Once installed, TriageForce can start faster and cache key assets for offline work.
Important: TriageForce is primarily intended for MCMS exercises and training simulations. Always follow your organization’s operational doctrine and medical protocols.
Print labels PDF triage sheet Excel export

Labels, PDF & Reporting

Prepare IDs before the exercise, print triage materials, then export a clean Excel file for debrief.

Tip: for accurate printing, keep browser print scale at 100% (no “fit to page”).
Print
3×8 sheet • A4
Label sheet preview (QR / Code128)
Generate → Preview → Print / Export PDF (browser).

Before the exercise (recommended)

1 — Prepare ID labels

Print a batch of QR / Code128 labels (e.g. 3×8 per page) and attach them to wristbands.

  • Keep pages dry / protected (field kit).
  • Reserve enough IDs for the whole scenario.
2 — Prepare a triage sheet (PDF)

Use the printable casualty triage sheet when paper is required on scene.

  • Write unit / hospital in the footer.
  • Use B&W mode when colour printing is unavailable.
3 — Test offline behaviour

Put a phone in airplane mode, create a victim, then reconnect to validate sync.

  • Victims created offline should show Pending local.
  • Sync should clear the pending queue when online.

After the exercise

Excel export: use the “Expert XLS” export from the Victims page to obtain victim fields + last tracking + location + gravity code (filtered on the active event).
  • Use Excel filters to split by triage category or evacuation phase.
  • Share the file with the exercise control team for consolidation.
  • Admins can consult the plugin logs in WordPress backoffice (Debug on/off).