Common use of CMS Hub Description Clause in Contracts

CMS Hub Description. All communication with the Hub is facilitated via Web services over the Internet. The Hub conveys information, using Transport Layer Security (TLS), version 1.2 for data encryption, server authentication, and message integrity. It uses Public Key Infrastructure (PKI) to authenticate connections. To protect the confidentiality of data transmitted from one system to another system, messages are encrypted, using the Hypertext Transfer Protocol Secure (HTTPS) protocol. All Application Programming Interface (API) transactions provided by an EDE Entity will go through the Hub for confirmation that the requesting EDE Entity is authorized by CMS. Upon confirmation, the API request will be passed to the Federally-facilitated Marketplace (FFM), at which point the FFM will validate the API request. The groups of services depicted in Figure 1 enable the FFM to provide internal and external stakeholders with the following capabilities: 7 Located at: xxxxx://xxx.xxx.xxx/about/agencies/asa/ocio/cybersecurity/index.html. 8 Located at: xxxx://xxx.xxx.xxx/Research-Statistics-Data-and-Systems/CMS-Information- Technology/InformationSecurity/.  Marketplace Consumer Record (MCR) APIs: Enable the Marketplace to provide customer-related data and search capabilities.  Standalone Eligibility Service (SES) APIs: Enable the Marketplace to determine the customer’s eligibility for Qualified Health Plans (QHP) and /or Qualified Dental Plans (QDP) and associated subsidies.  Issuer and Enrollment Services (IES) APIs: Enable the Marketplace to provide data to redirect consumers to the issuer payment portal.  Document Storage and Retrieval Service (DSRS) APIs: Enable the Marketplace to provide document upload and retrieval of Marketplace-generated notices.  Eligibility and Enrollment (EE) APIs: Enable the Marketplace to provide enrollment generation capabilities. Figure 1 is a high-level topological diagram illustrating the interconnectivity between the Hub and EDE entity systems. Figure 1: EDE Data Flow Diagram

CMS Hub Description. ‌ All communication with the Hub is facilitated via Web services over the Internet. The Hub conveys information, using Transport Layer Security (TLS), version 1.2 for data encryption, server authentication, and message integrity. It uses Public Key Infrastructure (PKI) to authenticate connections. To protect the confidentiality of data transmitted from one system to another system, messages are encrypted, using the Hypertext Transfer Protocol Secure (HTTPS) protocol. All Application Programming Interface (API) transactions provided by an EDE Entity will go through the Hub for confirmation that the requesting EDE Entity is authorized by CMS. Upon confirmation, the API request will be passed to the Federally-facilitated Marketplace Exchange (FFMFFE), at which point the FFM FFE will validate the API request. The groups of services depicted in Figure 1 enable the FFM FFE to provide internal and external stakeholders with the following capabilities: 7 Located at: xxxxx://xxx.xxx.xxx/about/agencies/asa/ocio/cybersecurity/index.html. 8 Located at: xxxx://xxx.xxx.xxx/Research-Statistics-Data-and-Systems/CMS-Information- Technology/InformationSecurity/.  • Marketplace Consumer Record (MCR) APIs: Enable the Marketplace Exchange to provide customer-related data and search capabilities.  • Standalone Eligibility Service (SES) APIs: Enable the Marketplace Exchange to determine the customer’s eligibility for Qualified Health Plans (QHP) and /or Qualified Dental Plans (QDP) and associated subsidies.  • Issuer and Enrollment Services (IES) APIs: Enable the Marketplace Exchange to provide data to redirect consumers to the issuer payment portal.  • Document Storage and Retrieval Service (DSRS) APIs: Enable the Marketplace Exchange to provide document upload and retrieval of MarketplaceExchange-generated notices.  • Eligibility and Enrollment (EE) APIs: Enable the Marketplace Exchange to provide enrollment generation capabilities. Figure 1 is a high-level topological diagram illustrating the interconnectivity between the Hub and EDE entity systems. Figure 1: EDE Data Flow Diagram

CMS Hub Description. All communication with the Hub is facilitated via Web services over the Internet. The Hub conveys information, using Transport Layer Security (TLS), version 1.2 for data encryption, server authentication, and message integrity. It uses Public Key Infrastructure (PKI) to authenticate connections. To protect the confidentiality of data transmitted from one system to another system, messages are encrypted, using the Hypertext Transfer Protocol Secure (HTTPS) protocol. All Application Programming Interface (API) transactions provided by an EDE Entity will go through the Hub for confirmation that the requesting EDE Entity is authorized by CMS. Upon confirmation, the API request will be passed to the Federally-facilitated Marketplace (FFM), at which point the FFM will validate the API request. The groups of services depicted in Figure 1 enable the FFM to provide internal and external stakeholders with the following capabilities: 7 Located at: xxxxx://xxx.xxx.xxx/about/agencies/asa/ocio/cybersecurity/index.html. 8 Located at: xxxx://xxx.xxx.xxx/Research-Statistics-Data-and-Systems/CMS-Information- Technology/InformationSecurity/.  • Marketplace Consumer Record (MCR) APIs: Enable the Marketplace to provide customer-related data and search capabilities.  • Standalone Eligibility Service (SES) APIs: Enable the Marketplace to determine the customer’s eligibility for Qualified Health Plans (QHP) and /or Qualified Dental Plans (QDP) and associated subsidies.  • Issuer and Enrollment Services (IES) APIs: Enable the Marketplace to provide data to redirect consumers to the issuer payment portal.  • Document Storage and Retrieval Service (DSRS) APIs: Enable the Marketplace to provide document upload and retrieval of Marketplace-generated notices.  • Eligibility and Enrollment (EE) APIs: Enable the Marketplace to provide enrollment generation capabilities. Figure 1 is a high-level topological diagram illustrating the interconnectivity between the Hub and EDE entity systems. Figure 1: EDE Data Flow Diagram