Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
7 of 8 tasks
indexing opened this issue Aug 7, 2024 · 5 comments
Open
7 of 8 tasks

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

indexing opened this issue Aug 7, 2024 · 5 comments
Assignees
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) product Issue captures work for the product team

Comments

@indexing
Copy link
Member

indexing commented Aug 7, 2024

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 indexing added the deliverable Work that ends with a non-code deliverable (e.g. Google doc) label Aug 7, 2024
@indexing indexing self-assigned this Aug 7, 2024
@indexing indexing added the product Issue captures work for the product team label Aug 7, 2024
@indexing indexing moved this from Todo to In progress in Digital Services Aug 7, 2024
@indexing
Copy link
Member Author

indexing commented Aug 16, 2024

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

@indexing
Copy link
Member Author

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
Copy link
Member Author

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.

@indexing
Copy link
Member Author

indexing commented Oct 9, 2024

We met with the Blue Button API team yesterday as scheduled. The demo went well! We expect to hear back from the Blue Button API team within a week with any feedback and required changes.

@indexing
Copy link
Member Author

indexing commented Nov 6, 2024

On Oct 21, 2024, CDT received production credentials to access the Blue Button API. We are now completed final details related to the implementation so we can make this pathway available to agencies using the Benefits app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc) product Issue captures work for the product team
Projects
Status: In progress
Development

No branches or pull requests

1 participant