You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add settings and functionality to automatically delete really old encounters, fully configurable by the user but there will be a maximum time where all encounters will be deleted to prevent bloat.
Acceptance Criteria
FE: Add a setting on the settings page for this feature
BE: Configure backend to auto delete encounters after they exceed a certain timestamp
BE: Implement pruning endpoint, where users can specify a date before which they want all encounters pruned.
Implementation details
One new API call for the settings page, deletion is completely backend.
Pruning is manual, users can select a date to prune before in the Settings page.
Pruning is relative to time_updated field in Encounter
Testing notes
Backend tests created to check if Encounters preceding prune data are correctly deleted
Future plans
If needed, can also create a pruning feature for encounter dates, instead of time_updated
The text was updated successfully, but these errors were encountered:
* Added TTL for encounters of 1 year
* Pruning endpoint created.
Takes input of date which we want to prune before
TODO testing.
* Added test to check that encounters before prune date are deleted
* Fixed prune test to properly call api
* Added TTL for encounters of 1 year
* Pruning endpoint created.
Takes input of date which we want to prune before
TODO testing.
* Added test to check that encounters before prune date are deleted
* Fixed prune test to properly call api
Description
Add settings and functionality to automatically delete really old encounters, fully configurable by the user but there will be a maximum time where all encounters will be deleted to prevent bloat.
Acceptance Criteria
Implementation details
One new API call for the settings page, deletion is completely backend.
Pruning is manual, users can select a date to prune before in the Settings page.
Pruning is relative to
time_updated
field in EncounterTesting notes
Backend tests created to check if Encounters preceding prune data are correctly deleted
Future plans
If needed, can also create a pruning feature for encounter dates, instead of
time_updated
The text was updated successfully, but these errors were encountered: