SPIKE: Identify deleting referral information we no longer need.

[loripusey]

Resources

Here’s a message from Stephen about the query to write to export data form Palantir. Might place it in ticket: https://dsva.slack.com/archives/C06RMRJCLHH/p1726602417747879?thread_ts=1726505070.527829&cid=C06RMRJCLHH

https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1724857034587/50f5a6735d13d9273970da070a5573385dd7fb2c

Task

• Identify and implement deleting referral information we no longer need. E.g., do we want to check if the appointment has been scheduled? Does the referral status change to scheduled? Do we delete them after the referral expiration date?

[lee-delarm6]

Two tier approach

First Pass (one which will be used for first release)

• Initial approach will be to store referral data from Palantir for as long as the appointment does not exist in vista-api-x. We'll check this daily. Before the appointment makes its way into vista, we can reference the appointment in EPS on the appointments list (this is outside the referral area), if we see the user has a referral still in the system. If the user checks their appointments, we can also make a check at that time to see if they have an appointment in vista that matches their referral. To recap:
  • Referral data stored until appointment is verified in vista
  • Verifying means checking that the referral data, now an appointment, that is created in EPS now exists in vista via matching patientICN, provider, and other data, as referralID numbers may not match up (following up)
  • Verifying occurs once a day, scanning for existing vista appointments that match the EPS appointment data
  • Verifying ALSO happens when a user logs in to see their appointments (same scan occurs and same removal occurs)
  • We can then remove the referral data we have in store

Second Tier

At some point in the future, HSRM will be able to provide us a referralID (or someone will) so we will not need to store the referral information past the point that a user makes an appointment using it. We will be able to use HSRM (via VAOS) to pull referral data, and thereby any associated appointments from EPS or other systems

Addendum

In addition, in either case we should delete referral's after the expiration date. There is no scope to determine if referrals are made by user error by facilities at this time (and hence should be deleted early). This deletion can occur at the same time we do the daily scan for new referrals

[loripusey]

@randomsync @kanchanasuriya to validate