Priority Dispatch Brings Medical Transport Protocol Inside Epic

I spent years watching health systems hire their own dispatch expertise. They'd bring in someone with twenty years running an ambulance service. That person would build triage protocols. They'd train staff on when to send ALS versus BLS. They'd try to teach the entire EHR department which transport resources fit which clinical needs.

Then that person would leave. And the protocols would die with them.

That's when I realized something: medical transport triage shouldn't be custom. It should be infrastructure. We partnered with Priority Dispatch, the company that's been running dispatch protocols for decades, to build that infrastructure inside Epic.

MTP Suite Inside Epic

Today, we're launching Priority Dispatch MTP Suite (Medical Transport Protocols 45, 46, and 47) embedded in the Epic EHR through the VectorCare SoFaaS platform. These aren't recommendations. These are decision logic. When a hospital coordinator submits a transport request, the EHR doesn't just record it. The system knows what type of transport is clinically appropriate for this patient, in this condition, at this facility level.

Protocol 45 is up-care, moving a patient to higher acuity. Protocol 46 is scheduled routine transport. Protocol 47 is behavioral health transport. Each one has decision trees built on decades of actual dispatch experience. Not hunches. Not what one hospital thinks is best. What's worked across hundreds of thousands of transports.

The Over-Dispatch Problem

Here's why this matters: A small hospital has a patient post-op, stable, but needs ICU monitoring. The coordinator could call an ALS ambulance. That means two paramedics, advanced equipment, fifteen-minute response time, higher cost. Or she could request BLS transport: two EMTs, basic equipment, eight-minute response time, lower cost. Which one's right?

Protocol 45 answers it. Patient's vitals are stable. Patient doesn't have a surgical airway. Patient's facility can manage the current care level. BLS is appropriate. Send the BLS unit. That's not cutting corners. That's efficiency. That's also what keeps the ambulance system from overloading. Every ALS unit babysitting a stable post-op patient is not available for someone who actually needs paramedics.

The math is brutal. Over-dispatch one stable patient with ALS instead of BLS, and you've spent $1,500 on a transport that needed $400 of resources. Multiply that across a health system doing 5,000 inter-facility transports a year. That's $5.5 million in unnecessary costs. Before the protocols were in the EHR, most hospitals had no way to know they were doing it.

What I Saw in Ohio

I watched this happen at a regional hospital network in Ohio. They had excellent clinicians. They had a good dispatch coordinator. But she was making decisions one at a time, by intuition, in the middle of managing four other calls. The network was bleeding money on over-dispatch because there was no system. The instant we put the protocols in Epic, their ALS utilization dropped from 68% of inter-facility transports to 41%. That's not less care. It's the same care, delivered more efficiently. It saved them $2.1 million in year one.

Before and After Protocols

Before protocols in the EHR, here's what happened: A hospital coordinator gets a transfer request. She opens a three-ring binder. She reads through a flowchart on paper. She makes her best guess. She calls the ambulance service. She updates the chart manually. She does this forty times a day.

After protocols in the EHR: The coordinator submits the transfer request from the patient's Epic chart. The system runs the patient's vitals, acuity level, facility type, and clinical history through the decision logic. The recommendation appears instantly. ALS or BLS. The coordinator approves. The dispatch system knows immediately. No call needed. No guessing. No manual updates.

Domain Expertise Meets Infrastructure

There's something larger here. We partnered with Priority Dispatch because they own the domain expertise. We own the infrastructure layer. That partnership is the model. Health systems don't need to hire dispatch experts and hope they stay. They don't need to build custom protocols. They need access to best practices embedded in their actual workflow.

The marketplace is changing. Hospitals used to build everything themselves. Now they're asking: What should I buy versus what should I build? Transportation triage is a "buy" decision. It's been solved. Protocol 45, 46, 47, that's the answer. The infrastructure that makes it automatic is something we're building.

MTP Suite works because it sits at the intersection of clinical data and operational decision-making. Epic knows the patient. Priority Dispatch knows the protocol. VectorCare connects them. When those three layers are aligned, the entire system works differently.

The bigger picture is this: Health systems are built on layers of infrastructure. The EHR is the foundation. On top, you layer clinical protocols, operational workflows, and resource management. Transportation triage used to be someone's job. Now it's built into the system. That's infrastructure thinking.

We've deployed MTP Suite with nine health systems so far. Combined, they're running 12,000 transports a month through the protocol logic. Over-dispatch is down. Clinical appropriateness is up. The one thing that surprised us: Clinicians actually like having the decision logic visible. It removes the guesswork from a decision that used to feel arbitrary.

I built this because I watched good hospitals make expensive mistakes every single day. Not from bad care. From missing infrastructure.