TCCC-compliant casualty card management integrated directly into ATAK. Track every casualty using the MARCH protocol, manage Casualty Collection Points (CCPs) on the map, and let the AI agent generate medevac briefs and triage summaries without leaving the tactical picture.
Every casualty record in the system mirrors a standard TCCC card: mechanism of injury, triage category (T1–T4), MARCH protocol findings, treatment rendered, and the CCP the patient was evacuated to. Records are stored in DuckDB and are immediately queryable by the AI agent for triage summary generation and medevac planning.
BRAVO-2 takes a round through the leg during a barricade standoff. The medic creates a TCCC card via the Tactical Med widget: mechanism = GSW, category = T1, tourniquet applied, CCP Bravo assigned. The AI agent is immediately queried by the IC: “Give me a 9-line medevac brief.” The agent reads the DuckDB record and formats the MIST report in seconds, ready to transmit to air medical.
Each casualty record supports the full MARCH protocol assessment to ensure no critical finding is missed or undocumented during the tactical phase.
CCPs are created with a name, grid coordinate, and capacity. Each CCP is broadcast as a CoT marker so all ATAK clients see CCP locations on the map. The AI agent can query CCP load across the entire incident: “Which CCP has the most capacity?”
tactical_medThe tactical_med AI agent tool bridges the TCCC data layer with natural language. Medics and commanders can query casualty counts by category, generate triage summaries, or instruct the agent to assign a patient to the nearest CCP based on map proximity.
At the end of a complex active-shooter incident with multiple casualties, the incident commander asks: “How many T1 patients do we have and where are they?” The agent queries the TCCC table, groups patients by triage category, maps them to their CCP assignments, and returns a summary that feeds directly into the ICS-206 medical plan.