CMS centralizes AI and interoperability under a new Office of Health Technology and Products

The Centers for Medicare and Medicaid Services has stood up a dedicated health technology unit that will direct AI implementation, interoperability, and digital product strategy across Medicare, Medicaid, and the Children's Health Insurance Program. The Office of Health Technology and Products (OHTP) was formally established through a Federal Register notice dated June 11, 2026, and carries more than 90 listed responsibilities spread across eight divisions, according to Fierce Healthcare's reporting on the filing.

Amy Gleason will lead the office as deputy administrator and chief product officer. A strategic advisor to CMS under the current administration, Gleason already spearheads the agency's Health Tech Ecosystem initiative, which is designed to accelerate data sharing and digital health adoption across federal programs, Healthcare Dive reported.

What the new office actually governs

The scope of the OHTP goes well beyond a typical technology steering committee. According to the Federal Register notice cited by Fierce Healthcare, the office will own enterprise AI strategy, interoperability policy, development of digital products including Medicare.gov, provider directories, and claims system modernization. It will work in close coordination with the CMS Chief Information Officer and is expected to set direction for systems that touch nearly every payer, provider, and vendor that transacts with the federal government.

For health system IT and revenue cycle leaders, the claims modernization mandate is the most operationally immediate item on that list. Modern Healthcare has tracked how hospitals are already under pressure from documentation complexity and staffing shortages in revenue cycle management, making changes to underlying CMS claims infrastructure consequential for anyone relying on clearinghouse or billing integrations.

Jodi Daniel, a former director of ONC's office of policy, described the scope as a meaningful shift, noting the volume of delegated responsibilities signals a significant change in expectations, not a routine administrative reorganization, according to Fierce Healthcare.

ONC's role shrinks as CMS expands

The OHTP's creation did not happen in a vacuum. In March 2026, HHS reversed a Biden-era reorganization and returned the Office of the National Coordinator for Health Information Technology to its original name and a narrower mandate, concentrating on health IT standards, certification, and policy, according to Fierce Healthcare. Three department-wide technology leadership roles, the chief technology officer, chief artificial intelligence officer, and chief data officer, were moved back under the HHS CIO rather than operating as standalone HHS-wide functions.

The net effect is a division of labor: ONC sets standards and policy, while CMS runs the operational and product machinery. For vendors and health systems that have historically calibrated their interoperability road maps around ONC guidance, that means CMS is now the entity to watch for implementation timelines, certification requirements tied to federal programs, and data-exchange enforcement.

A vendor market flush with capital meets a new regulatory counterpart

The federal restructuring lands in a digital health market showing strong investment activity. Digital health venture funding reached $7.4 billion in the first half of 2026, driven primarily by mega-deals of $100 million or more, according to Modern Healthcare's coverage of Rock Health data. That capital is flowing into AI, telehealth, and data platforms, precisely the categories the OHTP is now charged with overseeing at the federal level.

For procurement directors evaluating AI or interoperability vendors, the OHTP introduces a new layer of federal governance to factor into contract terms and compliance planning. Vendors pitching AI-assisted revenue cycle tools, for example, will increasingly need to demonstrate alignment with CMS's AI strategy, not just ONC certification status. The office's mandate over Medicare.gov and provider directories also suggests that API integrations touching beneficiary-facing data will face more centralized review.

What this means for your team

• Map your current vendor integrations against the OHTP's stated domains, AI, interoperability, claims systems, provider directories, and Medicare.gov, and flag any that could be subject to new federal product or data-exchange requirements.
• Revisit interoperability road maps that were anchored to ONC guidance; with CMS now leading operational implementation, timelines and certification expectations for Medicare and Medicaid data exchange may shift.
• Include OHTP compliance posture as a vendor evaluation criterion in upcoming RFPs for revenue cycle, clinical AI, and data-exchange platforms.
• Monitor the Health Tech Ecosystem initiative for formal rulemaking; the OHTP's broad mandate suggests regulatory activity is ahead, and early comment opportunities matter for organizations with large claims volumes.