Choose your vendors wisely

A decision you made years ago is about to matter in ways you did not expect

Most practice owners signed their EHR contract a long time ago. The circumstances that shaped that decision are long gone. The criteria that mattered at the time, the pricing, the specialty-specific templates, the billing integration, the recommendation from a colleague, were all reasonable. Nobody was thinking about whether the vendor would let data move in and out of the system freely a decade later, because the question had no practical consequence. The data sat inside the EHR and that was the end of it.

That world is over. A new layer of software is arriving in healthcare that can do administrative work no practice could realistically staff for. AI agents that answer the phone, process referrals, verify insurance, handle intake, and sync everything back into the record. The practices whose underlying vendors are open and interoperable will benefit from this wave. The practices whose vendors are closed will watch it happen to other practices. This is not hypothetical. It is the most consequential vendor decision a practice will make in the next five years, and most practice owners do not yet know they are making it.

We are writing this because we see the mechanics up close. When a new practice comes to Taxo, the first thing we do is look at their stack. Within an hour we can tell whether the deployment will be clean, or whether we will spend the first month fighting infrastructure that was never designed to let data out. The difference is not about the quality of the practice. It is almost entirely about the vendors the practice signed contracts with years earlier. And the practice owner usually had no idea, at the time, that those contracts were the decision.

What interoperability actually means

The word gets used loosely, so it is worth being precise. Interoperability in this context is the set of technical and contractual conditions that allow a third-party system, whether that is an AI administrative platform, a patient engagement tool, a billing automation, or whatever comes next, to read data from and write data to your EHR and your phone system without friction. It is not a marketing claim. It is a measurable property of the software you have bought.

On the EHR side, the serious signals are these. A modern REST API, documented and accessible, that a third party can integrate with in days rather than months. Bulk FHIR access, which is the regulatory standard that allows large-scale read access to clinical and administrative data. Real-time webhooks, so that when something changes inside the EHR a partner system can be notified immediately. Write-back capability, so that a partner system can create appointments, update records, and close loops without a human re-entering data. And, underneath all of this, pricing that does not penalize you for the act of accessing your own data. The last point matters more than practice owners expect. Some vendors technically provide API access but charge per-call fees, per-patient fees, or annual integration fees that make any serious third-party deployment economically unviable. That is a form of lock-in disguised as openness.

On the telephony side, the signals are similar in spirit. A phone system built on modern, programmable infrastructure, rather than legacy on-premise hardware that treats software integration as an afterthought. The ability to port numbers freely and to route calls through APIs. Support for SIP trunking, which is the industry-standard protocol that lets modern voice platforms plug into existing phone lines without replacing the hardware. Programmable voice platforms like Twilio, which are built for this kind of integration, are the cleanest path. Traditional copper-line or closed PBX systems are the opposite.

A practice that has chosen well on both fronts can have a platform like Taxo operational in a matter of days. A practice that has chosen poorly can wait weeks or months, or may discover that certain capabilities are simply not possible no matter how much the practice is willing to invest.

Why we are writing this

We are Taxo. We build AI administrative infrastructure for healthcare practices. The practice owner who picks an open EHR and a programmable phone system will benefit not only from Taxo but from every other serious administrative AI platform built in the next decade. The practice owner who picks a closed EHR and a legacy phone system will be locked out of that entire category of progress, and the lock-in will not announce itself until the practice tries to move.

The most painful conversations we have are with practice owners who love what we can do and who then discover that their EHR vendor charges a prohibitive fee for API access, or does not offer write-back, or does not support Bulk FHIR. We can still work with many of these practices, but the deployment is slower, the data flow is shallower, and the value the practice receives is a fraction of what it would have been if the underlying stack had been chosen differently. We would rather practice owners know this before the contract is signed than after.

Questions to ask an EHR vendor before you sign

The questions below are the ones we wish every practice owner asked before committing to an EHR. For each, we have written the ideal answer. If the answer you get is vague, evasive, or significantly worse than the ideal, that is information. A vendor who cannot answer these questions clearly in a sales call is a vendor whose technical posture is probably worse than the sales team realizes.

Do you provide a modern REST API with developer documentation, and is access included in the base contract?

What you want to hear. Yes. Our full REST API is documented publicly, access is included in the standard subscription, and there are no per-call fees or gated tiers for core endpoints.

Why it matters. Some vendors offer APIs as a premium add-on priced to deter use. This is lock-in. The API should be a standard entitlement, not an upsell.

Do you support Bulk FHIR data access, and if so, at what cost?

What you want to hear. Yes. We support the Bulk FHIR specification, and there is no separate access fee beyond the base subscription.

Why it matters. Bulk FHIR is the federal interoperability standard. A vendor that does not support it, or that charges five-figure annual fees for access, is signaling its posture on openness. Both are red flags.

Do you support write-back to the record from third-party systems? For which resources?

What you want to hear. Yes. Third-party systems can create and update appointments, patient demographics, insurance records, clinical notes where appropriate, and tasks, through the API, with appropriate permissions.

Why it matters. A system that can only be read from, not written to, cannot close the loop. Your AI administrative platform will be reduced to a fancy dashboard if it cannot actually update the record.

Do you provide real-time webhooks or event subscriptions when records change?

What you want to hear. Yes. Partner systems can subscribe to events such as appointment creation, patient updates, and new referrals, and receive near-real-time notifications.

Why it matters. Without webhooks, every integration has to poll the system, which is slow, expensive, and creates race conditions. Webhooks are how a modern stack actually works.

What is your policy on third-party integration fees? Do you charge partners to connect to your system?

What you want to hear. We do not charge third-party partners for standard API integrations. Practices may integrate with any certified partner at no additional platform fee.

Why it matters. Some vendors operate what amounts to a toll booth on integrations, charging both the practice and the partner. This is the single most effective form of soft lock-in in the industry, and it is invisible in the sales cycle unless you ask.

If we decide to leave, can we export the full patient record, including structured clinical and administrative data, in a standard format, at no additional cost?

What you want to hear. Yes. You own your data. We will export the full record in a standard interoperable format at any time, at no cost, on request.

Why it matters. The answer to this question reveals the vendor’s actual posture on ownership. Anything other than an unqualified yes is a warning.

Do you certify partner integrations, and which AI administrative platforms are currently integrated with your system?

What you want to hear. We maintain a partner program, we actively certify new integrations, and here is a list of current partners across the major categories.

Why it matters. A vendor with a healthy partner ecosystem is a vendor that treats interoperability as a feature rather than a threat. A vendor that cannot name any modern AI partners is a vendor that has chosen, implicitly or explicitly, not to participate in what comes next.

Questions to ask a phone system vendor before you sign

The phone system matters more than practice owners expect, because every AI administrative platform that touches voice has to plug into it. A modern, programmable telephony setup is the difference between a deployment that takes days and one that takes months.

Is your system cloud-based and programmable, or is it on-premise hardware?

What you want to hear. Cloud-based, programmable, and API-first. Our system is designed to integrate with modern voice platforms.

Why it matters. On-premise PBX hardware is the telephony equivalent of a closed EHR. It was acceptable in 2010. It is a liability in 2026.

Do you support SIP trunking and programmable call routing?

What you want to hear. Yes. We support SIP trunking and API-based call routing, and we work with programmable voice platforms including Twilio.

Why it matters. SIP trunking is the protocol that lets modern voice AI platforms sit alongside your existing phone infrastructure without replacing it. Without SIP support, the integration either cannot happen or requires ripping out hardware.

Can we port our existing numbers in and out freely, without fees or delays?

What you want to hear. Yes. Number portability is standard, there are no exit fees, and the process typically completes within a few business days.

Why it matters. Number lock-in is one of the quietest forms of vendor control in healthcare. A vendor that makes it difficult to take your own phone numbers elsewhere is a vendor you should not sign with.

Do you support call forwarding and dynamic routing to external voice platforms?

What you want to hear. Yes. Calls can be routed to external systems programmatically, and the routing logic can be controlled by a third-party platform through our API.

Why it matters. This is the specific technical capability that lets an AI voice agent answer your calls while keeping your existing infrastructure intact. Without it, the deployment requires replacing your phone system entirely.

What happens to recordings, logs, and metadata if we leave?

What you want to hear. You retain full access to all call recordings, logs, and metadata, and can export them in standard formats on request.

Why it matters. As with the EHR, the exit clause is the honest disclosure of the vendor’s posture. Read it carefully before you sign, not after.

One more question, for yourself

After you have asked the vendor all of the above, ask yourself one more. If I imagine my practice three years from now, with several AI administrative systems running in the background, handling calls, processing referrals, managing follow-up, and keeping the chart current, which of the vendors in front of me is the one my future practice will thank me for choosing. The answer is almost always the one whose salesperson could answer the hard questions without looking uncomfortable.

What we would tell a practice owner we cared about

If a practice owner we cared about asked us, privately, what to do, we would say this. Treat the EHR and phone system decisions as infrastructure choices, not as feature choices. Features come and go. Infrastructure is what determines what is possible for the next decade. Choose vendors whose technical and contractual posture makes your data free to move. Pay a little more, if you have to, for an open stack rather than a closed one. The premium you pay is insurance against being locked out of everything that is coming.

The next ten years of healthcare administration will be defined by AI platforms that can sit on top of an open stack and do work that no human team could sustainably do. The practices that benefit will be the ones whose underlying vendors made that possible. The practices that do not will spend the decade wondering why their competitors seem to be pulling ahead in ways they cannot quite explain. The vendor contract is the decision. It is worth treating it that way.