-
Notifications
You must be signed in to change notification settings - Fork 9
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 Veteran Service History and Eligibility API #2294
Comments
At our weekly check-in on Monday, 8/21, CDT reported that the VA continues to proactively reach out on a periodic basis to confirm they are reviewing our request for access, but still no meaningful progress toward a next step. We have communicated to the VA that we would like to launch enhancements to Veteran eligibility checks by Veterans Day (November 11, 2024). |
At our weekly check-in on Monday, 8/26, CDT reported there was no update from the VA on contracting. |
At our weekly check-in on Monday, 9/9, CDT reported there was no update from the VA on contracting. |
At our weekly check-in on Monday, 9/16, CDT reported there was no update from the VA on contracting. If we are aiming to have enhanced eligibility checks for Veterans available by Veterans Day in November, we need to think about escalating our request soon. Prior to escalating we need, we need more clarity on the scope of our ask. I will be refining the enhancements to our policy for Veterans in preparation. |
At our weekly check-in on Monday, 9/23, CDT reported there was no update from the VA on contracting. |
At our weekly check-in on Monday, 9/30, CDT reported there was no update from the VA on contracting. |
At our weekly check-in on Monday, 11/04, CDT reported there was no update from the VA on contracting. |
At our weekly check-in on Tuesday, 11/12, CDT reported there was no update from the VA on contracting. |
At our weekly check-in on Tuesday, 11/18, CDT received an email during our meeting that providing instructions to “begin the onboarding process” for the API. We're not sure what this means yet, but it's a glimmer of hope that we are making progress in our effort to get authority to operate. |
We implemented use of the Veteran Confirmation API in November 2023. See #1691 for details. While this API supports checks for Title 38 status, another API from the Veterans Administration—the Veteran Service History and Eligibility API—provides much more robust options for determining transit benefit eligibility, including the rider's disability status as a Veteran.
CDT applied for production access to this API early in 2024. 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
The text was updated successfully, but these errors were encountered: