The Microsoft Healthcare AI Transformation Navigator

Cowork library cards come from the Microsoft Copilot Cowork Healthcare Use-Case Library. Business Apps catalog cards come from the Microsoft Business Applications Pre-Built Agents and Capabilities report; they cover first-party Dynamics 365, Power Platform and Copilot Studio capabilities mapped to healthcare lines of business, and preview features may change. Dragon Copilot cards are drawn from Microsoft Learn documentation. Copilot Studio agent use cases and named agents come from the AI Apps and Agents for Healthcare Providers and Payers Executive Guide. Every agent use case in the Executive Guide is listed under Copilot Studio; each card’s footer shows the guide’s likely build, and many are Power App builds that a Copilot Studio agent can front. Impact tags use the six value levers from the Executive Guide, which line up with HAVEN's value lines. Named agents carry the guide's own tags; other tags are inferred from the use case text. Lateetud cards come from a partner solution shelf at field.lateetud.com; they are vendor-described, not Microsoft products, and should be validated before customer use. Clinical and nursing cards also draw on a nurse Build-A-Thon customer story, the Nursing Operations Assist multi-agent team, and a nursing capacity executive brief. Cards marked "Navigator addition" were drafted for the PMO line of business from the PMO Reimagined session and the Executive Guide, and should be validated before customer use. Supply chain cards marked “Supply chain webinar” were drafted from the October 1, 2026 Supply Chain Modernization session and its demo; they are illustrative and should be validated before customer use. Cards marked “Cowork + Copilot Studio provider portfolio” were drafted from an October 8, 2026 portfolio report for U.S. healthcare providers; the report’s statistics are not reproduced here, and the cards should be validated before customer use. Engineering team cards (Copilot Studio IDs starting EN-, and Cowork cards marked “engineering team scenario”) are scenarios built on Microsoft Learn documentation for the Azure DevOps MCP Server and Copilot Studio; they are illustrative, not product commitments, and should be validated before customer use. Pattern 5 cards describe Microsoft developer tools, drawn from Microsoft Learn documentation and Microsoft developer-tool positioning; the custom solution scenarios (IDs starting PC-) are illustrative designs, not product commitments, and should be validated before customer use. Cards marked “Copilot Chat, Cowork and Autopilot in Healthcare deck” were adapted from an October 2026 deck that pairs Copilot Chat, Copilot Cowork and Microsoft Autopilot across care-facing and corporate services functions; they are illustrative scenarios, have been adapted to U.S. providers, and should be validated before customer use. Microsoft Autopilot cards sit in Pattern 2 because Autopilot is an always-on agent that works on a person’s behalf. Marketing cards marked “Navigator addition” were drafted from the marketing line of an October 14, 2026 portfolio report for U.S. healthcare provider enterprises, the Cowork library marketing cases, the Executive Guide marketing agents, and the Business Applications report, including the Dynamics 365 CRM skills for Copilot Cowork announced October 8, 2026. They apply the Copilot Chat, Cowork and Autopilot pattern to marketing, are illustrative, and should be validated before customer use. Marketing use cases should use consented, approved data and avoid health-data targeting unless it is lawful and governed. Illustrative overviews are conversation starters, not Microsoft product commitments.