For example: the staff working with the server through a Web-viewer and by mistake (or intentionally) removes the patient or research.
Backup copies of data are not made, and the patient or his doctor can re-request the data, but they will not be.
How to protect server from the removal of patients or research?
Not the best solution, but you may consider using postgres as the database, and using barman for incremental backups of the databse.
If you want to prevent users to DELETE data from Orthanc, consider adding a “IncomingHttpRequestFilter” Lua script that only allows HTTP GET requests:
https://orthanc.chu.ulg.ac.be/book/users/lua.html#filtering-incoming-rest-requests
Lua scripts must be declared in the “LuaScripts” section of the configuration file:
https://orthanc.chu.ulg.ac.be/book/users/configuration.html
Sébastien-
Hi,
With Sonic Dicom, they have a solution I thinks it’s OK
All delete studies will be in sub folder named : Delete
So we can find out studies is deleted!
Is this alright?
If so … it neither delete de studies … just move them and rename them, maybe to later run a ‘garbage collector’ proc that erase them forever.