The VA Just Made Ambient AI Scribe a National Policy. The Medic Unit Is Next.
Robert Grand · Battalion Chief who still runs calls
Last week, the Department of Veterans Affairs announced that the ambient AI scribe technology piloted across VA medical centers starting in October 2025 will be deployed nationwide in 2026. Every VA facility. Every clinician on the platform. The pilot recovered roughly thirty minutes per provider per day in documentation time, and the agency framed it the way healthcare always frames these wins: clinician burnout, productivity, patient face time.
That precedent points right at the back of the box.
What The VA Just Decided
For people who don’t track federal health IT, here is the short version. Ambient AI scribe is the category of tools that passively listen to a clinician and patient conversation and produce a structured note as the output. No dictation step. No template-driven free text. The clinician talks to the patient, the agent does the assembly, the clinician reviews and signs.
The VA spent twelve months piloting this technology across multiple medical centers (https://www.soapnoteai.com/soap-note-guides-and-example/va-ai-scribe-2026/). The pilot recovered about thirty minutes per provider per day. The agency looked at that result and decided to scale it across every VA facility in the country in 2026. That is the largest federal medical system in the United States moving from “we are testing this” to “this is our standard tooling,” in one budget cycle.
Read that decision twice. Federal scale clinical AI adoption, with a productivity number attached, ratified by the procurement and operations machinery of an agency that serves roughly nine million veterans.
Now ask whether your agency has a credible reason to still be navigating drop-downs and free-text fields from a laptop in the parking lot.
What Thirty Minutes A Day Actually Looks Like In An EMS Schedule
Thirty minutes a day sounds modest until you map it onto our shift structure.
Take a high-volume ALS unit running eight to ten transports in a twenty-four hour period. Documentation on a complex run can eat fifteen minutes of chart time in the back, in the parking lot, or at the end of the shift. Multiply that by every patient contact. Add the calls that didn’t result in transport but still required a refusal or treat and release narrative. Add the supervisory chart reviews, the QA flags, the late-into-the-night completions that creep into the next shift.
In clinic, thirty minutes is a productivity gain. In our shift, thirty minutes is the meal break the medic often does not get to take. It is the recovery window between a code and the next chest pain. It is the breath before the next call. Every minute in EMS counts toward one of three things: a lifesaving response, rest for the crew, or recovery after a hard run. The math is not abstract.
It is the difference between a medic getting off shift on time and a medic finishing paperwork while their partner is already in the bay for the next call. It is the difference between accurate, in-the-moment narrative documentation and a chart written four hours later from memory, on a patient the medic has now seen three more of.
The VA bought back thirty minutes a day, per provider, in a setting where the chart is written in front of a workstation, with documentation time blocked into the schedule, in a quiet exam room.
We don’t document in a quiet exam room. We document in the back of an ambulance, in a hospital parking lot at one in the morning, on a phone or laptop balanced on the squad bench, trying to remember which arm we put the IV in.
And thirty minutes is the floor, not the ceiling. As ambient capture matures into full narrative, templated fields, and protocol cross-checks built for EMS, the recovered time scales to two or three hours per medic per shift. That stops being a productivity number. That is measurable relief, across a fleet and across a system. Less burnout. Faster post-call recovery. More crews ready when the next call drops.
The recovered time, on our side, isn’t thirty minutes. It is the chart finished before the next call drops.
The Habit That Keeps The Gap Open
Here is something I don’t hear people say out loud about field documentation modernization. The Fire & EMS leaders most ready for this technology are also still doing it the old way.
I write articles about voice-native ePCR workflow. When I worked a medic last year, I still did charting from a iPad in the parking lot. The narrative section, the part voice would help the most, is where I take the longest, because I’m translating a fast-moving call into structured story under fluorescent lights at the back of a hospital.
That gap, between knowing the technology is ready and still typing, is not a technology gap. It is a habit. Twenty-four years of routing “I need to document this call” straight to a keyboard. The medics in your agency will face the same friction the day this lands in your ePCR. The agencies that plan for that adoption curve get the productivity win. The ones who treat the technology as the deliverable will ship a feature nobody uses.
My first article on voice-native EMS documentation (https://www.linkedin.com/pulse/why-fire-services-biggest-technology-leap-wont-come-from-robert-grand-k1xlc/) made the case that voice is the primary unlock for closing the documentation gap in our service. The Google I/O piece (https://www.linkedin.com/pulse/google-just-announced-future-ems-documentation-dont-know-robert-grand-dhtpc/) followed it with the agentic frame. Both pieces named the gap between what is shipping for general knowledge workers and what our medics are still doing in the parking lot.
The VA decision tightens that gap in one direction only. In clinical settings, the gap is closing at federal scale. In Fire & EMS, it stayed exactly where it was.
That’s not a research gap. It is not a capability gap. It is a willingness gap, and willingness gaps get harder to defend the longer they sit open.
What “Federal Cover” Actually Buys In Our Service
The political utility of the VA decision is the part the trade press is undersold.
When an agency leader walks into a budget meeting and proposes ambient scribe for the medic units, the conversation has historically gone two ways. Either the medical director asks for clinical evidence the agency does not have, or the manager asks for productivity data on a comparable deployment, and the agency can only point at small commercial pilots. Both of those defensible, got harder to give last week.
The clinical evidence question now has a federal answer. The productivity question now has a thirty-minute-per-provider-per-day answer, ratified by the VA’s procurement process and aimed at nine million patients. The agency no longer has to argue from a single department’s pilot. It argues from federal precedent.
That doesn’t mean the technology automatically fits our environment. It doesn’t. The back of an ambulance is not a clinic exam room. The audio environment is harder, the documentation requirements are different, the legal exposure is different, the operational tempo is different. There is real work in adapting the clinical ambient scribe pattern to field EMS, and it will take operators, not tourists, to do it right.
But the political cover question is now settled. Any fire department or EMS agency that wants to move on field ambient scribe in the next twelve months can do it without having to win the precedent argument first. The precedent is on the desk. The work is in adapting it.
The Next Defensible No
The clinical world just got federal cover for ambient scribe. Fire & EMS did not.
That gap is not a research problem. It is not a capability problem. It is a leadership problem, and leadership problems only get harder to explain the longer the precedent on the other side keeps growing.
The medic in your agency is still charting in the parking lot. The VA clinician at the closest VA hospital is finishing notes thirty minutes earlier than they did last quarter. The next budget cycle is going to ask why we didn’t move.
Robert Grand is a Battalion Chief at Eugene Springfield Fire with 24 years of service. He writes Frontline Intelligence, a newsletter on operational doctrine, technology, and leadership in Fire & EMS.
If this landed, share it with someone in Fire & EMS who needs to hear it.
Reference: VA AI Scribe 2026: Nationwide Expansion, SOAP Note AI (https://www.soapnoteai.com/soap-note-guides-and-example/va-ai-scribe-2026/)
Subscribe
From the floor, not the vendor booth. Two times a week.