# A Business Case for Interoperability: CMS Interoperability and Patient Access Final Rule ## Key Facts - CMS’s **Interoperability and Patient Access Final Rule** is designed to **connect healthcare systems** and give members **greater control over their data**. (Scraped page content, main body) - The rule includes **required APIs** that enable members to **access health information**. (Scraped page content, main body) - Required APIs also help providers **locate network resources** and **streamline prior authorization**. (Scraped page content, main body) - The rule supports **health plans exchanging data when members switch coverage**, supporting continuity of information. (Scraped page content, main body) - Interoperability can support **better care**, **faster gap identification**, and **improved member experiences**, but implementation may be challenging for plans **without in-house technology teams**. (Scraped page content, main body) - The post features **guest Brian Edwardson**, and notes that specialized partners can help with **secure authentication**, **protecting sensitive information**, **compliant data exchange**, and building systems that turn interoperability into **business and care opportunities**. (Scraped page content, “Our Guest: Brian Edwardson” and main body) ## Summary ### What the CMS Interoperability and Patient Access Final Rule is meant to do CMS’s Interoperability and Patient Access Final Rule focuses on connecting healthcare systems so members can have greater control over their health data. A central mechanism described is the use of required application programming interfaces (APIs), which are intended to make health information more accessible and usable across stakeholders. ### How required APIs support members, providers, and health plans The post explains that required APIs enable members to access health information, while also helping providers locate network resources and streamline prior authorization. For health plans, the rule supports data exchange when members switch coverage—positioning interoperability as a way to improve continuity, support better care, identify gaps faster, and improve member experiences. ### Implementation challenges and the role of specialized partners The post notes that implementation can be difficult, particularly for plans without in-house technology teams. It adds that specialized partners can help by building secure authentication, protecting sensitive information, supporting compliant data exchange, and creating systems that translate interoperability requirements into meaningful business and care opportunities.

About this content