Rocksolid Light

Welcome to Rocksolid Light

mail  files  register  newsreader  groups  login

Message-ID:  

Not only is UNIX dead, it's starting to smell really bad. -- Rob Pike


devel / comp.protocols.dicom / Question on IOD Tables in revised Part 2

SubjectAuthor
* Question on IOD Tables in revised Part 2Markus Sabin
`* Question on IOD Tables in revised Part 2Peter Chripunow
 `* Question on IOD Tables in revised Part 2Markus Sabin
  `* Question on IOD Tables in revised Part 2Jörg_Riesmeier
   `* Question on IOD Tables in revised Part 2Marco Kemper
    `- Question on IOD Tables in revised Part 2Markus Sabin

1
Question on IOD Tables in revised Part 2

<75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>

  copy mid

https://news.novabbs.org/devel/article-flat.php?id=812&group=comp.protocols.dicom#812

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:6f04:b0:405:4ef2:b3b1 with SMTP id iv4-20020a05622a6f0400b004054ef2b3b1mr71921qtb.0.1693314283149;
Tue, 29 Aug 2023 06:04:43 -0700 (PDT)
X-Received: by 2002:ad4:4a6d:0:b0:649:d110:9746 with SMTP id
cn13-20020ad44a6d000000b00649d1109746mr933208qvb.11.1693314282982; Tue, 29
Aug 2023 06:04:42 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Tue, 29 Aug 2023 06:04:42 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=212.204.96.130; posting-account=FpWjmwoAAADouxZodjPwb9TZUXzY1wOz
NNTP-Posting-Host: 212.204.96.130
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>
Subject: Question on IOD Tables in revised Part 2
From: markussabin@gmail.com (Markus Sabin)
Injection-Date: Tue, 29 Aug 2023 13:04:43 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Markus Sabin - Tue, 29 Aug 2023 13:04 UTC

Dear DICOM experts,

we are currently updating the DCS of our DICOM library to the latest Part 2.. I can tell it is a lot of work :-D.

I have a question about the IOD tables.N.9 A.A names a list of terms for the "Source" column. It says they "can be used" and does not explicitly state that other values "can not be used". But I am interpreting it this way.

Question 1: Correct? It is not allowed / desired that authors of the DCS would extend the terms?

Supposed that the answer is "Correct, you may only use these terms in Part 2"...my "problem" refers to the Referenced Performed Procedure Step Sequence (0008,1111). Technically, the source is "MPPS" here, but this is not an allowed term. The best approximation seems to be "GENERATED" to me, but that's a very generic term, and I wonder why "from MWL" can be explicitly expressed while "from MPPS" can not.

Question 2: Any hint how I should go about that?

Thank you very much

Markus

Re: Question on IOD Tables in revised Part 2

<5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com>

  copy mid

https://news.novabbs.org/devel/article-flat.php?id=814&group=comp.protocols.dicom#814

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ad4:4a6d:0:b0:63d:2a18:b07b with SMTP id cn13-20020ad44a6d000000b0063d2a18b07bmr29528qvb.10.1693379101945;
Wed, 30 Aug 2023 00:05:01 -0700 (PDT)
X-Received: by 2002:a17:902:dacb:b0:1bd:df9a:4fc6 with SMTP id
q11-20020a170902dacb00b001bddf9a4fc6mr451712plx.4.1693379101701; Wed, 30 Aug
2023 00:05:01 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Wed, 30 Aug 2023 00:05:00 -0700 (PDT)
In-Reply-To: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=147.161.137.23; posting-account=uEdamQoAAAB4v_2PWXmtCkd7Au0jNOPq
NNTP-Posting-Host: 147.161.137.23
References: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com>
Subject: Re: Question on IOD Tables in revised Part 2
From: peter.chripunow@siemens-healthineers.com (Peter Chripunow)
Injection-Date: Wed, 30 Aug 2023 07:05:01 +0000
Content-Type: text/plain; charset="UTF-8"
 by: Peter Chripunow - Wed, 30 Aug 2023 07:05 UTC

Hi Markus,

Fair question, made me curious, too.
There is the following instruction: "For the "Source" column use one of the pre-defined terms above [...]". This sounds straight and would not need a term like "shall" because it directly addresses the reader.
So, maybe therein lies the answer.

Regarding "MPPS" vs "GENERATED" it can be argued that MPPS information is indeed "generated by the system".
It's like: A breed of a dog is a dog, yet a dog can be of any breed.
Maybe either of the columns "Value" or "Comments" are the intended means to tell the breed.
How your sw archticture manages procedure steps and created objects might not be relevant, here.

Anyway, let's see if there will be more certain replies.

Best regards,
Peter

Re: Question on IOD Tables in revised Part 2

<281225d9-3630-478f-a296-12d9ec258b48n@googlegroups.com>

  copy mid

https://news.novabbs.org/devel/article-flat.php?id=815&group=comp.protocols.dicom#815

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:1a12:b0:412:14a0:448e with SMTP id f18-20020a05622a1a1200b0041214a0448emr51083qtb.1.1693394508232;
Wed, 30 Aug 2023 04:21:48 -0700 (PDT)
X-Received: by 2002:a05:6a00:2da3:b0:68a:46d4:b863 with SMTP id
fb35-20020a056a002da300b0068a46d4b863mr694011pfb.4.1693394507964; Wed, 30 Aug
2023 04:21:47 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Wed, 30 Aug 2023 04:21:47 -0700 (PDT)
In-Reply-To: <5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=93.104.238.112; posting-account=FpWjmwoAAADouxZodjPwb9TZUXzY1wOz
NNTP-Posting-Host: 93.104.238.112
References: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com> <5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <281225d9-3630-478f-a296-12d9ec258b48n@googlegroups.com>
Subject: Re: Question on IOD Tables in revised Part 2
From: markussabin@gmail.com (Markus Sabin)
Injection-Date: Wed, 30 Aug 2023 11:21:48 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1557
 by: Markus Sabin - Wed, 30 Aug 2023 11:21 UTC

Peter Chripunow schrieb am Mittwoch, 30. August 2023 um 09:05:03 UTC+2:
> Hi Markus,
>
> Maybe either of the columns "Value" or "Comments" are the intended means to tell the breed.

Good idea. If there is no better suggestion, I'll go ahead this way. Source = "CONVERTED" and Comment = "from MPPS" would tell the story. Thanks for your suggestion.

Re: Question on IOD Tables in revised Part 2

<7effe5b9-0eef-4a01-b875-c4ff9f4b3c82n@googlegroups.com>

  copy mid

https://news.novabbs.org/devel/article-flat.php?id=816&group=comp.protocols.dicom#816

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:6214:18c7:b0:651:62a3:6480 with SMTP id cy7-20020a05621418c700b0065162a36480mr336qvb.4.1693410750078;
Wed, 30 Aug 2023 08:52:30 -0700 (PDT)
X-Received: by 2002:a17:90a:d682:b0:268:5afe:888 with SMTP id
x2-20020a17090ad68200b002685afe0888mr586578pju.1.1693410749525; Wed, 30 Aug
2023 08:52:29 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Wed, 30 Aug 2023 08:52:28 -0700 (PDT)
In-Reply-To: <281225d9-3630-478f-a296-12d9ec258b48n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=85.16.184.31; posting-account=P9OsJAoAAABf_UoLgO-4Y0jtck08GqVx
NNTP-Posting-Host: 85.16.184.31
References: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>
<5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com> <281225d9-3630-478f-a296-12d9ec258b48n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7effe5b9-0eef-4a01-b875-c4ff9f4b3c82n@googlegroups.com>
Subject: Re: Question on IOD Tables in revised Part 2
From: dicom@jriesmeier.com (Jörg Riesmeier)
Injection-Date: Wed, 30 Aug 2023 15:52:30 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 1534
 by: Jörg Riesmeier - Wed, 30 Aug 2023 15:52 UTC

Markus,

you might also want to contact DICOM WG-31 (Conformance) [1] and ask what their intention was when they wrote "can be used" :-)

[1] https://www.dicomstandard.org/activity/wgs/wg-31

Regards,
Jörg

Re: Question on IOD Tables in revised Part 2

<0cedf97e-b059-4852-803a-015694e93d1dn@googlegroups.com>

  copy mid

https://news.novabbs.org/devel/article-flat.php?id=818&group=comp.protocols.dicom#818

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:6214:1921:b0:64a:5473:41e9 with SMTP id es1-20020a056214192100b0064a547341e9mr184635qvb.0.1693769760695;
Sun, 03 Sep 2023 12:36:00 -0700 (PDT)
X-Received: by 2002:a17:903:191:b0:1bb:d27f:ac46 with SMTP id
z17-20020a170903019100b001bbd27fac46mr2945864plg.2.1693769760374; Sun, 03 Sep
2023 12:36:00 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Sun, 3 Sep 2023 12:35:59 -0700 (PDT)
In-Reply-To: <7effe5b9-0eef-4a01-b875-c4ff9f4b3c82n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=77.171.131.33; posting-account=EqcuLAoAAAAkq_ZTomtkVhGsgVgFygqJ
NNTP-Posting-Host: 77.171.131.33
References: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>
<5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com> <281225d9-3630-478f-a296-12d9ec258b48n@googlegroups.com>
<7effe5b9-0eef-4a01-b875-c4ff9f4b3c82n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0cedf97e-b059-4852-803a-015694e93d1dn@googlegroups.com>
Subject: Re: Question on IOD Tables in revised Part 2
From: dicom.workshopfor.me@gmail.com (Marco Kemper)
Injection-Date: Sun, 03 Sep 2023 19:36:00 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Marco Kemper - Sun, 3 Sep 2023 19:35 UTC

Hi Markus,

I have written a few DICOM Conformance Statements for customers in the past, and am still offering this as a service through https://www.workshopfor.me/. So I think I can help you with this :).

If the information for this attribute was received by MPPS, then MPPS should be specified in the source column, and the value MPPS should also be defined in the beginning of this section, after the sentence "In the "Source" column, the following Values can be used". If e.g. your system would also have a HL7 interface, then HL7 could also be used in the source column in the same way. The most important thing here is that the reader of the DCS knows where all information for a created SOP Instances comes from, and the reader would expect to see this in the Source column, and not in other columns..

Also note "[For all SOP Instances of supported Storage SOP Classes (including Real-Time Video objects) that can be created by the system".
I was not able to find Referenced Performed Procedure Step Sequence (0008,1111) in part 3, so I am wondering if the information you are describing actually belongs in the N.9 AA section?

Regards,
Marco

Re: Question on IOD Tables in revised Part 2

<87664531-53b3-439b-8596-8abb60f1f113n@googlegroups.com>

  copy mid

https://news.novabbs.org/devel/article-flat.php?id=819&group=comp.protocols.dicom#819

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:5b03:0:b0:410:a9dd:9fe4 with SMTP id m3-20020ac85b03000000b00410a9dd9fe4mr217948qtw.1.1693812022044;
Mon, 04 Sep 2023 00:20:22 -0700 (PDT)
X-Received: by 2002:a17:902:ec8f:b0:1bf:559a:7bd6 with SMTP id
x15-20020a170902ec8f00b001bf559a7bd6mr3634548plg.3.1693812021458; Mon, 04 Sep
2023 00:20:21 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Mon, 4 Sep 2023 00:20:20 -0700 (PDT)
In-Reply-To: <0cedf97e-b059-4852-803a-015694e93d1dn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=93.104.238.112; posting-account=FpWjmwoAAADouxZodjPwb9TZUXzY1wOz
NNTP-Posting-Host: 93.104.238.112
References: <75bc6ce0-d6a4-42ba-8e1f-93024dfb4452n@googlegroups.com>
<5041c6da-14f2-4b29-a094-a986f4c46fden@googlegroups.com> <281225d9-3630-478f-a296-12d9ec258b48n@googlegroups.com>
<7effe5b9-0eef-4a01-b875-c4ff9f4b3c82n@googlegroups.com> <0cedf97e-b059-4852-803a-015694e93d1dn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <87664531-53b3-439b-8596-8abb60f1f113n@googlegroups.com>
Subject: Re: Question on IOD Tables in revised Part 2
From: markussabin@gmail.com (Markus Sabin)
Injection-Date: Mon, 04 Sep 2023 07:20:22 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Markus Sabin - Mon, 4 Sep 2023 07:20 UTC

Hi Marco,

thank you very much for your thoughts. Sure I could do as you suggest (that was actually my question), but I just wanted to make sure that this extension of the possible values for the "Source" column is fine with the authors of part 2. The new style of part 2 and the DCS is much more formalized than before, so I was hesitant to just extend the list of possible values.
@Jörg Riesmeier: Thank you for your advice, which I followed. But yet I have not received a reply from the WG-31. If I receive any information, I will share it here.

About your question: The Refererenced PPS Sequence (0008,1111) is part of the General Series Module (https://dicom.nema.org/medical/Dicom/2016e/output/chtml/part03/sect_C.7.3.html), hence part of almost any DICOM object to reference the PPS to which the object belongs. It is type 3 in the General Series Module, but an IHE requirement for attribute transfer in SWF.b.

Best,

Markus

Marco Kemper schrieb am Sonntag, 3. September 2023 um 21:36:03 UTC+2:
> Hi Markus,
> [...]
> Marco

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor