Will need to update the mri.yaml base file to ensure that patient sex, date of birth are ~overriden~ (overwritten?) with a fixed value instead of being deleted so that we don't get validation warnings. Might also be worth breaking out into two files, so that we have base.yaml for any modality, and then mri.yaml which adds in MRI-specific tags. https://dicom.innolitics.com/ciods isn't a bad place to see where tags are used at a higher level
Could do #418 before the rest of the other work to ensure that our configurations are DICOM standard compliant first
Definition of Done / Acceptance Criteria
The deidentification process is clearly documented and as a user, I can access this and see how my data has been deidentified
Testing
Documentation
Dependencies
Details and Comments
Probably a good place to start is the ms-pinpoint project de-identification, not keeping the study date as default.
Will need to update the mri.yaml base file to ensure that patient sex, date of birth are ~overriden~ (overwritten?) with a fixed value instead of being deleted so that we don't get validation warnings. Might also be worth breaking out into two files, so that we have
base.yaml
for any modality, and thenmri.yaml
which adds in MRI-specific tags. https://dicom.innolitics.com/ciods isn't a bad place to see where tags are used at a higher levelCould do #418 before the rest of the other work to ensure that our configurations are DICOM standard compliant first