Article
What changed
HHS Secretary Robert F. Kennedy Jr. approved the reorganization on June 9, and it took effect that day, according to a notice published in the Federal Register on June 11. The new office provides enterprise leadership for CMS technology and digital product strategy across Medicare, Medicaid and the Children’s Health Insurance Program. It works alongside the agency’s chief information officer, who keeps responsibility for IT governance, cybersecurity, enterprise architecture and capital planning.
The office has four parts:
- Product Development Group. Runs internal and public-facing products, including claims and payment platforms, the National Provider Directory, Medicare.gov and Medicare Plan Finder.
- Standards & Interoperability Group. Sets CMS interoperability strategy and standards, builds FHIR-based APIs and data exchange platforms, and coordinates with ONC and standards bodies on regulations and administrative transaction standards.
- Open Source Program Group. Sets open source policy and encourages code reuse across CMS and HHS.
- Digital Service at CMS. Runs short discovery sprints and provides surge capacity for priority projects.
Why hospitals should pay attention
Several systems hospitals depend on every day now sit under one product owner. The office directs modernization of the National Plan and Provider Enumeration System, the Provider Enrollment, Chain and Ownership System and the National Provider Directory. It also oversees the replatforming of Medicare claims processing and payment systems.
That concentration has practical effects. Changes to enrollment workflows, directory data requirements or claims interfaces are likely to come from a single team with a product mindset, and possibly on a faster schedule than in the past. The interoperability group’s role in developing regulations means future data exchange rules may be designed alongside the platforms that enforce them.
What to do now
- Clean up provider data. Confirm that NPPES and PECOS records for every facility and employed clinician are current. Directory and enrollment modernization may surface old errors.
- Check API readiness. Review whether your EHR and revenue cycle vendors can support FHIR-based exchange with CMS platforms, and ask for their roadmaps.
- Watch for sprint reports. Digital Service at CMS publishes recommendations from its sprints, which can signal where requirements are heading.
- Coordinate internally. Bring the CIO, revenue cycle and compliance leaders together, since changes will touch all three.
Archive entry for Jun 17, 2026, added Nov. 11, 2026.