search

episphere / connect

Connect API for DCEG's Cohort Study
10 stars 5 forks source link

Block overwriting of date requested for data destruction, withdrawal and revocation #1093

Open brotzmanmj opened 2 months ago

brotzmanmj commented 2 months ago

Currently if a second request for data destruction is entered in the SMDB, our system overwrites the date data destruction requested (269050420) with the date of the second submission. We assume the same happens for date withdrawal requested (659990606) and date HIPAA revocation requested (664453818) if those are entered a second time, but we have not yet checked for this.

All three dates should not overwrite the original date if requested again.

rohanjay10 commented 2 months ago

Hi @brotzmanmj, if somebody puts in a second request for Data Destruction can we prevent the SMDB from submitting the data destruction form the second time, or should we prevent the data from being overwritten?

brotzmanmj commented 2 months ago

HI @rohanjay10 if we can prevent the SMDB from submitting the data destruction a second time (and display a message to the user to show that the request did not submit and why) that would be ideal.