Enterprise health systems have been running AI in production for 18 months. Not in pilot programs. Not in vendor demos. In live operational environments — scheduling, clinical documentation, prior authorization, supply chain, and staffing.

The results are in. And they are significantly more complicated than the press releases suggest.

For independent practices, this matters now — not because you’re being asked to deploy enterprise AI, but because the vendors you already work with are. Your EHR, your clearinghouse, your billing software, your payers — all of them are integrating AI into the workflows that touch your practice daily. You don’t get to opt out. You do get to be prepared.

Here’s what enterprise IT has actually learned, and what it means at your scale.

78%
of health systems report AI projects exceeded initial implementation timelines
more staff training required than initially scoped in enterprise AI rollouts
41%
of enterprise AI tools retired or replaced within 24 months of deployment

What Enterprise IT Learned the Hard Way

AI adds workflow layers before it removes them.

The assumption going in was that AI would reduce administrative burden. For the first 12–18 months of most enterprise deployments, the opposite happened. Clinicians needed to review AI-generated documentation. Staff needed to validate AI-suggested prior auth codes. Billing teams needed to audit AI-flagged claims before submission. New oversight workflows were required to manage the AI workflows. The net effect in year one: more steps, not fewer. The promise is real — but the timeline to efficiency is longer than vendors represent, and the transition period is genuinely hard.

The integration gap is where the ROI disappears.

Enterprise health systems discovered that AI tools performing well in isolation often performed poorly inside existing EHR and practice management workflows. An AI prior auth tool might generate accurate recommendations — but if it doesn’t integrate cleanly with the EHR, staff end up copy-pasting between systems, which eliminates the time savings entirely. The integration work — APIs, data mapping, staff retraining, workflow redesign — cost enterprise IT teams two to three times the original vendor estimates. For independent practices, this is a critical due diligence question: before any AI tool, ask where it lives in your existing workflow, not just what it does.

Cognitive burden is the hidden cost nobody budgeted for.

The most significant finding from enterprise AI rollouts isn’t financial — it’s human. Clinical and administrative staff at health systems with active AI deployments reported significantly higher decision fatigue. AI tools present recommendations, flags, and alerts constantly. Each one requires a human judgment call: accept, override, investigate. When those calls number in the hundreds per day, the cumulative cognitive load becomes a staffing problem. Burnout rates in high-AI environments tracked 20–30% higher in the first year. Enterprise IT is now designing for “alert fatigue” as a first-order problem. Independent practices with 2–5 billing staff cannot absorb this. Vendor promises of automation must be weighed against what your team will actually be asked to do.

The enterprise lesson isn’t that AI doesn’t work. It’s that AI works best when the underlying workflow is already clean, the integration is seamless, and the staff have enough capacity to manage the transition period. Most independent practices are resource-constrained on all three dimensions before any AI tool enters the picture.

What This Means at Independent Practice Scale

Your EHR vendor is already integrating AI whether you activate it or not. Epic’s ambient documentation, Oracle Health’s clinical AI, athenahealth’s autonomous coding tools — these are moving from optional modules to default features in 2026–2027 contract cycles. The question isn’t whether AI is coming to your practice. It’s whether you’re ready to manage it as a project rather than react to it as a disruption.

Three things independent practices can do right now that enterprise IT wishes it had done earlier:

Document your current workflows before any AI touches them. Enterprise health systems that struggled most with AI implementations were the ones that had no baseline documentation of how work actually got done before the tools arrived. When the AI started making recommendations, they had no clear standard to compare against. A one-page workflow map for your top 5 billing and scheduling processes costs nothing and becomes invaluable during any technology change.

Ask vendors one question before any AI demo: “Show me where this lives in my current workflow, not in a clean demo environment.” The honest answer to that question will tell you more about actual implementation risk than any ROI projection.

Protect a decision window. Enterprise IT learned that the worst AI implementations happened when vendors moved fast and practices didn’t evaluate slowly. You have something large health systems don’t: the ability to say not yet. Use it deliberately. The practices that will deploy AI well in 2027 are the ones that are watching carefully right now — not the ones that signed contracts in Q3 2026.

Your Action Item This Month

  1. Pull your current EHR contract. Find the section on “product updates,” “new features,” or “AI tools.” Note what is coming and when.
  2. Identify the one workflow in your practice that takes the most time and produces the most errors. Write it down — step by step — as it works today. That is your AI readiness baseline.
  3. If any vendor has pitched you an AI tool in the last 90 days, send them one question: “How does this integrate with [your EHR]? Who manages that integration?” Their answer is your due diligence.

The enterprise wave is real. The enterprise experience shows the path is navigable — with the right preparation. That’s what this publication is for.

Enterprise knowledge. Independent practice scale.
— The PMRx Team
The PMRx Insider Pulse is published monthly. For Knowledge Session playbooks and implementation tools, visit the PMRx Library.