Operational events
Self-contained containers per deployment. Own incidents, own resources, own audit trail. The fair, the marathon, the holiday market each live in their own event.
Features
Every capability a real operation actually uses. None of the bloat.
ctHelixCAD™ was scoped from real after-action reviews — not enterprise feature checklists. Each capability earned its place because an operator asked for it in the field, the command tent, or the 24/7 dispatch center.
Posts & deployment positions
Geographic posts with map view. Build a reusable template library so each year’s plan is a clone, not a rebuild.
Master + event rosters
One master roster of personnel and apparatus. Clone any subset into an event. Multi-agency by default — filter, group, and color by agency, resource type, home station, or capability tag.
Resource types
Police, Fire, EMS, Security, and custom types. Filter, group, color-code so the board reads at a glance from across the room.
Incidents & CFS codes
Full incident lifecycle and a configurable CFS catalog — code, description, category, default priority, color, and safety-check intervals. Up to five CFS codes per incident for complex call types. Command aliases let keyboard dispatchers fly.
Pending & stacked calls
Earmark calls to specific units before those units are free. Many-to-many: one unit on multiple calls, one call across multiple units. When a stacked unit returns to AVL, dispatch gets a one-tap popup.
Transport-phase workflow
Phase buttons only — Depart, Arrive, Transfer of Care, Complete. Phase changes drive unit status automatically. Assignment is a plan; the unit doesn’t move until you say so.
Mileage tracking
Configurable rules prompt for mileage at the status transitions that matter — typically on AVL after a transport. Full audit trail linked to the originating incident. Aggregate mileage reports by unit.
Weather alerts & forecast
Real-time National Weather Service alerts for the event’s lat/lng — tornado, severe thunderstorm, flood, heat, civil emergency — plus a multi-day forecast. Server-side proxy with shared cache: a hundred dispatchers monitoring the same event = one upstream call.
Configurable numbering
Token-driven incident numbers: {YYYY}, {YY}, {MM}, {DD}. Annual, monthly, weekly, or ad-hoc cadences without operator math.
Live resource board
Real-time view of every unit — status, current incident, last known location, time-in-status. Socket.IO-backed updates across every dispatcher seat and every mobile client in the beat.
PDF reporting
Branded, server-rendered reports on demand — Event Summary, Daily Operations, Incident Listings, Resource Activity, Response Time, Mileage, Audit. The after-action document writes itself.
Audit trail
Every status change, every assignment, every note, every config edit timestamped and attributed. Filterable by user and date range. Defensible by design.
Permissions
Role-based, granular, agency-scopable. Dispatch staff, supervisors, command, and IT each see what they should — including a separate gate for license management.
Transport workflow
Phase buttons only.
No auto-status-on-create. Assignment is a plan; the unit doesn’t move until you say so. Dispatch decides when each phase begins, and the unit board, the patient record, and the audit log update together.
The result: post-event reconstruction matches what actually happened, not what the system assumed when the incident was first opened.
- 1
Depart
Unit leaves the post. Clock starts. Status auto-updates.
- 2
Arrive
Unit on scene. Patient contact begins.
- 3
Transfer of Care
Care handed off — hospital, family, releasing agency.
- 4
Complete
Unit clears. Reverts to available, ready for next call.
Numbering
Tokens, not spreadsheets.
Drop the same tokens into any operation’s numbering format. The system handles roll-over, padding, and uniqueness.
| Cadence | Format | Example |
|---|---|---|
| Annual fair | FEST-{YYYY}-#### | FEST-2026-0142 |
| Monthly market | MKT-{YYYY}-{MM}-### | MKT-2026-05-027 |
| Quarterly drill | DRILL-{YYYY}-{MM}-## | DRILL-2026-04-12 |
| Backup CAD | BCAD-{YY}{MM}{DD}-## | BCAD-260511-04 |
Tokens supported: {YYYY}, {YY}, {MM}, {DD}. Padding is configurable per operation.
Licensed add-on EMS Transport
Non-emergent transport and on-scene patient flow, on the same backbone as your 911 dispatch.
EMS Transport extends ctHelixCAD™ with patient management, multi-patient transports, treatment areas, billing data capture, and EMS-specific reporting. CAD-only — we capture the data, you keep your existing PCR. The module stays hidden until your license enables it.
Patient management
Per-incident patient roster: name, DOB/age, sex, chief complaint, triage tag number, triage category (Red/Yellow/Green/Black), status. Triage categories and patient statuses are configurable.
Treatment areas
Named on-scene zones (Triage, Minor Injuries, Morgue, etc.) with capacity, location, and supervisor assignment. Patient movement between areas is logged.
Destinations & facilities
Hospital and receiving-facility database — name, address, lat/lng, type (ED, urgent care, behavioral health, etc.). Drives the destination picker on every transport.
Multi-patient transports
Scene-to-facility transports with explicit phase timestamps: loaded, departed scene, arrived destination, transfer of care, cleared. Transport phase drives unit status automatically.
Service levels
Configurable transport categories — BLS, ALS, Critical Care, Cardiac, Bariatric, custom. Per-agency. Drives billing classification and reporting.
Non-emergent scheduling
Schedule discharges, dialysis runs, inter-facility transfers, and standing-order routes alongside live 911 traffic. Same board, same units, mixed-mode.
Billing data capture & export
Capture-and-export only. HCPCS codes for procedures and equipment. PCS expiration tracked per patient/template. On-demand export for your billing partner — we don’t produce 837P claims.
EMS-specific reporting
Patient Manifest (mass-casualty roster with triage, destination, and transport status) and Transport Log (per-transport timestamps end to end). Same PDF rendering as the rest of the suite.
HIPAA-friendly primitives
PHI tables scoped to the transport module, encrypted at rest. PHI audit log distinct from the general audit log. Role-gated access. Short admin session timeouts. (Final posture depends on how you deploy — talk to us about your framework.)
Capture the data. Keep your existing PCR.
We don’t replace your patient care report and we don’t produce 837P claims. EMS Transport captures the CMS-aligned data each transport needs and exports it for your billing partner.
Want a walkthrough of any of these?
Tell us the feature your team cares most about. We’ll start the demo there.