Mercy Health AI Strategy & Governance | Leading with Ethics

Navigating the AI Frontier in Healthcare: A strategic & Governance-First Approach

Artificial intelligence is rapidly transforming ⁣healthcare,promising unprecedented gains in efficiency,accuracy,and patient experience. But realizing these benefits requires more than just adopting the latest tools. It demands a strategic, governance-focused ⁣approach – one that prioritizes understanding why you’re implementing AI, not ⁤just what AI you’re implementing. This article, drawing on insights from⁢ MercyS AI leader, will guide ⁢you through ‍building a responsible and impactful AI strategy for your health system.

The Foundation: Strategy Before Solutions

Too often, organizations fall into the trap of chasing shiny new AI objects. before evaluating any vendor or launching an internal project,anchor your⁢ efforts to your enterprise’s Objectives and Key Results (OKRs). Let your strategic goals dictate the scope of your AI initiatives, not the other ‍way around.

This means clearly defining the problems you’re trying to solve. ⁢ Don’t ask ‍for an AI solution; ask how AI can help you achieve specific, measurable improvements ⁣in financial performance, operational efficiency, or patient/provider experience.

Vendor Evaluation: Beyond the Marketing Hype

When evaluating AI vendors, remember ⁣that a “powered by AI” label doesn’t guarantee responsible or effective implementation. you are ultimately accountable for how these tools are used within your association.

Here’s what ‍you need to do:

* Pressure-test data specifications. Ensure vendor data requirements align with your real-world workflows and‍ existing documentation patterns.don’t accept assumptions – validate everything.
* Understand the “how.” Don’t just accept claims ‍of accuracy. Demand transparency into how the AI reaches its recommendations and identify its inherent limitations.
* Validate governance, even when asserted needless. Even⁤ if a vendor claims their product isn’t a regulated device, your health system must still validate its governance posture. ⁣ Don’t outsource this obligation.
* Demand notification‍ of AI ⁤additions. Include a contractual clause requiring vendors to notify ⁢you whenever they ‍add⁢ AI capabilities to‍ products you’re already using.

Building for Scale: Pilots as Platforms, Not⁣ Experiments

Internal AI initiatives should be architected for scalability from the outset. Think of “pilots” not as isolated experiments, but as platform builds utilizing⁤ reusable microservices⁢ and agents. This prevents “throwaway” code and accelerates deployment across service lines ⁣once value is proven.

Vendor pilots also require⁣ careful planning. Budget realistically – the IT lift required for even a limited trial can be substantial, especially within a single Electronic Medical Record (EMR) environment. Clearly defined milestones ‍and resourcing are crucial to avoid open-ended projects.

Measuring Success: Beyond the Bottom Line

Defining value metrics upfront is essential, but be prepared to adapt. Some benefits, like reduced administrative burden, may be qualitative. Others, ⁣such as denial prevention⁣ or faster prior authorizations, are easily quantifiable.

Consider‍ these points:

* Focus on prevention. Frequently enough, the most impactful solution isn’t optimizing a downstream fix, but preventing the problem upstream.
* Embrace a holistic view. Collaborate closely between informatics, operations, and engineering teams to identify and address root causes.
* be flexible. Reality often diverges from initial plans. Be prepared to adjust your metrics and approach as you learn.

Essential Governance & Operational Practices

To ensure responsible AI ‍implementation, consider these key practices:

* Separate, but parallel, governance & change control. Establish a dedicated AI governance process, but run it in⁤ parallel‍ with your existing IT change control procedures.
* Human-in-the-loop⁣ for clinical LLMs. Always maintain human oversight for clinical Large Language Model (LLM) ⁢applications. Educate end-users on both the capabilities and limitations of these tools.
* Continuous ‍feedback & ⁣iteration. Involve informaticists and operational ⁢staff continuously to identify edge cases and exceptions. Their insights are invaluable for refining AI models and workflows.
* Prioritize ⁢humility. recognize that⁢ AI⁣ is a powerful tool, but it’s not a panacea. be humble about what it⁣ can and cannot do.

Key Takeaways – Actionable Steps ⁢for Your⁢ Organization:

* Anchor AI investments to enterprise OKRs.
* ⁢Pressure-test vendor data specs against real workflows.
* Separate AI⁢ governance from IT change control,but run processes in

Leave a Comment