Complete "Authority to operate" (ATO) for Blue Button API

[indexing]

Over and above the technical work to make Medicare cardholder eligibility available in the Benefits application, we need to complete the contracting process with the Center for Medicare Services (CMS) which grants us authority to operate and use the Blue Button API in production.

This issue will track and capture official approval so all teams know when contracting is complete and the functionality is available to agencies using the Benefits app.

cc// @jarrettkrumrei @johnatstate anirban sen @thekaveman @srhhnry

Acceptance Criteria

• CDT has submitted application to CMS requesting production access to the Blue Button API.
• CDT/Cal-ITP teams have completed the design and dev work to do a demonstration of how Benefits will utilize the API (in the Benefits dev environment).
• CDT has scheduled a date to demo the Benefits implementation to CMS.
• CDT/Cal-ITP teams have completed product demo for CMS.
• CDT has completed the contracting process with CMS.
• CDT has notified the Cal-ITP Benefits team contracting is complete.
• Cal-ITP team has deployed the Medicare cardholder enrollment pathway to Benefits test environment.
• Cal-ITP team has released the Medicare cardholder enrollment pathway to production so any agency using Benefits can enable the pathway.

[indexing]

Ani at CDT submitted the form for production access to the Blue Button API today.
cc// @thekaveman @srhhnry @johnatstate

[indexing]

Ani at CDT is scheduling our demo for production access for early October. We need to have a functional implementation of our use of the API in the test environment prior to the demo.

[indexing]

Ani at CDT confirmed we have meeting on Oct. 8, 2024 with the Blue Button team to demo our use of the Blue Button API.