Design | Service History API

[steele-lm]

Issue Description

We need to determine the best approach for pull in a Veteran's Service History through the Service History API. Here is an example of what is done on the Chapter 33 form.

Spike that determined what fields are available: #68092

---

Tasks

• [ ] What is the approach for unauthenticated users? It looks like Chapter 33 requires those users to manually enter.
• [ ] What is the approach for authenticated users that have service history on their record?
• [ ] What is the approach for authenticated users that do not have service history on their record (Chapter 33 displayed an alert)?

Acceptance Criteria

• [ ] Design approach for auto-filling military service history

[fiorella-io]

Synced up with Julie P. and Laura.

To do:

• [x] Create a feature brief under Burial (Add a link in the COE and Ch 31 readme pages to this feature brief)
• [x] Sync up with Micah and capture how Vet's API works
• [x] Connect with the profile / authenticated experience (#accountexp-authexp) to understand what information can be stored, and updated.

[fiorella-io]

The Profile team connects to a different API “Profile Service V3 API” and has the military history among other types of information from the Veteran. Based on this Slack thread, the information should be the same.

Profile Service V3 API - thread

• If the Veteran wants to update their military history, updates could take years if at all
• It shows a limited amount of information and the database is small (~1200 records)
• It only has deployment data after 2001

Outstanding questions:

• If the Veteran provides that information (by filling out our form), where can we save it so they don't have to re-enter it on another form? It looks like APIs are read-only information, and there might not be APIs that provide add/update functionality OR
• Can we attach their DD214 into their profile?

[fiorella-io]

Updates:

• COE: Since only the Veteran is accessing this form, we can prefill all military history once we link to the Profile V3 API
• Ch 36 PCPG: We will only prefill the military history if the Veteran is filling out the form.
• Burial: Further discovery is needed, such as:
  • Understanding the processors' journey
  • Tracking relationship with the Veteran
  • Tracking pages with the most drop-off
  • Tracking how many submissions have uploaded a DD214
  • Tracking the military history step

On 7/11, we decided first to conduct Burial's usability testing and understand the processors' journey and then decide on our next approach.

[fiorella-io]

Updates: On 7/18, we decided to ask our COE and Ch 36 PCPG SMEs and build a case as to why we should only require the claimant's latest service period.

To do:

• [x] Schedule a short meeting with Ch 36 PCPG SMEs, including our OCTO folks
• [x] Use the COE's sync meeting in August to discuss

[fiorella-io]

On July 22, our Ch36 SMEs mentioned that it's OK to only ask about the latest/current service periods for military history. When we prefill military history to this form, it can follow the 1010ez form: When the claimant gets to the Military history page, show the Service Period page filled in. Draft designs.