CMS launches dedicated health technology office as AI and interoperability pressure mounts on hospital IT teams

The Centers for Medicare and Medicaid Services moved in June 2026 to consolidate its technology functions into a single new unit, the Office of Health Technology and Products, signaling that federal oversight of clinical AI and data exchange is no longer a peripheral concern for hospital CIOs but a core operational reality. According to Healthcare Dive reporter Emily Olsen, the office will oversee the design and development of digital health tools, manage AI implementation across CMS programs, and promote healthcare data exchange.

Amy Gleason, a strategic advisor to CMS under the current administration and the architect of the agency's Health Tech Ecosystem initiative, will lead the office as deputy administrator and chief product officer, Healthcare Dive reported. The Health Tech Ecosystem is aimed at accelerating data sharing and broader digital health adoption across payers and providers.

What the office means for interoperability compliance

The office's formation is part of a deliberate CMS effort to centralize and streamline its technology functions, according to Healthcare Dive. That centralization has direct implications for how health systems document and demonstrate interoperability. National frameworks like the ONC's Trusted Exchange Framework and Common Agreement, known as TEFCA, already require health systems to build toward a unified data environment. A dedicated federal office focused specifically on data exchange enforcement and digital health tool governance adds weight to those requirements.

For procurement and IT operations teams, the practical effect is straightforward: vendors and platforms that cannot demonstrate structured interoperability and standards-compliant data outputs become a compliance liability. Terminology management, data mapping, and semantic interoperability tools move from nice-to-have to contractually relevant. Wolters Kluwer, for instance, positions its Health Language platform as a solution for maintaining enterprise healthcare data in a single environment for authoring, modeling, and mapping to industry standards, directly addressing the data quality layer that interoperability mandates require.

AI readiness demands a trusted data foundation

Clinical AI is the other axis of this shift. The new CMS office will manage AI implementation across the agency's scope, and that mandate is likely to sharpen scrutiny of how health systems validate the AI tools they deploy. For technology leaders, the question is less whether to adopt AI and more whether the underlying data infrastructure can support trustworthy AI outputs at the point of care.

Wolters Kluwer notes that its clinical technology and solutions are used by organizations spanning more than 180 countries and are trusted by over 90% of U.S. academic medical institutions, with more than two million clinicians relying on those tools. The company frames AI-enabled clinical decision support, through products such as UpToDate and UpToDate Expert AI, as delivering real-time, evidence-based insights aligned to how clinicians actually work. Separately, Wolters Kluwer's whitepaper on medication intelligence characterizes structured drug data layers as foundational to AI readiness in health tech development, a point that resonates with digital health vendors building on top of existing EHR and pharmacy infrastructure.

The convergence here is meaningful for IT and procurement teams. Federal policy is moving toward holding health systems accountable for the quality and interoperability of data flowing through AI systems, not just the AI models themselves. That means the vendor evaluation process now needs to account for data provenance, terminology standards compliance, and the ability to produce structured outputs that downstream analytics and reporting tools can consume.

Clinical workflows and the technology stack underneath them

Beyond compliance, the operational argument for investing in foundational health tech infrastructure is tied to care delivery efficiency. Wolters Kluwer's technology leader resources describe advanced analytics as critical for uncovering population-level trends, predicting risk, and optimizing resources in value-based care arrangements. Those capabilities depend on clean, standardized data that most health systems are still working to achieve.

Pharmacy operations are another pressure point. Wolters Kluwer's Simplifi+ Pharmacy Compliance platform is positioned to support safer, more connected pharmacy care within the interoperability context, a practical consideration for health systems managing medication data across care settings and payer requirements. The drug data layer, in particular, is becoming a point of evaluation for any health system building toward AI-assisted prescribing or medication management.

What this means for your team

• Audit your interoperability posture against TEFCA requirements now, before the new CMS office translates its mandate into formal reporting or audit expectations for providers and their vendor partners.
• Evaluate whether your clinical AI vendors can document the data lineage and standards compliance of their underlying content layers, not just the performance of the model itself.
• Prioritize terminology management and data quality infrastructure in near-term procurement cycles, as semantic interoperability is increasingly the foundation on which both AI readiness and regulatory compliance rest.
• Review pharmacy compliance and drug data platforms for structured output compatibility, particularly if your organization is building toward AI-assisted medication management or cross-setting care coordination.