Yuma Fire's proposed telehealth deal is free for the City. Patients are another story.

"At no cost to the City" is a lovely phrase to find in a staff report. It's just worth asking, every time, who it costs instead.

The phrase turns up in a proposal going to Yuma City Council on Wednesday. The Fire Department wants to sign a five-year agreement with MD Ally Technologies, a telehealth company, item MC 2026-197. Yuma would piggyback on a contract the City of Phoenix already put out to bid, RFP 22-071 and Contract 155988, with a few local changes.

The idea is simple and pretty sensible. Not every 911 call is a life-or-death emergency. Some callers need advice more than an ambulance. Under this kind of program, some of them could be connected to a clinician by phone or video instead, which keeps fire crews free for the calls that need them.

The three-page Yuma agreement answers the "who pays" question in one line. Compensation "shall be received from patients, or on behalf of patients, who receive telehealth services from MD Ally. MD Ally will not receive compensation from the City."

The agreement doesn't identify exactly who would pay on a patient's behalf. What it makes clear is that the City's cost and the patient's cost are two separate questions, and the agenda packet only answers the first one.

The Yuma agreement doesn't list a price for a consultation. It doesn't mention copays, what an uninsured caller would be charged, or how someone could dispute a bill.

What the Phoenix contract promises

Because Yuma would adopt Phoenix's terms, Phoenix's scope of work fills in some of how the service is supposed to work. A caller could be routed to telehealth by phone or video either straight from dispatch, instead of sending a unit, or at the scene, after firefighters or paramedics have assessed the patient and decided they meet the criteria. The contract calls for triage protocols, privacy protections, quality checks and follow-up care where it's appropriate.

It also requires services regardless of a caller's insurance status or ability to pay.

That's a real protection. Nobody gets turned away from a consult because they're uninsured. It is not, however, a promise that they won't get a bill afterward, and nothing in the documents makes that second promise.

The documents also describe requirements, not results. They don't show that Yuma has written its local protocols, trained its dispatchers, picked a start date, or estimated how many calls might go this route. Whatever Phoenix's experience has been, it isn't Yuma's.

The agreement would last five years, then renew a year at a time unless either side gives 90 days' written notice. If Phoenix's own contract with MD Ally ends, Yuma's would keep going under the same terms.

Before the first call

The Fire Department recommends approval, and I can see why. For calls that meet the medical triage criteria, a telehealth visit could be a better use of emergency resources and the patient's time.

But the person on the other end of this service just dialed 911, and a few things should be spelled out before the program starts. How will a dispatcher decide who's eligible? Can a caller say no and still get an ambulance? Will patients be told up front that the consult may be billed, and roughly what it costs? What happens with an uninsured patient's bill?

The agreement may well pass Wednesday. If it does, those answers are the part residents will actually feel.

Sources

• City of Yuma, MC 2026-197 legislation record and staff report: "at no cost to the City," Phoenix RFP 22-071, staff recommendation, $0 fiscal impact
• City of Yuma, Telehealth Services Agreement with MD Ally Technologies: Section 2 compensation; Section 3 term, renewal, 90-day notice, continuation
• City of Phoenix contract exhibit, scope of work and amendments: PDF pp. 55-57, sections 5.3 (access regardless of insurance or ability to pay), 5.6.1 (audio or video), 5.8.1-5.8.2 (dispatch and scene referrals), triage and quality requirements