On-site anonymisation
Data from participating facilities can be anonymised before it reaches XNAT. The on-site protocol documented here applies to data from HIRF and CAI.
How on-site anonymisation fits
Section titled “How on-site anonymisation fits”On-site anonymisation changes selected DICOM values before the files are transferred. It provides a baseline transformation before any project anonymiser runs during ingestion into an XNAT project.
Confirm that the values produced by the protocol match your project’s approved naming and anonymisation requirements before transferring data.
Modified tags
Section titled “Modified tags”The protocol replaces the following tag values. The example values illustrate the resulting format.
| DICOM Tag | Original value | New value |
|---|---|---|
| PatientBirthDate | 10/12/2000 | 1/1/2000 |
| PatientComments | XXXXXXXX | Project:Proj001 Subject:TEST_MR Session:TEST_MR-20210405T1220 |
| ReferringPhysicianName | Proj001 | Proj001 |
| PatientName | XXXXXXXX | TEST_MR |
| PatientID | TEST_MR | TEST_MR-20210405T1220 |
Blanked tags
Section titled “Blanked tags”The protocol removes the values from the following tags.
| DICOM Tag |
|---|
| AccessionNumber |
| ImageComments |
| OperatorName |
| OtherPatientIDs |
| AdditionalPatientHistory |
| AdmittingDiagnosisDescription |
| MedicalRecordLocator |
| NameOfPhysicianReadingStudy |
| Occupation |
| OtherPatientNames |
| PatientBirthTime |
| PerformingPhysicianName |
| PhysicianOfRecord |
| ReferringPhysicianAddress |
| ReferringPhysicianPhoneNumbers |
Next steps
Section titled “Next steps”Project anonymiserApply a project-specific DICOM tag and naming scheme during archiving.
Uploading and downloading dataCompare the available methods for moving data into and out of XNAT.