Who’s Running Your Strategy: You or Your EHR Vendor?

As EHR platforms absorb more capabilities, health system leaders face a choice: accept what is coming, build something different, or let a vendor's roadmap set their competitive future.

Environment

In technology and operations discussions with health system leaders, one answer now comes up more than any other: "Our EHR already does that, or will soon." We heard it recently from a senior health system executive weighing how to close immediate gaps in fax management, primary care chart preparation, and prior authorization. His organization was deciding whether to buy a third-party solution or wait for its EHR vendor to deliver comparable capabilities, and that hesitation is common and reasonable.

The answer comes up often because EHR vendors now ship on a much faster cycle. Epic says its release cycle has moved from 18 months to quarterly. In February, Epic made its own ambient AI charting tool available, in a category where many health systems already held contracts with third-party scribes, and athenahealth announced AI waitlist scheduling, two-way patient texting, a voice front desk assistant, and plain-language self-scheduling for release during 2026. In August, Epic showcased an integrated ERP suite, real-time prior authorization checks, and Agent Factory, a no-code platform for building AI agents that starts with more than 120 prebuilt agents, with broader availability planned for 2027. EHR vendors are moving past recordkeeping into the automation and orchestration of clinical and administrative work. An Advisory Board analyst summarized the trend: "Epic is steadily absorbing functionality that historically lived with third-party vendors."

Impact

For provider organizations, this is mostly good news. Each capability the EHR handles well means one less interface, security review, and contract to manage, and for many needs the EHR-native option is the right choice. Faster release cycles also change how capability decisions get made. Organizations defer a build, pause a vendor search, or shelve a partnership while they wait for a credible EHR-native solution, often without weighing the cost of the delay.

Postponing a capability prolongs today's expense, and postponing one central to the organization's competitive position gives a competitor time to move first. Waiting has its own advantages, since early adopters absorb costs and implementation risks that later adopters avoid, and a lead built on technology alone tends to close as the technology spreads. The lead that lasts goes to the organization that builds a better operating model around the technology, whenever it adopts. The larger risk is that leaders confuse the capabilities their vendor intends to deliver with the capabilities their organization needs to compete. When that happens, the EHR roadmap ends up making a strategy decision that belongs to the leadership team.

Imperative

Leadership teams should decide which capabilities make their patient experience distinct, then choose how to own each one before the EHR roadmap chooses for them.

Insight

A.G. Lafley and Roger L. Martin's Playing to Win (Harvard Business Review Press, 2013) offers a useful discipline for those choices, and for every capability decision around them. Martin advises asking one question of each option before choosing: what would have to be true for it to be the right one? The options include waiting for the EHR, building on the EHR's platform, building your own, buying a third-party solution, and partnering. Four questions test them: whether the capability reaches the people and settings where it matters, whether it is table stakes, an operating advantage, or a source of differentiation, whether you can measure its contribution, and whether your organization can capture the value. Under the second question, a capability on its way to becoming standard EHR functionality has to earn a separate investment through better operating economics, faster value, or meaningful differentiation.

1. Does the capability reach the people and settings where it matters?

Count the practices, sites, and clinicians who need the capability to deliver on your organization's promises, then count the ones who would go without it under each option. For the EHR's default, many networks have an answer above zero: independent practices in a clinically integrated network running their own EHRs, affiliates on a hosted instance that may license fewer modules, and acquired groups still waiting for conversion. A third-party tool raises the same question, since it may integrate well with your primary EHR and poorly with everyone else's.

If a capability reaches only part of the network, patients get different levels of service under one brand, affiliated physicians watch employed practices receive new capabilities first, and payers and employers see uneven performance across the network. Universal deployment suits some capabilities and overreaches for others. Some matter most in particular specialties, populations, or markets, and some are best phased in. The test is whether the capability reaches everyone needed to deliver the clinical, operational, and market performance your organization promises.

If you accept a gap, make it deliberate: name who is affected, what it costs them, and when it will close. The left-out practices can serve as a control group only if you design the comparison on purpose, since practices on and off the platform differ in size, ownership, and patient mix as much as in the tool.

2. Is the capability table stakes, an operating advantage, or a source of differentiation?

Next, ask what job the capability does for your organization. Some capabilities are table stakes. Patients and payers expect them, and doing them well earns little extra credit. Online bill pay, appointment reminders, and refill requests often sit here. For these, the EHR's default is usually sufficient, provided it meets performance and cost expectations.

Other capabilities improve operating performance. Automating prior authorization, preparing charts before visits, and reducing administrative work can generate substantial economic value even when competitors have access to similar technology. Here, the test is whether the capability materially improves productivity, capacity, quality, or cost, and a third-party solution earns its expense when it produces better economics or delivers benefits substantially sooner than the EHR alternative. The executive I spoke with who was weighing fax management, chart preparation, and prior authorization was making this kind of decision.

Other capabilities are ingredients in why someone chooses your organization. If your promise is the fastest path from symptom to care, then triage, scheduling, referral coordination, and the first digital touch are the patient experience. When those touchpoints run on the same EHR tools as the system across town, with the same screens, messages, and scheduling logic, patients meet the same experience at both front doors. Anything you can switch on, your competitor can switch on too, whether it comes from the EHR or a popular third-party vendor, so a shared tool gives you the experience your competitor offers or can switch on next.

That leaves two paths for a differentiating capability. The first is to own it: build it, buy or partner for something your competitors lack, or build and configure your own design on the EHR's platform. The second is to accept parity on that capability, win on something else, such as access, clinical outcomes, physician relationships, price, or the way your teams run the work, and tell the market clearly what that difference is. Staffing, clinical workflows, and service design can create real differences around shared technology when the organization builds them deliberately and patients can feel them. Organizations get into trouble when they accept the EHR's tool, assume their experience is still distinct, and market a difference patients never notice.

A market leader can often take the second path, because its advantage rests on footprint, reputation, and referral patterns built over decades, and the market already knows what it stands for. A challenger trying to take share needs a reason for a patient, physician, or employer to switch, so it has to either own the experience or build and name a difference the leader cannot copy by turning on the same release.

Restaurants show both paths. Starbucks invested in its own app and loyalty program, because convenience, speed, and habit are core to what it sells. A neighborhood restaurant can take online orders through the same point-of-sale platform as the place across the street, win on the food and the service, and make sure the neighborhood knows it. As AI capabilities standardize within EHR platforms, more health systems will find themselves in the neighborhood restaurant's position on more of their touchpoints, and the ones that win will know what sets them apart and say it plainly.

3. Can you measure what you need to prove?

Then ask whether each option captures and reports the metrics your value proposition depends on. Software vendors, EHR and third-party alike, tend to report what their software does: adoption, message volume, and time saved per task. Those are useful operational measures, and they leave the economic and competitive case unproven. A health system CFO wants to know whether administrative costs fall, whether clinical capacity rises, and whether the organization captures the financial benefit. A payer wants to know whether your network resolves more care needs at a lower cost. An employer wants to know whether its people are seen sooner with you than elsewhere.

The metrics behind a differentiation claim end up in case studies, contracts, and marketing, and they need to hold up when a payer's analyst reruns them. If an option does not capture the necessary data, a capable analytics team can often build the measurement around it, or the organization can choose an alternative that does.

Measurement should also cover the economics of waiting. Deferring an investment avoids licensing, implementation, and integration costs, and it can also prolong administrative expense, constrain clinical capacity, delay revenue, or leave patients with a worse experience. Compare these costs over a defined period, alongside the acquisition price, and put one question to the team: what is the measurable cost of operating as we do today while we wait for the capability we expect tomorrow?

4. Can your organization capture the value?

Even when the strategic case is compelling, execution capacity decides whether the investment succeeds. A health system can recognize an opportunity to differentiate and still lack the product management, clinical operations, technical, or change management capability to deliver it, which makes a strong case for an EHR-native solution even when another option offers more functionality. An organization with strong operational leadership can often match or beat a specialized solution by configuring and managing technology it already owns. The test is whether the organization can redesign the work, secure physician and staff adoption, establish accountability, and sustain the improvement after implementation.

Building on the EHR's platform

Agent Factory and platforms like it blur the line between accepting the EHR's default and building your own. For many organizations, building on the platform will be the best answer. It keeps the advantages of a common clinical technology environment while letting the organization encode its own policies, knowledge, and workflows.

It is also a build decision, with the obligations of one, and question 4 applies in full. Any customer that adopts Agent Factory gets the same prebuilt agents, so whatever makes your version different lives in what your team adds and how your organization puts it to work. Someone has to own it as a product, measure it, and keep improving it after launch.

Organizations with those capabilities can build meaningful operating and competitive advantages on a common platform. Epic plans to make automations proven with its early partners broadly available across its client community, so a workflow you co-develop with Epic may become every customer's default, and what lasts is the staffing, accountability, and improvement your organization builds around it. An agent built within your EHR instance reaches the practices on that instance, including hosted affiliates that license it, and affiliates on other EHRs still get a different experience. Each capability built on the platform also ties more of your operating model to one vendor's architecture, roadmap, and pricing. That can be a sensible trade when the leadership team makes it on purpose.

Reading the answers together

When the answers point toward the EHR's default, take it and move on. When they point away from it, the real decision is among building on the platform, building independently, buying, and partnering. When the answers are mixed, return to Martin's question and ask what would have to be true for each option. Waiting makes sense when the EHR's delivery timeline is credible, the functionality sufficient, the economics favorable, and the cost of delay acceptable. A third-party investment makes sense when its incremental value covers the added cost and the integration work. Building makes sense when the organization has the talent, operating discipline, and resources to sustain the capability. Every option needs clinical, operational, and financial benefits you can measure.

Any option outside the EHR adds a vendor, partner, or internal team to sustain, and a third-party vendor's category may be the next one the EHR enters, so negotiate data portability and an exit into the contract. Judge each option, the EHR's included, on what has shipped and been demonstrated, and attach a date, a cost, and a degree of confidence to everything else.

Questions for your leadership team

• How many practices, clinicians, and patients essential to your value proposition would be left out under each option?
• Which capabilities are necessary to operate, which materially improve operating economics, and which influence why patients, physicians, payers, or employers choose your organization? Where those run on shared tools, what difference will you deliver, and how will the market know it?
• What performance improvement would justify acting now, and can you measure it?
• Does your organization have the leadership and operating capacity to capture the value, whoever supplies the technology?

Next step

Pick one capability from your EHR's release list or your purchase pipeline and run it through these questions with your strategy, IT, clinical operations, finance, and contracting leads in the same room. Write down what would have to be true for each option, then test the assumptions that matter most before anyone argues for a particular vendor. How you organize clinical capacity, redesign patient access, coordinate care across employed and independent physicians, and build a more sustainable operating model are choices for your leadership team, whichever vendor supplies the tools, and each one deserves a decision made on purpose.