As healthcare organizations move from piloting individual AI tools to deploying them broadly, a sponsored article from athenahealth argues that the key question is whether AI is merely connected to the EHR or built natively into the platform. Standalone tools can introduce new data boundaries, governance processes, and workflow interruptions, while AI-native capabilities work from the same data, permissions, and clinical context as the rest of the system.
The article highlights three considerations for healthcare leaders. First, AI is more useful when context follows the clinician—for example, by generating problem-oriented summaries before a visit and capturing notes during it without requiring a separate login. Second, AI creates more value when one workflow informs the next: more complete documentation can support accurate coding, which can then feed quality measurement and care-gap identification. Third, as adoption scales, architecture determines whether capabilities can share data and workflows across the organization, rather than being managed as separate experiences.
The piece cites athenahealth customer data showing a reduction of nearly six minutes per visit in chart preparation and documentation time, and same-day chart completion above 80%. These figures come from the vendor's own Q2 2026 data compared with Q2 2025, and the article notes that individual results may vary.
Because this is a single, vendor-sponsored perspective, the claims are not independently verified. Still, the central recommendation—evaluate the architecture behind AI capabilities, not just the feature list—offers a concrete framework for CMIOs and other leaders assessing EHR AI investments.