Open
Description
Benefit to the Veteran
As a Veteran, I would like to be able to submit my 10-10EZR and have it be processed as normal so that I don't have to pay co-pays and the VA knows who to bill (my insurance) for my medical care.
Hypothesis or Bet
If we make this change, we will modernize the process for how we send information to VES
If we make this change, we will stabilize how we send data to VES
OKR
Which Objective / Key Result does this epic push forward?
It works the same as the previous SOAP API
Background
- What details are necessary for understanding the specific work or request tracked by this issue?
- In Fall 2024, Josh Faulkner notified us that VES would be migrating from its current SOAP API to a new Rest API. The timeline was, and remains, TBD. The new Rest API will be designed to mimic the SOAP API. There may be some improved functionality with how Rest handles "associations."
- What are we doing within the scope of this ticket?
- Same functionality as before
- MAYBE EC and NoK will be added, but the FE of that is out of scope
- Is there anything specifically out of scope of this ticket?
- FE for EC/NoK
- Anything not current functionality with SOAP API
- Is there anything that must be done before this ticket? (link ticket as dependency)
- VES needs to finish REST API
- Are there any external dependencies?
- VES
Resources
- Product or Initiative brief links
- Design links
- Screenshots
- Reference docs/tickets where we have this kind of work documented
- Etc.
Acceptance Criteria/Definition of Done
- What will be created or happen as a result of this story?
How to configure this issue
- Labeled with Team (
1010-team) - Labeled with Form (
1010-ez,1010-ezr,1010-cg) - Labeled with Project (
facilities-cg,registration,toxic-exposure, etc.)
Activity