Technical Discovery for "Give Vet clear expectations of claim status"

[mengA6]

Issue Description

Investigate the engineering work required in some potentially tricky parts of Submission Experience design for the milestone "Give Vet clear expectations of claim status". Goal is to anticipate and plan for technical challenges and/or inform other design solutions that allow us to implement more easily.

Related: Complete design for "Give Vet clear expectations of claim status"#84850

Figma screens / emails

Some items to investigate came from our meeting "Engineering feasibility for submission experience 6/13/24"

---

Items to investigate

• [ ] Can we get "date received"? is there an API already for that?
• [x] Linking to a specific Claim in Claim Status Tool? Yes, we can, but we have questions We won't need this until a later iteration
• [x] Can we trigger a "track your claim online" email from the claim showing up in Claim Status Tool? If this isn't easy to do, we can send the email on a delay based on when we expect the claim to be available in CST. We won't need this until a later iteration

Tasks

• [ ] What work is necessary for this story to be completed?

Acceptance Criteria

• [ ] What will be created or happen as a result of this story?

[pacerwow]

@mengA6 can this be closed? This looks to have been completed a couple of weeks ago.

[mengA6]

No, this is still relevant. These are outstanding questions that came out of our conversation and require further tech discovery. However, 2 are not relevant anymore based on the current simplified design direction, so I checked those off.