Replies: 1 comment 1 reply
-
The behavior is configurable by attribute
on Archive Device and Archive Network AE level. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
The archive appears to automatically assign a value to the Patient ID attribute if none of the patient or study level attributes have a value. These are all type 2 attributes and so the values may be rightfully missing (e.g., after de-identification).
The archive should not just modify the data upon storage. This behavior is very problematic. For example, if one stores a set of images in the archive, then derives other objects from these images (e.g., an SR document), inheriting the patient and study level metadata from the source image, and finally downloads the derived object, then the metadata in the derived object will be different from the image that was stored in the first place. If one then tries to store both the original images and derived object in another archive, this archive will complain that the metadata is different and will refuse to store the data.
Beta Was this translation helpful? Give feedback.
All reactions