00 — Fire & EMS records platform
Fire & EMS records, rebuilt for the AI era.
One incident record that produces NERIS fire reports and NEMSIS EMS reports. AI that drafts, checks, and explains every report — with a human signing off. Connected to the systems your agency already runs, on your cloud or your own servers.
- Built to NERIS & NEMSIS v3.5
- Human-approved AI
- Any cloud or on-prem
01 — Why now
Every call is a record worth reading.
Source: NFPA data (2023), via the National Volunteer Fire Council.
Two-thirds of fire department calls are medical, yet fire and EMS reporting usually live in separate systems. Now the national fire standard is changing from NFIRS to NERIS, and EMS reporting must meet NEMSIS v3.5. Systems built around paper-era forms are being patched for both — so crews re-key the same call twice, and reports fail validation long after the crew has gone home.
02 — The standards
NERIS and NEMSIS. One record.
Firemarq captures an incident once and produces both reports: NERIS for the fire side, NEMSIS v3.5 for patient care. The data model follows each standard's structure, and validation runs while the report is being written — not after it's rejected.
- Dispatch & unit response
- Location & exposures
- Actions & tactics
- Casualty & rescue
- Risk reduction
- Emerging hazards
- Patient care (NEMSIS)
- State EMS submission
Built to the NERIS and NEMSIS v3.5 specifications. Certification testing is in progress — we'll say “certified” when it's official.
◆ — Product preview
One screen. Both reports. Fewer re-keys.
A company officer finishes a structure fire with a patient transport. Firemarq has already pulled the CAD times and units, linked the patient care record, drafted the narrative, and flagged what NERIS will reject.
Timeline from CAD
- Dispatched
- 14:02:11
- En route
- 14:03:05
- On scene
- 14:07:40
- Fire control
- 14:31:02
Units
Actions & tactics
Patient care NEMSIS
Narrative draft AI · needs your review
Engine 1 arrived at 14:07 to smoke showing from the second floor, C/D cornerCAD. Crew advanced an attack line through the A-side entrance while Ladder 1 completed the primary search, negativeL1 notes. Fire was controlled at 14:31CAD. One occupant was evaluated for smoke inhalation and transported by Medic 1ePCR.
Before you submit
- NERIS Smoke alarm presence is missing (risk reduction).
- NERIS Narrative mentions a D-side exposure; exposures count is 0.
03 — AI that rides along
Intelligence that rides along.
AI should make the officer faster and the record better — never make the decision. Every Firemarq AI feature shows what it read, what it suggests, and who approved it.
ANarrative copilotCompany officers
Claude drafts the incident narrative from CAD timestamps, unit notes, crew input, and the linked patient care record — citing the source of each sentence. The officer edits, then signs. Nothing is submitted without a human.
- Reads
- CAD times, unit notes, ePCR
- Suggests
- A draft narrative with sources
- Decides
- The reporting officer
BQA before submissionRecords managers
Missing, contradictory, or out-of-range fields are flagged against NERIS and NEMSIS rules before a report leaves the station — with the reason and the fix.
- Reads
- The draft report and both rule sets
- Suggests
- Specific corrections
- Decides
- The records manager
CAsk your dataChiefs & analysts
Plain-language questions — “How did turnout times change on B-shift after the new station opened?” — answered with a chart and the exact query shown, so every number can be checked.
- Reads
- Your incident data
- Suggests
- Charts and the query behind them
- Decides
- You
DLive situational insightCommand staff
CAD events, prior incidents at the address, pre-plans, and known hazards summarized for the incident commander while units are still responding — the kind of fire-attack decision support now being piloted in the field.
- Reads
- CAD events, history, pre-plans
- Suggests
- Hazards, exposures, resource gaps
- Decides
- The incident commander
The 3D fireground on this page is a concept visualization, not live data.
◆ — Integrations
Connects to what you already run.
Records are only as good as the data flowing in. Firemarq is designed to sit in the middle of your agency's systems, so information is entered once and reused everywhere.
NERIS submission for fire; NEMSIS v3.5 export to state EMS repositories.
Incident, unit, and timestamp data from CAD platforms such as Hexagon OnCall.
Pre-hospital care coordination with platforms such as Pulsara.
Real-time call and unit status feeds for situational awareness.
Addresses, occupancies, and hazards attached to every incident.
Documented API, webhooks, and open formats. Your data, always portable.
Product names are trademarks of their respective owners and are listed to show planned compatibility, not partnership or endorsement.
04 — Anywhere
Yours to run. Anywhere.
Your records belong to your department. Firemarq ships as containers on an open-source database stack, so you choose where it lives — and you can always take your data with you.
- Security by designEncryption in transit and at rest, role-based access, and HIPAA-aligned handling of patient data are design requirements.
- Model choiceClaude via Anthropic's API or your cloud's model service.
- Audit trailEvery AI suggestion is logged with its inputs and approver.
05 — The company
Built from the station up.
Our aim is to rebuild how the fire service records, understands, and acts on every call — starting with the report every crew has to file.
- NowNERIS + NEMSIS data model, validation, and exports
Built to spec; certification testing in progress.
- NextNarrative copilot, pre-submission QA, founding pilots
First agencies shape the workflow with us.
- ThenCAD and patient-handoff integrations, ask-your-data analytics
Starting with platforms our pilot agencies run.
- LaterReal-time fireground insight for command staff
Decision support built on clean, connected records.
“I've spent my career between the fire service and software — running data and AI pilot programs and architecting systems. Firemarq exists to build technology that genuinely helps the people who save lives and property, and to serve them with honor, pride, and integrity.”
Vinay DanepalliFounder, Firemarq · founder@firemarq.com
Questions agencies ask
Is Firemarq certified for NERIS and NEMSIS?
Firemarq is built to the NERIS and NEMSIS v3.5 specifications and certification testing is in progress. We'll publish certification status when it's official — not before.
Who owns our data?
You do. Firemarq runs in the environment you choose, exports in open formats, and never uses your agency's data to train shared models.
Does the AI submit reports on its own?
No. AI drafts and checks; a named person reviews and signs every report. Every suggestion is logged with its inputs and approver, and AI features can be switched off per module.
Can we bring our history from our current system?
We're building a migration assistant to map existing exports, including NFIRS-era records, into the new data model. Pilot agencies help us prioritize which systems come first.
What does the founding pilot involve?
A small group of agencies gets early access, direct input on the roadmap, and founding pricing. We'll start with a conversation about your workflow and systems.
Join the founding pilot
We're looking for a small group of fire and EMS agencies — career, combination, or volunteer — to shape Firemarq with us. Pilot agencies get direct input on the roadmap and founding pricing.
Your details go only to the Firemarq founder and are used only to contact you about the pilot. Expect a reply within two business days.