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

[mdevans]

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]

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