Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

BYTE editors are people who separate the wheat from the chaff, and then carefully print the chaff.


devel / comp.protocols.dicom / Re: Modifying dicom header attributes before store to PACS

SubjectAuthor
* Re: Modifying dicom header attributes before store to PACSguiot...@gmail.com
`* Re: Modifying dicom header attributes before store to PACSPatrick A. Nast
 `- Re: Modifying dicom header attributes before store to PACSguiot...@gmail.com

1
Re: Modifying dicom header attributes before store to PACS

<1fe6e621-f212-4847-8985-5b7e118f3595n@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=416&group=comp.protocols.dicom#416

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:4310:b0:67b:3fc1:86eb with SMTP id u16-20020a05620a431000b0067b3fc186ebmr8734845qko.495.1650981450149;
Tue, 26 Apr 2022 06:57:30 -0700 (PDT)
X-Received: by 2002:ac8:59d0:0:b0:2f1:fc58:2fce with SMTP id
f16-20020ac859d0000000b002f1fc582fcemr15504421qtf.290.1650981449899; Tue, 26
Apr 2022 06:57:29 -0700 (PDT)
Path: i2pn2.org!i2pn.org!news.samoylyk.net!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Tue, 26 Apr 2022 06:57:29 -0700 (PDT)
In-Reply-To: <9693998e-0111-44c9-9456-51732cfde49e@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=193.191.131.34; posting-account=ZWzKCQoAAADGl251sIFSnldJzFPWDhiz
NNTP-Posting-Host: 193.191.131.34
References: <9693998e-0111-44c9-9456-51732cfde49e@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <1fe6e621-f212-4847-8985-5b7e118f3595n@googlegroups.com>
Subject: Re: Modifying dicom header attributes before store to PACS
From: guiothomas@gmail.com (guiot...@gmail.com)
Injection-Date: Tue, 26 Apr 2022 13:57:30 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 65
 by: guiot...@gmail.com - Tue, 26 Apr 2022 13:57 UTC

Le mardi 15 novembre 2016 à 10:34:30 UTC+1, lysenkoalex...@gmail.com a écrit :
> Hello!
>
> Our software allows customers to store dicom studies into PACS systems.
> Customers asked if they can edit some dicom attributes before storing, like:
>
> Patient ID (0x0010, 0x0020)
> Accession number (0x0008, 0x0050)
> Study description (0x0008, 0x1030)
>
> Pixel data and another attributes remains the same.
>
> I am looking for information in dicom standard(preferred) or some article that describes rules to match dicom standard when performing such changes.
>
> After reading Dicom standard Part 10: Media Storage and File Format for Media Interchange, Table 7.1-1 DICOM File Meta Information I have concluded that in addition to above 3 attributes from DataSet our software must modify following 2 attributes in meta-header:
> Implementation Class UID (0002,0012)
> Implementation Version Name (0002,0013)
>
> I have searched for answer in this google group and found following topic:
> https://groups.google.com/forum/#!searchin/comp.protocols.dicom/modifydicomheader|sort:relevance/comp.protocols.dicom/NKi3xz0Xkck/ZEHsMAYgWPQJ
>
> Above topic referes to http://gdcm.sourceforge.net/wiki/index.php/Writing_DICOM#Derived_DICOM_Images
>
> Does it mean that we need to insert Original Attributes Sequence (0400,0561)
> element and set all attributes:
> -Source of Previous Values (0400,0564)
> -Attribute Modification Datetime (0400,0562)
> -Modifying System (0400,0563)
> -Reason for the Attribute Modification (0400,0565)
> -Modified Attributes Sequence (0400,0550)
> this element will include list of updated attributes
>
> Question is:
> What are additional attributes that must be changed as part of edit operation?
>
> Is it mandatory to change Sop/Series/StudyInstanceUID?
>
> Best regards, Alexander

Hello
a little up for this old unanswered question because i have the exact same one. What is the policy when editing dicom tags, for instance, to correct patient weight that was incorrectly entered the first time ?
should a new seriesUID be created for this single edit ? other tags added ?
Since the edit was made to correct a mistake, it would make sense to discard the incorrect series entirely, and thus keeping the SeriesUID. However, different PACS may handle this case differently when receiving the corrected images. Some might discard the new series because it already has series with the same SeriesInstanceUID.

thanks
Thomas

Re: Modifying dicom header attributes before store to PACS

<5fe9411a-4512-46b5-b3bf-539e794c0e6fn@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=417&group=comp.protocols.dicom#417

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:648:b0:2f3:642d:c12a with SMTP id a8-20020a05622a064800b002f3642dc12amr11965471qtb.464.1651044463767;
Wed, 27 Apr 2022 00:27:43 -0700 (PDT)
X-Received: by 2002:ac8:59d0:0:b0:2f1:fc58:2fce with SMTP id
f16-20020ac859d0000000b002f1fc582fcemr18184655qtf.290.1651044463608; Wed, 27
Apr 2022 00:27:43 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Wed, 27 Apr 2022 00:27:43 -0700 (PDT)
In-Reply-To: <1fe6e621-f212-4847-8985-5b7e118f3595n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=147.161.251.88; posting-account=QfkPSAoAAADEkVUJMxFZ--NR17j3Onov
NNTP-Posting-Host: 147.161.251.88
References: <9693998e-0111-44c9-9456-51732cfde49e@googlegroups.com> <1fe6e621-f212-4847-8985-5b7e118f3595n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5fe9411a-4512-46b5-b3bf-539e794c0e6fn@googlegroups.com>
Subject: Re: Modifying dicom header attributes before store to PACS
From: patrick.nast@zeiss.com (Patrick A. Nast)
Injection-Date: Wed, 27 Apr 2022 07:27:43 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 76
 by: Patrick A. Nast - Wed, 27 Apr 2022 07:27 UTC

guiot...@gmail.com schrieb am Dienstag, 26. April 2022 um 15:57:31 UTC+2:
> Le mardi 15 novembre 2016 à 10:34:30 UTC+1, lysenkoalex...@gmail.com a écrit :
> > Hello!
> >
> > Our software allows customers to store dicom studies into PACS systems.
> > Customers asked if they can edit some dicom attributes before storing, like:
> >
> > Patient ID (0x0010, 0x0020)
> > Accession number (0x0008, 0x0050)
> > Study description (0x0008, 0x1030)
> >
> > Pixel data and another attributes remains the same.
> >
> > I am looking for information in dicom standard(preferred) or some article that describes rules to match dicom standard when performing such changes.
> >
> > After reading Dicom standard Part 10: Media Storage and File Format for Media Interchange, Table 7.1-1 DICOM File Meta Information I have concluded that in addition to above 3 attributes from DataSet our software must modify following 2 attributes in meta-header:
> > Implementation Class UID (0002,0012)
> > Implementation Version Name (0002,0013)
> >
> > I have searched for answer in this google group and found following topic:
> > https://groups.google.com/forum/#!searchin/comp.protocols.dicom/modifydicomheader|sort:relevance/comp.protocols.dicom/NKi3xz0Xkck/ZEHsMAYgWPQJ
> >
> > Above topic referes to http://gdcm.sourceforge.net/wiki/index.php/Writing_DICOM#Derived_DICOM_Images
> >
> > Does it mean that we need to insert Original Attributes Sequence (0400,0561)
> > element and set all attributes:
> > -Source of Previous Values (0400,0564)
> > -Attribute Modification Datetime (0400,0562)
> > -Modifying System (0400,0563)
> > -Reason for the Attribute Modification (0400,0565)
> > -Modified Attributes Sequence (0400,0550)
> > this element will include list of updated attributes
> >
> > Question is:
> > What are additional attributes that must be changed as part of edit operation?
> >
> > Is it mandatory to change Sop/Series/StudyInstanceUID?
> >
> > Best regards, Alexander
> Hello
> a little up for this old unanswered question because i have the exact same one. What is the policy when editing dicom tags, for instance, to correct patient weight that was incorrectly entered the first time ?
> should a new seriesUID be created for this single edit ? other tags added ?
> Since the edit was made to correct a mistake, it would make sense to discard the incorrect series entirely, and thus keeping the SeriesUID. However, different PACS may handle this case differently when receiving the corrected images. Some might discard the new series because it already has series with the same SeriesInstanceUID.
>
> thanks
> Thomas
Hi,

I would recommend to check following chapters of the standard:
https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.12.html#sect_C.12.1.1.9
https://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.4.html#sect_B.4.1.3

Regards,
Patrick

Re: Modifying dicom header attributes before store to PACS

<8baf5f71-969e-4964-91a6-007378ab06e7n@googlegroups.com>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=418&group=comp.protocols.dicom#418

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:6214:c2b:b0:446:512a:26f7 with SMTP id a11-20020a0562140c2b00b00446512a26f7mr19314730qvd.38.1651051008578;
Wed, 27 Apr 2022 02:16:48 -0700 (PDT)
X-Received: by 2002:a05:622a:104e:b0:2f3:8652:8b40 with SMTP id
f14-20020a05622a104e00b002f386528b40mr183720qte.357.1651051008412; Wed, 27
Apr 2022 02:16:48 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Wed, 27 Apr 2022 02:16:48 -0700 (PDT)
In-Reply-To: <5fe9411a-4512-46b5-b3bf-539e794c0e6fn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=193.191.131.34; posting-account=ZWzKCQoAAADGl251sIFSnldJzFPWDhiz
NNTP-Posting-Host: 193.191.131.34
References: <9693998e-0111-44c9-9456-51732cfde49e@googlegroups.com>
<1fe6e621-f212-4847-8985-5b7e118f3595n@googlegroups.com> <5fe9411a-4512-46b5-b3bf-539e794c0e6fn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <8baf5f71-969e-4964-91a6-007378ab06e7n@googlegroups.com>
Subject: Re: Modifying dicom header attributes before store to PACS
From: guiothomas@gmail.com (guiot...@gmail.com)
Injection-Date: Wed, 27 Apr 2022 09:16:48 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 5
 by: guiot...@gmail.com - Wed, 27 Apr 2022 09:16 UTC

Thanks Patrick.

Unfortunately, I don't think this fully answers the case I was referring to. This part deals with SCPs modifying attributes to reach conformance, and how to do it properly.
here I'm talking about editing values because they were wrongly entered in the first place. So the question is : when I do this correction, do I have to create a new Series/SOP Instance UID ?
The only thing I can take from sect_C.12.1.1.9 is that it's OK to keep the previous SOP/Series Instance UID when a SCP changes Attributes for some reason, so it should also be ok for me when I manually correct Attributes.

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor