(0400,0564) Source of Previous Values: The source that provided the SOP Instance prior to the removal or replacement of the values. For example, this might be the Institution from which imported SOP Instances were received.

in the item of the (0400,0561) Original Attributes Sequence is missing.

Its value may be empty, if you can't identify the source (Type 2)

(s. https://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.12.1.1.9-1 )

On Friday, March 10, 2023 at 4:51:49 PM UTC+1, Jeffrey Jedele wrote:
> Hey everyone, this is my first post here :)
>
> I searched if somebody asked this before but didn't find anything.
>
> I'm looking for some confirmation if I understand correctly how the OriginalAttributesSequence (0400,0561) should be used. I didn't so far find any information which left me with 100% certainty.
>
> Scenario: We have a software that allows storing DICOM data. For diverse reasons, when storing this data we sometimes have to assign new UIDs and want to retain the original IDs as it intended by the standard.
>
> This is how I currently understand how it should be done (I hope my custom DICOM/JSON is easily understandable):
>
> Original:
> {
> "(0008,0018)|SOPInstanceUID": "org.inst.id",
> "(0020,000D)|StudyInstanceUID": "org.study.id",
> "(0008,1030)|StudyDescription": "examination x ...",
> }
>
> After IDs have been rewritten:
> {
> "(0008,0018)|SOPInstanceUID": "new.inst.id",
> "(0020,000D)|StudyInstanceUID": "new.study.id",
> "(0008,1030)|StudyDescription": "examination x ...",
> "(0400,0561)|OriginalAttributesSequence": [
> {
> "(0400,0562)|AttributeModificationDateTime": "20230101",
> "(0400,0563)|ModifyingSystem": "my SW vX",
> "(0400,0565)|ReasonForTheAttributeModification": "COERCE",
> "(0400,0550)|ModifiedAttributesSequence": [
> {
> "(0008,0018)|SOPInstanceUID": "org.inst.id",
> "(0020,000D)|StudyInstanceUID": "org.study.id",
> }
> ],
> }
> ],
> }
>
> Is this correct?
>
> Thx and regards,
> Jeff

On Monday, March 27, 2023 at 3:52:21 PM UTC+2, gunter zeilinger wrote:
> (0400,0564) Source of Previous Values: The source that provided the SOP Instance prior to the removal or replacement of the values. For example, this might be the Institution from which imported SOP Instances were received.
>
> in the item of the (0400,0561) Original Attributes Sequence is missing.
>
> Its value may be empty, if you can't identify the source (Type 2)
>
> (s. https://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.12.1.1.9-1 )
> On Friday, March 10, 2023 at 4:51:49 PM UTC+1, Jeffrey Jedele wrote:
> > Hey everyone, this is my first post here :)
> >
> > I searched if somebody asked this before but didn't find anything.
> >
> > I'm looking for some confirmation if I understand correctly how the OriginalAttributesSequence (0400,0561) should be used. I didn't so far find any information which left me with 100% certainty.
> >
> > Scenario: We have a software that allows storing DICOM data. For diverse reasons, when storing this data we sometimes have to assign new UIDs and want to retain the original IDs as it intended by the standard.
> >
> > This is how I currently understand how it should be done (I hope my custom DICOM/JSON is easily understandable):
> >
> > Original:
> > {
> > "(0008,0018)|SOPInstanceUID": "org.inst.id",
> > "(0020,000D)|StudyInstanceUID": "org.study.id",
> > "(0008,1030)|StudyDescription": "examination x ...",
> > }
> >
> > After IDs have been rewritten:
> > {
> > "(0008,0018)|SOPInstanceUID": "new.inst.id",
> > "(0020,000D)|StudyInstanceUID": "new.study.id",
> > "(0008,1030)|StudyDescription": "examination x ...",
> > "(0400,0561)|OriginalAttributesSequence": [
> > {
> > "(0400,0562)|AttributeModificationDateTime": "20230101",
> > "(0400,0563)|ModifyingSystem": "my SW vX",
> > "(0400,0565)|ReasonForTheAttributeModification": "COERCE",
> > "(0400,0550)|ModifiedAttributesSequence": [
> > {
> > "(0008,0018)|SOPInstanceUID": "org.inst.id",
> > "(0020,000D)|StudyInstanceUID": "org.study.id",
> > }
> > ],
> > }
> > ],
> > }
> >
> > Is this correct?
> >
> > Thx and regards,
> > Jeff
Ok, thx for the input Gunter!