MGMIMass Gathering Medicine

← State of the Evidence

Comms & ICS State of the Evidence v0.1

Communications, Command & Surveillance — State of the Evidence

Revised: 2026-08-16 (v2) — supersedes the 2026-08-08 draft. What changed: the 2026 Purple Guide tranche adds a command-architecture layer the domain lacked — transfer and return of primacy, partial primacy, the mesh command structure, the competence-gap provision, restricted-channel rules for child incidents, and the common-operating-picture requirements (gridded plans, identical naming across agencies). The domain remains doctrine-heavy and trial-free; that framing is unchanged.

Bottom line for practitioners

This is the thinnest domain in MGMI, and that thinness is the finding. Communications, incident command, and surveillance are where mass-gathering medicine most resembles doctrine and least resembles science: what exists is consensus guidance (NAEMSP), binding UK venue guidance (SGSA), industry guidance with statutory-responder co-authorship (the Purple Guide's Contingency chapter), and a small number of feasibility demonstrations for real-time surveillance at very large religious gatherings. There is no comparative study in this collection testing whether any communications architecture changes patient outcomes. Practitioners should treat the doctrine below as the professional floor — it is coherent, specific, and auditable — while understanding that its evidentiary basis is expert consensus plus hard-won institutional experience, not trials.

What the doctrine requires

Channel discipline. The NAEMSP position statement requires multiple interoperable communication modes for redundancy, trialed before the event; a dedicated medical channel separate from both event operations and the surrounding jurisdiction's traffic; an interface with the host-jurisdiction PSAP; and a predesignated MCI channel — all documented on ICS Form 205, with the Medical Plan on ICS Form 206 and the Safety Plan on ICS Form 208. It also assigns social media a dual role: early incident detection and public information [1].

Control point and the Medical Plan. The UK Green Guide embeds communications inside the Medical Plan itself: its 16-element checklist (§18.6) includes communications among the medical team, with safety management, and with external services, alongside command structure, call categorisation, triage, and casualty-clearing arrangements. The control point is the fixed hub — the Event Doctor must be in position before gates open, with whereabouts known to the control point until stood down [2]. On a declared major incident, all medical staff pass under the senior statutory ambulance officer, which is why written handover protocols are required in advance [2].

Language, escalation, and the log. SGSA's SG03 supplies the operational grammar. First reports use pre-agreed terms and Operations-Manual site-plan names. Emergency codes must make it immediately obvious whether an incident is fire, crowd-related, medical, a suspicious object, or terrorist. Responders report casualty numbers and condition to the control point on an ongoing basis "using pre-agreed terms and classifications." UK doctrine references M/ETHANE reporting and JESIP interoperability principles; command generally remains with the Safety Officer even when emergency services assist, transferring only via pre-agreed protocols. Every incident is logged with time, location, reporter, decision-maker, action, and outcome — and near-misses are explicitly logged and reviewed post-event [3].

The command architecture — new in v2

The Purple Guide's Contingency & Emergency Planning chapter (working group includes an NHS ambulance service and a fire and rescue service) fills in the command layer between "the Safety Officer holds command" and "the statutory services take over," and its provisions answer questions US event plans routinely fudge [4]:

- Transfer of primacy is defined — a major emergency passes control of the site from the organiser to a statutory service — and so is partial primacy: command can split geographically, the emergency services owning the cordon while the organiser retains control, including medical operations, everywhere else. For an event medical director this resolves a recurring ambiguity: when the ambulance service declares a major incident, the event medical team does not stop — it runs everything outside the cordon and supplies staff to the incident commander. Two jobs at once, which is a staffing implication nobody plans for. - Primacy has a return path. The Crowd Management chapter specifies a signed Return of Authority form releasing control back to the organiser once risk is tolerable — the closing bracket US plans almost never write [5]. - Command is a mesh, not a pyramid. The management structure is "set up in a mesh, or similar, format": leadership shifts to whoever owns the hazard type, rather than routing everything through one fixed incident commander — a genuine structural alternative to ICS worth naming when teaching command. And the provision most plans lack: organisers must ensure decisions can still be made when the designated person is absent or outside their competence — the failure mode inquiry reports keep finding. - Agreements to strike in advance: access and emergency routes, grid-referenced maps, rendezvous points, and the primacy protocol — via consultation with police, fire, ambulance and the local authority, typically through the Safety Advisory Group. - Depute forward; command stays back. From the chapter's escalation worked example: send a deputy to the scene while the event manager remains at event control — "if everyone heads to the incident, it is difficult to make/consider strategic issues." The classic command failure, named, and it applies squarely to medical leadership. The same example requires designated staff to meet and brief arriving emergency services and maintain liaison.

The common operating picture is a design requirement, stated three ways. Campsite layouts must be "fully integrated between the various agencies involved, so that the site features and descriptions of locations are identical for all the agencies" [6]; site plans are gridded "to assist in identifying locations on site in an emergency," version-controlled, and distributed current to "stewards, first-aid and welfare teams" [7]; and colour-coded festoon zones give campers and workers an orientation vocabulary at night [6]. If the medical team and the fire service name the same field differently, the dispatch is wrong — this is a communications requirement living inside site-design chapters.

Restricted channels exist, and child incidents are the case. Safeguarding doctrine prohibits broadcasting a lost child's name or personal details on PA or open radio; worker communication about missing/found children runs face-to-face, by telephone, or on a dedicated channel [8]. That is a channel-discipline rule with a privacy rationale — the broadcast instinct is the restricted act — and it belongs in the ICS 205 conversation alongside the medical and MCI channels.

Public messaging is pre-scripted. Show-stop and contingency doctrine requires pre-agreed announcement texts, pre-recorded messages, and advance screen/stage visuals — with a designated audience communicator and a competent alternative, because some performers cannot address a crowd in an emergency [5]. The audience may be slow to react mid-performance; the performer is the highest-authority channel on site, which makes the show-stop script a negotiation with the touring production, not just a document.

What the research shows

Real-time surveillance at scale is feasible. The strongest empirical entry is Lami's cross-sectional study of the 2016 Arbaeenia pilgrimage: 60 data collectors captured 41,689 patients over 11 days from 20 health outlets along the Najaf–Karbala route. Presentation mix (categories overlap): 58.5% acute/infectious conditions, 33.1% chronic conditions, 23.9% trauma or injury, and 28.2% joint pain attributed to long-distance walking [9]. This is a working model — collectors, outlets, a route, a live feed — not merely an aspiration.

Communicable-disease surveillance has an outcome-adjacent literature. Goumballa's PRISMA systematic review of SARS-CoV-2 transmission at religious mass gatherings found ten studies across six major events: no cases detected at the 2020 Hajj or 2020/21 Grand Magal of Touba; 7% positivity after the 2022 Grand Magal; 0–15% prevalence across 2021–22 Hajj/Umrah studies; 3% of 2021 Arbaeen pilgrims positive; and roughly 0.4 million COVID-19 cases diagnosed among returning Kumbh Mela pilgrims across India. Outcomes were highly dependent on mitigation, density, and background prevalence [10]. The Lancet mass-gatherings literature on communicable and non-communicable risk is held in the domain but unextracted [11] [12].

A surveillance channel nobody wires up: the medical tent itself. The Crowd Management chapter requires trained crowd spotters in elevated positions, on a pre-agreed protocol to event control, as the detection layer for crowd collapse and excessive density [5]. The medical team is a second, independent sensor — a cluster of syncope or crush presentations from one sector is density data that arrives at the tent, not the barrier — but the listed show-stop decision group contains no medical lead, so that signal has no defined route to the decision. A presentation threshold routed to control is the cheap fix, and it is a comms-architecture change, not a staffing one.

Conceptual anchors only. Auf der Heide's argument that disaster planning rests too often on untested assumptions — with communications among the classically cited failure points — frames why this domain matters, but MGMI holds citation only, no extracted content [13] (unextracted). The same applies to crowd-monitoring as a surveillance input [14] (unextracted).

What's honestly thin

The extracted core remains small; most shelf documents are cited for existence only [15] [16] [17] [18] [19] (all unextracted). There are no comparative studies of communications architectures in this collection. There is no US surveillance standard equivalent to what Lami demonstrated ad hoc. The Purple Guide chapters are chapter-level extractions with unread remainders — notably the Contingency chapter's own Communications section, which is among its unread sections and should be read before this synthesis is next revised. None of this makes the doctrine wrong; it makes it untested.

What we don't know

- Does a dedicated medical channel, versus shared event-operations traffic, measurably change response times or patient outcomes? No entry addresses this. - What is the return on syndromic surveillance at ordinary events — a 20,000-seat stadium, not a multi-million-person pilgrimage? The feasibility evidence is all from the largest religious gatherings. - How often do interoperability failures (channel, terminology, triage-category mismatch) occur at US venues, and with what consequences? The near-miss data that would answer this is exactly what SG03-style event logs would capture — and what is not being systematically collected or published. - Does the mesh command structure outperform, underperform, or simply differ from fixed-commander ICS at events? Named here as a structural alternative [4]; no comparative evidence exists.

How MGMI operationalizes this

The composer's communications line implements the convergent doctrine: dedicated medical channel plus MCI channel (ICS 205) [1], control-point reporting in pre-agreed classifications, and medical-distinguishing emergency codes [3] [2]. To that it should now add: primacy provisions with a documented return path [4] [5]; a restricted-channel rule for child incidents [8]; a common-map requirement (gridded, version-controlled, identically named across agencies) [7] [6]; and a defined medical-to-control density signal. The registry carries a near-miss outcome category, directly importing SG03's logging discipline — creating, event by event, the dataset this domain lacks. Research-agenda hooks: channel-architecture comparisons, surveillance ROI at mid-size events, interoperability failure reporting, and mesh-versus-pyramid command.

Reading pathway

1. [1] — the US consensus floor for event medical communications. 2. [3] Ch.6 — incident management grammar: codes, casualty reporting, near-miss logging. 3. [2] Ch.18 — communications inside the Medical Plan and control-point structure. 4. [4] — primacy, partial primacy, mesh command, and the competence-gap provision. 5. [9] — what real-time surveillance looks like when actually built. 6. [10] — what surveillance found during COVID-era gatherings.

Citations

  • [1] NAEMSP Position Statement: Mass Gathering Medical Care. Prehospital Emergency Care, 2021. DOI 10.1080/10903127.2021.1903632.
  • [2] Guide to Safety at Sports Grounds ("Green Guide"), 6th ed. Sports Grounds Safety Authority, 2018. Ch.18.
  • [3] SG03: Event Safety Management, Digital Edition. Sports Grounds Safety Authority. Ch.6.
  • [9] Lami F, et al. JMIR Public Health Surveill, 2019. DOI 10.2196/14510.
  • [10] Goumballa N, et al. New Microbes New Infect, 2024. DOI 10.1016/j.nmni.2024.101442.
  • [4] · [5] · [8] · [6] · [7] Events Industry Forum, The Purple Guide, chapters published 2026-01-26 (chapter-level extractions; coverage and unread remainders in entry notes).
  • [11] Steffen R, et al. Lancet Infect Dis, 2012. DOI 10.1016/s1473-3099(11)70293-6. (unextracted)
  • [12] Memish ZA, et al. The Lancet, 2019. DOI 10.1016/s0140-6736(19)30501-x. (unextracted)
  • [13] Auf der Heide E. Ann Emerg Med, 2006. DOI 10.1016/j.annemergmed.2005.05.009. (unextracted)
  • [14] Johansson A, et al. Lancet Infect Dis, 2012. DOI 10.1016/s1473-3099(11)70287-0. (unextracted)
  • [15] NAEMSP. Mass Gathering Medical Care (position statement). (unextracted)
  • [16] FEMA. Special Events Contingency Planning (IS-15). (unextracted)
  • [17] Auf der Heide E. Disaster Response: Principles of Preparation and Coordination, 1989. (unextracted)
  • [18] WHO. Public Health for Mass Gatherings: Key Considerations, 2015. (unextracted)
  • [19] FEMA. NIMS/ICS core doctrine, 2017. (unextracted)