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
Users logs into ADIT and next to the existing apps they have access to an upload app. The upload app is also bound to a permission manged by an admin. An admin can grant users access to the upload app. How the upload form should look like can be seen in the diagramm avobe. To process the images on the server side, the existing ADIT infrastructure for receiving images should be used, see BatchTransfer App und ADIT Core. The client side can transfer the images unpseudonymized to th server. But the user can also select an internal pseudonymization and one with a user provided batch file.
General info regarding pseudonymization:
Happens on client side, using Java Script (dcmjs)
Happens on-the-fly
Image is received by the client browser on upload
Image is read
Image is pseudonymized
Image is send to ADIT server
Proceed with next image
General info for internal pseudonymization:
In general the same infroamtion as stated above is also valid for this pseudonymization type
Users can not assign pseudonyms, the complete process is handled by client side code
Technical workflow:
Take the department field from the user model of the currently uploading user
Put it in front of the PatientID extracted from the uploaded image (e.g. DIR123456)
Run SHA3-256 hashing function over the resulting string
Use new 64 byte long string as new PatientID and PatientName
Update the DICOM tags with that information
Pseudonymize leftover DICOM tags normally with dcmjs
Send image to server
Upload Job View
Same general info about the upload job as in a BatchTransferJob view
Upload tasks list also the same as in BatchTransferJob view
But additional View Results button as in a BatchQueryJob which the user can download
The downloaded CSV file should contain a column with PatientID and the newly assigned pseudonym
If the pseudonymization is None, the two columns are basically the same
If the pseudonymization is Batch file, the client gets the same list as initially provided by the user
If the pseudonymization is Internal, the client gets a list with the generated pseudonyms and PatientIDs
In the last to cases, no information about PatientID is transferred to the server, only pseudonym
In the first case, the PatientID is transferred to server, since no pseudonymization is applied
Implement frontend of upload app
Implement connection via websockets
Implement receiving image handling on server side
Implement new permissions for pseudonymization type on upload (see diagramm above)
Implement client side pseudonymization with Batch File
Implement client side pseudonymization with Internal hashing method
The text was updated successfully, but these errors were encountered:
Addition to the PSN process: Dept+ID Strings should be padded to ensure the same length before hashing, otherwise there's a small risk of being able to relate pseudonyms to departments, which is undesirable
Desired workflow
Users logs into ADIT and next to the existing apps they have access to an upload app. The upload app is also bound to a permission manged by an admin. An admin can grant users access to the upload app. How the upload form should look like can be seen in the diagramm avobe. To process the images on the server side, the existing ADIT infrastructure for receiving images should be used, see BatchTransfer App und ADIT Core. The client side can transfer the images unpseudonymized to th server. But the user can also select an internal pseudonymization and one with a user provided batch file.
General info regarding pseudonymization:
General info for internal pseudonymization:
Upload Job View
The text was updated successfully, but these errors were encountered: