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

Merge VAProfile Health Benefit Services into V3::ProfileInformation #86486

Open
9 tasks
Tracked by #83183 ...
jennb33 opened this issue Jun 20, 2024 · 0 comments
Open
9 tasks
Tracked by #83183 ...

Merge VAProfile Health Benefit Services into V3::ProfileInformation #86486

jennb33 opened this issue Jun 20, 2024 · 0 comments
Assignees
Labels
2024 backend needs-refinement Identifies tickets that need to be refined platform-product-team va-profile For all issues/bugs/requests that have to do with the VA Profile team & integration

Comments

@jennb33
Copy link
Contributor

jennb33 commented Jun 20, 2024

User Story

As the engineers working on the EVSS PCIU migration objective,
It is is important that the v2::ContactInformation is updated to v3::ProfileInformation
So that the EVSS PCIU migration work can be completed

Issue Description

V3::ProfileInformation is a service that pulls data from multiple VAProfile services currently being used in Vets-API. Upgrading from V2::ContactInformation to V3::ProfileInformation will reduce the number of requests and simplify the Vets-API infrastructure. This ticket is to replace each applicable service to use V3::ProfileInformation. The following services can be merged into V3::ProfileInformation:

  • VaProfile::Profile
  • VaProfile::Communication
  • VAProfile::Demographics
  • VeteranVerification::DisabilityRating
  • VaProfile::HealthBenefit
  • VaProfile::MilitaryPersonnel

Tasks

  • Merge MilitaryPersonnel Services into V3::ProfileInformation
  • Test MilitaryPersonnel Services on V3::ProfileInformation
  • Deprecate V2::MilitaryPersonnel
  • Update any relevant documentation for VAProfile

Success Metrics

  • Number of requests to Vets-API have been reduced after the merge of all profiles by X%
  • Vets-API infrastructure is simplified (how was it simplified? Process?)

Acceptance Criteria

  • All MilitaryPersonnel Services profiles have been merged
  • All MilitaryPersonnel Services profiles have been tested and validated post-merge
  • All relevant documentation has been updated

The services were derived from this list of Va::ProfileInformation data

- contactInformation
- militaryPerson.transferOfEligibility
- benefitAwardInformation
- communicationPermissions
- demographics
- disabilityRating
- healthBenefit
- militaryPerson.adminDecisions
- militaryPerson.dentalIndicators
- militaryPerson.militaryOccupations
- militaryPerson.payGradeRanks
- militaryPerson.prisonerOfWars
- militaryPerson.militaryServiceHistory
- militaryPerson.militarySummary
- militaryPerson.militarySummary.customerType.dodServiceSummary
- personAttributes
- militaryPerson.adminEpisodes
- genderIdentityTraits
- militaryPerson.retirements
- militaryPerson.separationPays
- militaryPerson.retirementPays
- militaryPerson.combatPays
- militaryPerson.unitAssignments
- militaryPerson.medalsAndAwards

## Validation
_Assignee to add steps to this section. List the actions that need to be taken to confirm this issue is complete. Include any necessary links or context. State the expected outcome._
@jennb33 jennb33 added 2024 backend needs-grooming Use this to designate any issues that need grooming from the team needs-refinement Identifies tickets that need to be refined platform-product-team va-profile For all issues/bugs/requests that have to do with the VA Profile team & integration labels Jun 20, 2024
@jennb33 jennb33 changed the title Copy of Merge VAProfile Demographics Services into V3::ProfileInformation Merge VAProfile Health Benefit Services into V3::ProfileInformation Jun 20, 2024
@jennb33 jennb33 removed the needs-refinement Identifies tickets that need to be refined label Jul 29, 2024
@AshleyGuerrant AshleyGuerrant added needs refinement needs further review and discussion at a refinement session needs-refinement Identifies tickets that need to be refined and removed needs-grooming Use this to designate any issues that need grooming from the team needs refinement needs further review and discussion at a refinement session labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2024 backend needs-refinement Identifies tickets that need to be refined platform-product-team va-profile For all issues/bugs/requests that have to do with the VA Profile team & integration
Projects
None yet
Development

No branches or pull requests

3 participants