Alpha Command

Client briefing · Alpha Event Medicine

Alpha Command

The physician-built command platform for mass-gathering medicine — one live picture from event stand-up to after-action report.

Physician-founded & led ~225 providers KY · OH · IL · MO · IN Privacy by default
01

The problem

Mass-gathering medical operations still run on radios, paper, and hope — no shared live picture, no closed loop on who's responding, and no evidence of how it actually went until someone reconstructs it from memory.

No shared picture

Command can't see where teams are or which care center is under load.

Open-ended dispatch

A radio call goes out; whether it was heard, acknowledged, or acted on is anyone's guess.

No evidence after

Response times and outcomes are estimated later, not measured as they happen.

02

The answer

Built by the physicians who run these events.

Alpha Command is purpose-built for event medicine by a physician-founded, physician-led company — not a generic dispatch tool adapted after the fact. It gives command one live, accountable system of record for the whole operation.

  • Wristband patient identity, offline-capable
  • Live provider map + closed dispatch loop
  • Weather, alerts, and an automatic after-action report
Abstract illustration of the event command console: live venue map, command board, and dispatch card Event Command — Live Gate 3 · Infield · Grandstand georef overlay Live provider AVL · satellite imagery Command Board care centers Infield Aid2 providers · clear OK Grandstand West1 open case · heat watch WATCH Gate 3 Medactive dispatch SURGE Dispatch #4821 Assign → Gate 3 Med assign alert ack en route acknowledged in 0:12 · on live board

Product illustration — the live operating picture.

03

Platform · patient identity

Wristband identity that survives dead zones.

Scan a wristband to track a patient through the event. Scan-to-track is offline-capable and syncs when connectivity returns — and it's pseudonymous, so there's no PHI in the field view.

  • Offline-capable scan-to-track
  • No PHI on the operational layer
  • Every scan timestamped & attributed
Wristband patient identity being scanned by a phone, working offline wristband ID Scan to track offline OK PT-7Q2 tracked care center · time · status Offline-capable scan-to-track · syncs when connectivity returns · no PHI on the operational layer

Product illustration — no patient data.

04

Platform · situational awareness

Every provider on the map, on your venue.

A live provider AVL map on satellite imagery, with your own georeferenced venue map on top and named care centers pinned in place. Command sees the operation, not a mental model.

  • Live provider locations on satellite imagery
  • Uploaded georeferenced venue maps
  • Named care centers pinned in context
Live provider location map on satellite imagery with a georeferenced venue overlay uploaded georef map Live provider AVL available en route on scene

Product illustration — abstract map.

05

Platform · accountable dispatch

A dispatch loop that closes and times itself.

Assign a case, the provider's phone alerts, and each step returns to the live board. Because the loop closes, response times are measured — not estimated.

  • Assign → alert → acknowledge → en route → on scene
  • Timed at every transition
  • Reflected on the board in real time
The closed dispatch loop: assign, phone alert, acknowledge, en route, on scene, back to the live board Live Board assign phonealert acknowledge en route /on scene resolve /update Every status change is timestamped, attributed, and reflected on the board in real time.

Product illustration — the closed loop.

06

Platform · command board

One board per event, with the care centers you named.

Stand up a command board with named care centers, live staffing, and open cases — while a configurable alert engine watches for surge, heat, severe weather, and response timeouts.

  • Per-event boards, named care centers
  • Configurable real-time alerts
  • Nothing hard-coded — thresholds per event
Per-event command board with named care centers and status Command Board live Infield Aid Care center 01 CLEAR 2 staff Grandstand W Care center 02 WATCH 1 open Gate 3 Med Care center 03 SURGE 3 staff Open cases by care center · acuity Gate 3 Med · in progress Grandstand W · monitoring Infield · resolved Infield · resolved

Product illustration — command board.

07

Platform · weather & surge

Heat and weather, on the same screen as the medicine.

WBGT, radar, and NWS alerts are integrated into the operating picture and feed the alert engine directly. The workflow is engineered and tested for mass-gathering surge.

  • WBGT / radar / NWS integrated
  • Auto-surfaced to command
  • Engineered & tested for surge
Weather, WBGT heat index, radar, and NWS alerts integrated into the operating picture WBGT heat 84° flag: yellow activity guidance by threshold Radar ! NWS alert Heat advisory · zone active auto-surfaced to command Conditions Temp91°F Humidity63% Wind12 mph Lightningnone SourceNWS feeds the alert engine

Product illustration — values illustrative.

08

Buyer concern · accountability

Prove who did what, and how fast.

Access is per-person and authenticated; every action is attributed and timestamped. The record is built as the event runs — there are no anonymous actions.

  • Per-person authenticated access
  • Full audit attribution
  • Response times measured from the loop
Per-person authenticated access with full audit attribution on every action Per-person access authenticated named identity role-scoped access Audit trail every action · attributed 09:41:02 J. Rivera assigned case → Gate 3 09:41:14 M. Chen acknowledged 09:43:50 M. Chen on scene 09:52:11 M. Chen resolved 10:03:27 Command board note added 10:07:09 A. Patel care center staffed Immutable, timestamped, who-did-what — no anonymous actions. (Names illustrative.)

Product illustration — names illustrative.

09

Buyer concern · privacy

No PHI on the layer everyone touches.

The operational layer runs on pseudonymous tokens and operational facts. Protected health information is handled by a separate, HIPAA-grade datastore architecture designed with a signed-BAA path.

  • Privacy by default — no PHI operationally
  • HIPAA-grade PHI datastore architecture
  • Designed with a signed-BAA path
Privacy-by-default architecture: no PHI on the operational layer, separate HIPAA-grade PHI datastore behind a signed-BAA path Operational layer no PHI PT-7Q2 · trackedpseudonymous token only Care center · time · statusoperational facts, not identity Board · dispatch · AVLruns entirely PHI-free what every operator sees signed-BAA path PHI datastore HIPAA-grade, by design separate · access-controlled designed for a signed BAA

Product illustration — architecture.

10

Live demo · right now

Watch a live event, right now.

Close the deck. In the next few minutes, on your venue, you'll see the whole loop run — start to evidence.

The live demo flow: a live command board on the venue, a dispatch to a phone, and the after-action report in the inbox Command Board live Infield Aid2 staff · clear Grandstand W1 open · heat watch Gate 3 Medactive dispatch your venue Dispatch#4821 New case Gate 3 Med · assign Acknowledge the presenter's phone After-actioninbox Event report · ready P50 P90 zero-PHI before we leave
  1. 1

    A live command board on your venue

    Care centers, staffing, and open cases — on your event.

  2. 2

    A dispatch to the presenter's phone

    Assign a case; it alerts a phone in the room.

  3. 3

    The after-action report in your inbox before we leave

    Automatic, zero-PHI, with response-time percentiles.

11

The deliverable

Every event ends with evidence.

Close the event and receive an automatic, zero-PHI after-action report with response-time percentiles — the documentation a risk manager needs, without anyone staying late to build it.

  • Automatic on event close
  • Response-time percentiles
  • Zero-PHI, safe to share
Illustrative layout of the automated, zero-PHI after-action report with response-time percentiles After-Action Report Event ____ · Date ____ · generated automatically zero-PHI Total encounters Median response Transports Response-time percentiles p50 p75 p90 p95 Sections Executive summary Encounter overview Response times By care center Weather & alerts Timeline & audit Illustrative layout — not real event data.

Illustrative layout — not real data.

12

About Alpha Event Medicine

The standards-writers built the software.

Alpha Event Medicine is physician-founded and physician-led. Our founder is an emergency medicine professor who chairs the ACEP Event Medicine Section. Alpha Command reflects how event medicine is actually practiced.

~225
providers
5-state
footprint
ACEP
Section chair
Physician-led: a clinical command center at the center of a provider network Physician-founded & physician-led · providers across a five-state footprint

Physician-led provider network.

13

Built for mass gatherings

Made for the venues where minutes matter.

Our providers work premier horse racing, arenas, and stadiums across five states — and the platform is engineered and tested for mass-gathering surge.

Premier venues

Horse racing, arenas, and stadiums — the highest-density live environments.

Five-state footprint

Active across KY, OH, IL, MO, and IN.

Surge-tested

Engineered and tested for mass-gathering surge.

14

Engagement model

Physician-led services, on our platform.

Event medical services

Physician-led clinical staffing and event medical operations, delivered by our provider network across the region.

Alpha Command platform

The command platform running underneath every engagement — the live operating picture and the after-action evidence.

Commercial terms — to be discussed
15

Let's talk

See Alpha Command run your event.

Bring your venue and your risk questions — we'll walk you through the live operating picture and the after-action report you'd receive.

brian@alphaeventmedicine.com

Alpha Event Medicine · physician-founded & physician-led event medicine

16