Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data model inconsistency: Manage case of different PatientID's within same study #18

Open
mdevans opened this issue Oct 21, 2024 · 1 comment
Assignees
Labels
invalid This doesn't seem right

Comments

@mdevans
Copy link
Collaborator

mdevans commented Oct 21, 2024

As per logs provided by Adam Flanders on 18 Oct 2024 from TJU data retrieval project.

2024-10-16 14:56:22,125 ERROR AnonWorker_1 controller.anonymizer._write_to_quarantine.184 Storage Error = Critical error PHI PatientID=****** not found in patient_id_lookup, QUARANTINE to <storage_directory>\private\quarantine\Capture_PHI_Error******<studyUID><seriesUID><instanceUID> .dcm

=> Do reverse lookup to get the Anonymized PatientID already associated with this

@mdevans mdevans added the invalid This doesn't seem right label Oct 21, 2024
@mdevans mdevans self-assigned this Oct 21, 2024
@mdevans
Copy link
Collaborator Author

mdevans commented Oct 25, 2024

From log analysis of ProjectController._handle_stoer remote scp (VNA) definitely mixing PatientIDs within same study.
To prove, added to Anonymizer Version 17.2.1-RC3
IF pydicom logging enabled then incoming datasets, either via network or file import, will be stored in private subdir or storage directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant