VRE | Update json payload

[steele-lm]

Issue Description

The Chapter 31 digital form payload is currently sent to CMS, which is being retired. The payload will be redirected to point to the RES system through this work, and the json payload needs to be updated to include missing fields (fields that appear on the form but not the json).

Open question: Are these fields actually missing or are they included on the new version of the form (but VA.gov is using the old version).

Answer: The pdf generated on VA.gov is the old version of the form. The fields listed below are new (or missing) from the payload and need to be added. Work to update the frontend of the form is captured in #65900.

Documentation: The RES team provided the following document that contains an example of what the json file could look like with the new fields: RES - VA GOV Requirements Document v1.0.docx

---

Tasks

• [ ] Update json to include the following fields:
  • [ ] internationalNumber (new field)
  • [ ] receiveElectronicCommunication (new field)
  • The following fields were added as part of #65386
    • ssn
    • cellNumber
    • receivedDate
• [ ] Separate the regional office / station ID field into two fields:
  • Right now, it looks like this: “regionalOffice": "317 - St. Petersburg"
  • Ideally, it would be separated into two fields
    • “stationID”: “317”
    • “regionalOffice”: “St. Petersburg”
• [ ] documentID
  • When a document is uploaded by VA.gov to the VBMS eFolder via Claim Evidence API, VA.gov receives a document ID from the upload service. RES is requesting that the document ID be included in the payload sent to RES. This is so that RES can directly identify which JSON payload corresponds to which eFolder document in the case that multiple 28-1900 forms are found in the Veteran’s eFolder. Hope Lam is a resource for tracking down this number.

Acceptance Criteria

• [ ] json file contains new fields
• [ ] Regional office and station ID have been separated into two fields
• [ ] json file contains documentID

• [ ] RES Team updated that changes have been made

### Tasks

[sortizsh]

Handoff to Micah

[steele-lm]

@micahaspyr and @DLarson-Oddball I just wanted to flag that the RES team provided some documentation (added to the ticket summary) and requested that documentID be added to the json in addition to the other fields they previously requested.

[micahaspyr]

@steele-lm Ok, that shouldn't be a problem. Honestly, I haven't looked at this ticket in awhile. Are we needing to bump up the priority?

[steele-lm]

@micahaspyr No need to prioritize right now. We are scheduled to pick it up in sprint 24 or 25.

[emilytheis]

Note re: documentID., we likely don't use the Claim Evidence API, we likely use the older VBMS eFolder SOAP service. Hope indicated on a call 4/11 that we should still be getting the docID back.

[micahaspyr]

I checked and we do use the older VBMS soap service. Yuck...

[sortizsh]

we need to do this once we complete the form update and add the fields to the fe. moving to BL