Fire/EMS Encryption: Beyond Police
As police encryption becomes routine, fire and EMS departments are following, removing another layer of public access to emergency information
The Expanding Encryption Trend
Police radio encryption dominates the public debate, but fire and EMS agencies are encrypting with less resistance and less coverage. The trend gets less scrutiny and the stakes are just as high.
The arguments and politics differ from police encryption in several ways:
Police encryption
- Justified by officer safety, criminal monitoring
- Significant First Amendment implications
- Affects crime coverage, accountability
- Controversial, widely debated
Fire/EMS encryption
- Justified by patient privacy (HIPAA)
- Less First Amendment focus in debates
- Affects emergency awareness, traffic info
- Often implemented quietly
NOAA weather: the public-safety transparency model fire/EMS should follow
Fire and EMS departments using HIPAA as cover for dispatch encryption are ignoring a federal agency that got this right decades ago. NOAA weather radio is unencrypted, unrestricted, and mandatory—because warnings don't work if they're locked. That's what public-safety transparency looks like. Until fire/EMS follows suit, here's the stack listeners rely on.
Currently encrypted fire departments
These agencies have encrypted dispatch or all communications as of early 2026:
Planned or announced
The HIPAA justification
Fire and EMS departments frequently cite HIPAA as the main reason for encryption. The argument doesn't hold up under scrutiny:
The claim
"We must encrypt to protect patient privacy under HIPAA. Broadcasting medical information violates federal law."
The reality
- HIPAA doesn't mandate encryption—it requires "reasonable safeguards" but doesn't specify radio encryption
- EMS agencies have operated with open radios for 50+ years without widespread HIPAA enforcement
- HHS has not pursued HIPAA violations against fire/EMS agencies for radio transmissions
- If HIPAA truly mandated encryption, all EMS would be encrypted—it isn't
What experts say
HIPAA requires "appropriate administrative, technical, and physical safeguards" to protect patient information. Radio encryption is one possible safeguard, but not the only one. Training dispatchers to minimize identifiable information, using coded language, or transmitting sensitive details via MDT are alternatives that preserve public access.
Case study: Northwest Chicago suburbs
The Northwest Central Dispatch System (NWCDS) provides a clear example of coordinated fire encryption:
13 fire departments encrypt simultaneously
NWCDS Executive Director John Ferraro cited "scene safety," borrowing directly from police encryption arguments. Fireground tactical channels stayed open, which undermines the stated rationale.
Read the full Chicago Fire case study →Case study: Toms River, NJ
Toms River Fire District 1 became New Jersey's first and only fully encrypted fire department in January 2025:
New Jersey's first encrypted fire department
Fire chiefs across Ocean County formally opposed the decision. Officials went ahead anyway, then issued gag orders and required neighboring departments to sign NDAs. The case shows that professional opposition doesn't stop fire encryption from moving forward.
Read the Toms River investigation →Why fire encryption matters
Fire and EMS radio carries public information that extends well beyond emergency response:
Emergency awareness
Structure fires, hazmat incidents, and mass casualty events affect entire neighborhoods. Real-time radio lets residents know when to shelter in place or evacuate.
Traffic information
Radio traffic reporters and navigation apps use fire/EMS channels to identify accidents and road closures faster than official sources.
News coverage
Journalists use fire scanners to cover breaking emergencies. Encryption means waiting for official statements that may be delayed or incomplete.
Accountability
Response times, resource decisions, and incident communications can be independently verified when radios are open.
The interoperability issue
When one agency encrypts and neighboring agencies don't, multi-agency coordination breaks down:
Common multi-agency scenarios
- During structure fires with rescues, fire crews need to know police status for scene safety
- Vehicle accidents require EMS, fire, and police to coordinate traffic control and patient care
- Fire/EMS staging at active shooter incidents depends on knowing police tactical status
- Hazmat events require evacuation coordination across all agencies
When one agency encrypts and another doesn't, radio interoperability breaks down. This is increasingly common as police encrypt but fire departments lag behind—or as fire departments encrypt before police.
Alternatives to full encryption
Patient privacy can be protected without locking down the whole system:
Training and protocol
Train dispatchers and crews to avoid broadcasting identifiable patient information. Use unit numbers instead of addresses for ongoing calls.
Mobile data terminals
Transmit sensitive patient information via encrypted MDT text rather than voice radio. Many departments already do this.
Selective encryption
Encrypt only EMS channels with patient information. Leave fire dispatch and fireground tactical channels open.
Delayed feeds
Implement a 5-minute delayed public feed (like Boston's model) that removes sensitive information but preserves access.
What fire leaders should know
If your region is considering fire/EMS encryption, these resources can help:
Take Action
Monitor your local agencies
Check if your fire/EMS department has announced encryption plans. These decisions often happen quietly at board meetings.
Attend public meetings
Fire district boards and city councils make these decisions. Public comment can influence outcomes.
Contact local media
Journalists may not realize fire encryption affects their coverage until it's too late. Alert them to proposals.
Request alternatives
Push for selective encryption, delayed feeds, or media access programs instead of full encryption.
Stay informed
Fire/EMS encryption is accelerating. Case studies and resources below.