[SPIKE] How are we going to set up a database to store referral IDs?

department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:

https://depo-platform-documentation.scrollhelp.site/index.html

281 stars 197 forks source link

[SPIKE] How are we going to set up a database to store referral IDs? #91911

Open benbrasso-agile6 opened 2 weeks ago

benbrasso-agile6 commented 2 weeks ago

Description

How are we going to set up a database to store new referral IDs from EPS? (Stephen suggested reusing the existing database. Maybe talking about the CHIP db.)

Community Care VSS referral to VA Notify userflow

Tasks

[ ] Flesh out workflow or architecture of storing referrals IDs, encrypting, generating short urls for each referral ID, and managing which short urls (or db records) have been sent to VA Notify (or not yet). E.g., we shouldn't deliver the same referral ID/short url more than once to VA Notify.
[ ] Create any implementation tickets needed.

benbrasso-agile6 commented 2 weeks ago

Hey team! Please add your planning poker estimate with Zenhub @lee-delarm6 @simiadebowale

lee-delarm6 commented 1 week ago

receive referral ID from EPS
encrypt referral ID, store encrypted
Store data in postgres DB via vets-api
retrieve as necessary (for passthrough back to EPS

benbrasso-agile6 commented 1 week ago

Note: We are no longer getting referral IDs from EPS. Right now, it's TBD (for Stephen to tell us next steps). I've updated what we know in the userflow here - https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1724857034587/50f5a6735d13d9273970da070a5573385dd7fb2c?wid=0-1724938592386

It is sounding like we might get either referral IDs or a Consult Factor status from CDW via a nightly job. But, TBD.