Connect with us

Thought Leaders

The Strategic Side of AI: Making Technology Work for Clinicians and Patients

mm

Five years ago, real-time clinical decision support and documentation that writes itself would have sounded like science fiction. Today, these capabilities are shipping in production software. The gap between what’s possible and what’s practical has dissolved, and healthcare leaders who are still debating whether to adopt artificial intelligence (AI) are already behind. The question now is how fast organizations can implement this technology responsibly.

For health systems seeking to move beyond experimentation, from large acute care networks to specialty organizations managing unique workflows in wound care, rehabilitation, and occupational health, the path forward demands strategic clarity about where AI creates genuine value, deliberate planning for workflow integration, and honest measurement of whether it’s actually helping. The distinction between AI theater and AI substance will define which organizations lead and which scramble to catch up.

Choosing the Right Use Cases

Not all AI initiatives deliver equal value, and the organizations that scale successfully share a pattern. They start with a workflow pain point that clinicians actually feel, not a technology capability that seems impressive in a demo. Documentation burden is the most measurable example. Research shows that clinicians spend nearly half their workday on EHR and desk work, roughly two hours of documentation for every hour of direct patient care. In rehabilitation therapy, 70% of therapists report documentation speed as the biggest factor in burnout. AI that reduces this burden gives clinicians back time with patients and helps retain an exhausted workforce.

But leaders need to be discerning about what “AI-assisted documentation” actually means. Most ambient documentation vendors today generate narrative clinical notes: a SOAP summary pasted into the notes section of the EHR. That’s a useful starting point, but it’s not where the real value lies. The next frontier is AI that extracts structured data from clinical conversations, such as range of motion, strength scores, and exercise details, then populates discrete fields directly. The difference between AI that writes a paragraph and AI that populates forty-seven structured clinical fields is the difference between convenience and a transformation.

There’s an affordability lens too often ignored. Post-acute care settings and private practices operate on razor-thin margins. Any AI investment has to show return on investment in months, not years. AI can’t just be for health systems with billion-dollar IT budgets. The math must work for a ten-provider skilled nursing facility or a rural outpatient clinic. Organizations that focus first on revenue cycle efficiency and documentation productivity build the foundation for expanding into more ambitious clinical applications.

Native AI vs. Bolted-On Solutions

One of the most consequential decisions is whether AI should be natively embedded within clinical systems or bolted on as point solutions. Point solutions create what I call “swivel-chair AI.” Meaning, clinicians are toggling between systems, copying outputs between screens, and managing separate logins. Every integration seam is a friction point. When AI lives outside the clinical workflow, insights arrive out of context, feedback loops break, and cognitive load on clinicians actually increases. Bolted-on AI is a feature. Native AI is a platform capability.

Native AI has context that external partners simply cannot replicate. When intelligence is embedded within the EHR, it knows the patient’s history, the current workflow state, and the clinician’s documentation preferences, all without an API call or data handoff. There’s also a governance advantage; you control the full audit trail, model updates, and data residency. And native integration closes the feedback loop that makes AI better over time. AI suggests, the clinician acts, the outcome is captured, and the solution improves. The best AI disappears into the workflow, and that invisibility is only achievable when intelligence is woven into the system clinicians already live in.

Strategies for Successful Deployment

Even the best AI won’t succeed if the organization isn’t ready. Without aligned clinical leadership and redesigned workflows, initiatives will falter. Leaders need to insist on deployment prerequisites like executive sponsorship, clinical champions, and change management resources before signing contracts.

Not all AI initiatives deliver equal value, and the organizations that scale successfully share a common pattern. These systems should be auditable, controllable, and transparent. Can you articulate why the AI made a particular suggestion? Is there an immutable record of what it did and what the clinician decided? Can you turn it off, adjust thresholds, or exclude certain populations? If you can’t explain it, audit it, and control it, don’t deploy it.

Equally critical is that AI output in clinical settings should always be a draft, never a final record. Keeping humans in the loop is essential to ensuring safety and accuracy in any AI-generated output.

Leaders should also ask more strategic questions of their AI vendors. “What happens when you’re wrong?” Every AI makes mistakes; how does the vendor detect errors, notify customers, and remediate? “Who owns the model improvement cycle?” Is your data improving their model, and do you benefit from those improvements? “Show me a failure.” Any vendor claiming 100% success is either lying or hasn’t deployed at scale.

The Specialty Care Advantage

In specialty care, including wound care, rehabilitation therapy, and occupational health, these principles take on even greater importance. Specialty workflows are more structured than general acute care, so AI trained on specialty data achieves higher accuracy than one-size-fits-all solutions.

Consider ambient documentation in rehabilitation therapy. When AI can listen to a session and accurately populate range-of-motion measurements, manual muscle testing scores, and exercise details into discrete clinical fields, rather than generate a narrative summary, it fundamentally changes the value equation. When that ambient system is tightly coupled to the EHR, it synthesizes the patient’s documentation history alongside the current transcript, producing contextually aware documentation that understands the treatment arc rather than treating each encounter in isolation. The specialty EHR vendor that owns both the clinical workflow and the AI intelligence layer can close the loop between what AI suggests and what actually happens to the patient in ways that bolted-on solutions cannot.

Looking Forward

The near future is already coming into focus. Agentic AI, systems that don’t just suggest but act, will handle significant portions of administrative workflows. Picture prior authorizations submitted automatically, referral packets compiled without human assembly, and prescription renewals processed with clinician oversight but not clinician labor. Two years from now, manual prior authorization will seem as archaic as faxing.

Success begins with selecting use cases that align with organizational goals and clinical realities, embedding AI natively into workflows, involving frontline clinicians in design and validation, and measuring outcomes with the same rigor applied to any clinical intervention. The technology is the easy part. The hard parts are organizational commitment, workflow redesign, and measurement discipline. But for health systems that approach AI deliberately, the reward is substantial. Safer care, fewer burned-out clinicians, and better patient outcomes. AI isn’t here to practice medicine. It’s here to help us practice medicine better, to eliminate what exhausts clinicians so they can excel at what energizes them: helping people heal.

For over 28+ years, Eric has developed software in a variety of industries, including healthcare. He has served as an Enterprise Architect for University Hospitals in Cleveland. As a Principal Architect, for the past decade before joining Net Health, he shepherded many large enterprises with their application modernization efforts.

In his current role, Eric serves as Net Health’s chief architect and also leads the software engineering organization that includes all of the product development teams for all of Net Health’s products.