Rocksolid Light

Welcome to Rocksolid Light

mail  files  register  newsreader  groups  login

Message-ID:  

Houston, Tranquillity Base here. The Eagle has landed. -- Neil Armstrong

devel / comp.protocols.dicom / MWL C-FIND and timezones

SubjectAuthor
* MWL C-FIND and timezonesAlon Dolev
+* MWL C-FIND and timezonesRoni Zaharia
|`- MWL C-FIND and timezonesAlon Dolev
`* MWL C-FIND and timezonesMathieu Malaterre
 `- MWL C-FIND and timezonesAlon Dolev

1
MWL C-FIND and timezones

<7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:1713:b0:403:b888:fa29 with SMTP id h19-20020a05622a171300b00403b888fa29mr82093qtk.0.1689671305847;
Tue, 18 Jul 2023 02:08:25 -0700 (PDT)
X-Received: by 2002:a05:6808:1514:b0:3a4:14c1:20f5 with SMTP id
u20-20020a056808151400b003a414c120f5mr21630125oiw.6.1689671305461; Tue, 18
Jul 2023 02:08:25 -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, 18 Jul 2023 02:08:25 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=212.126.160.62; posting-account=bNHBAQoAAABiqgeSSCTRr3hH5CWb1OUI
NNTP-Posting-Host: 212.126.160.62
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com>
Subject: MWL C-FIND and timezones
From: alon.dolev@positrigo.com (Alon Dolev)
Injection-Date: Tue, 18 Jul 2023 09:08:25 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Alon Dolev - Tue, 18 Jul 2023 09:08 UTC

Dear group,

We are implementing a modality that does C-FIND requests to get modaliy worklist items. We use a range matching on the scheduled procedure step start date, and scheduled procedure step start time. In our system all times are handled in UTC, and we would like to commuciate with the PACS in UTC as well. It is unclear to us how we should go about that. This is what we have discovered

- We can set Timezone Offset From UTC on the C-FIND request root dataset to +0000, but we are not sure if this means that the time we are sending is in UTC, or that the time we would like to receive is going to be in UTC, or maybe even both?
- There is an extended negotiation that we can do which is called Timezone query adjustment, but we are not sure how it is related to the mechanisms described above, as our tests PACS (dcm4chee) does not seem to behave differently when this is turned on or off, or maybe we are doing something wrong?

We are starting to suspect that timezone handling is not well supported in todays PACS, and that we might better not rely on it. Does anybody have input on tha

Any answer, however short, will be greatly appreciated.

Best regards,

Alon

Re: MWL C-FIND and timezones

<1dfcaf1a-ab46-426c-a12c-0f02ea7a88e9n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:8783:b0:767:b47b:1451 with SMTP id py3-20020a05620a878300b00767b47b1451mr10363qkn.0.1690296252723;
Tue, 25 Jul 2023 07:44:12 -0700 (PDT)
X-Received: by 2002:a05:6808:1528:b0:3a3:7087:bbfb with SMTP id
u40-20020a056808152800b003a37087bbfbmr26687703oiw.6.1690296252424; Tue, 25
Jul 2023 07:44:12 -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, 25 Jul 2023 07:44:12 -0700 (PDT)
In-Reply-To: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a0d:6fc2:5d50:2800:80cf:da06:d92d:c6f4;
posting-account=nyGQKwoAAADiQvjoalqMT41R4ZphCL9Q
NNTP-Posting-Host: 2a0d:6fc2:5d50:2800:80cf:da06:d92d:c6f4
References: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <1dfcaf1a-ab46-426c-a12c-0f02ea7a88e9n@googlegroups.com>
Subject: Re: MWL C-FIND and timezones
From: roni@hrzkit.com (Roni Zaharia)
Injection-Date: Tue, 25 Jul 2023 14:44:12 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Roni Zaharia - Tue, 25 Jul 2023 14:44 UTC

On Tuesday, July 18, 2023 at 12:08:27 PM UTC+3, Alon Dolev wrote:
> Dear group,
>
> We are implementing a modality that does C-FIND requests to get modaliy worklist items. We use a range matching on the scheduled procedure step start date, and scheduled procedure step start time. In our system all times are handled in UTC, and we would like to commuciate with the PACS in UTC as well. It is unclear to us how we should go about that. This is what we have discovered
>
> - We can set Timezone Offset From UTC on the C-FIND request root dataset to +0000, but we are not sure if this means that the time we are sending is in UTC, or that the time we would like to receive is going to be in UTC, or maybe even both?
> - There is an extended negotiation that we can do which is called Timezone query adjustment, but we are not sure how it is related to the mechanisms described above, as our tests PACS (dcm4chee) does not seem to behave differently when this is turned on or off, or maybe we are doing something wrong?
>
> We are starting to suspect that timezone handling is not well supported in todays PACS, and that we might better not rely on it. Does anybody have input on tha
>
> Any answer, however short, will be greatly appreciated.
>
> Best regards,
>
> Alon
Hi Alon,
Very rare. In general you should relay only on the mandatory most basic implementation and even then reserve space for vendor specific discounts. DICOM is an open standard. There're many implementations each making their own interpretation of the standard just like you do.
Roni

Re: MWL C-FIND and timezones

<dd7dc51b-426b-46e2-aa85-5b044d94c3c3n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:1a03:b0:403:27b2:85b5 with SMTP id f3-20020a05622a1a0300b0040327b285b5mr10794qtb.12.1690299558587;
Tue, 25 Jul 2023 08:39:18 -0700 (PDT)
X-Received: by 2002:a05:6870:7685:b0:1bb:8e01:eb8f with SMTP id
dx5-20020a056870768500b001bb8e01eb8fmr5057482oab.0.1690299558298; Tue, 25 Jul
2023 08:39:18 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.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: Tue, 25 Jul 2023 08:39:17 -0700 (PDT)
In-Reply-To: <1dfcaf1a-ab46-426c-a12c-0f02ea7a88e9n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=212.126.160.62; posting-account=bNHBAQoAAABiqgeSSCTRr3hH5CWb1OUI
NNTP-Posting-Host: 212.126.160.62
References: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com> <1dfcaf1a-ab46-426c-a12c-0f02ea7a88e9n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <dd7dc51b-426b-46e2-aa85-5b044d94c3c3n@googlegroups.com>
Subject: Re: MWL C-FIND and timezones
From: alon.dolev@positrigo.com (Alon Dolev)
Injection-Date: Tue, 25 Jul 2023 15:39:18 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3079
 by: Alon Dolev - Tue, 25 Jul 2023 15:39 UTC

Thank you Roni for your reply. Very helpful. Alon

On Tuesday, July 25, 2023 at 4:44:14 PM UTC+2, Roni Zaharia wrote:
> On Tuesday, July 18, 2023 at 12:08:27 PM UTC+3, Alon Dolev wrote:
> > Dear group,
> >
> > We are implementing a modality that does C-FIND requests to get modaliy worklist items. We use a range matching on the scheduled procedure step start date, and scheduled procedure step start time. In our system all times are handled in UTC, and we would like to commuciate with the PACS in UTC as well. It is unclear to us how we should go about that. This is what we have discovered
> >
> > - We can set Timezone Offset From UTC on the C-FIND request root dataset to +0000, but we are not sure if this means that the time we are sending is in UTC, or that the time we would like to receive is going to be in UTC, or maybe even both?
> > - There is an extended negotiation that we can do which is called Timezone query adjustment, but we are not sure how it is related to the mechanisms described above, as our tests PACS (dcm4chee) does not seem to behave differently when this is turned on or off, or maybe we are doing something wrong?
> >
> > We are starting to suspect that timezone handling is not well supported in todays PACS, and that we might better not rely on it. Does anybody have input on tha
> >
> > Any answer, however short, will be greatly appreciated.
> >
> > Best regards,
> >
> > Alon
> Hi Alon,
> Very rare. In general you should relay only on the mandatory most basic implementation and even then reserve space for vendor specific discounts. DICOM is an open standard. There're many implementations each making their own interpretation of the standard just like you do.
> Roni

Re: MWL C-FIND and timezones

<4e5535d7-5eb8-4c89-b89f-2547acf0955bn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:6214:b28:b0:63c:ef89:1a5e with SMTP id w8-20020a0562140b2800b0063cef891a5emr7390qvj.0.1690352428494;
Tue, 25 Jul 2023 23:20:28 -0700 (PDT)
X-Received: by 2002:ad4:4e74:0:b0:63c:f952:2d0e with SMTP id
ec20-20020ad44e74000000b0063cf9522d0emr3536qvb.2.1690352428118; Tue, 25 Jul
2023 23:20:28 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.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, 25 Jul 2023 23:20:27 -0700 (PDT)
In-Reply-To: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=91.173.12.104; posting-account=5syELgoAAABMLWsjbxhk8Wo7CLxGgTPG
NNTP-Posting-Host: 91.173.12.104
References: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4e5535d7-5eb8-4c89-b89f-2547acf0955bn@googlegroups.com>
Subject: Re: MWL C-FIND and timezones
From: mathieu.malaterre@gmail.com (Mathieu Malaterre)
Injection-Date: Wed, 26 Jul 2023 06:20:28 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 31
 by: Mathieu Malaterre - Wed, 26 Jul 2023 06:20 UTC

On Tuesday, July 18, 2023 at 11:08:27 AM UTC+2, Alon Dolev wrote:
> Dear group,
>
> We are implementing a modality that does C-FIND requests to get modaliy worklist items. We use a range matching on the scheduled procedure step start date, and scheduled procedure step start time. In our system all times are handled in UTC, and we would like to commuciate with the PACS in UTC as well. It is unclear to us how we should go about that. This is what we have discovered
>
> - We can set Timezone Offset From UTC on the C-FIND request root dataset to +0000, but we are not sure if this means that the time we are sending is in UTC, or that the time we would like to receive is going to be in UTC, or maybe even both?
> - There is an extended negotiation that we can do which is called Timezone query adjustment, but we are not sure how it is related to the mechanisms described above, as our tests PACS (dcm4chee) does not seem to behave differently when this is turned on or off, or maybe we are doing something wrong?
>
> We are starting to suspect that timezone handling is not well supported in todays PACS, and that we might better not rely on it. Does anybody have input on tha
>
> Any answer, however short, will be greatly appreciated.

If you have not found them yet, did you check:

* https://groups.google.com/g/comp.protocols.dicom/c/MMca_hurWOM/m/z0zC1_MPAwAJ
* https://groups.google.com/g/comp.protocols.dicom/c/-skycy7S-e4/m/aFj4noY8dk0J

Re: MWL C-FIND and timezones

<b529bbb3-3f36-4af8-b2d0-e3b3b17de2dcn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:28c2:b0:767:fe53:3691 with SMTP id l2-20020a05620a28c200b00767fe533691mr162247qkp.3.1691062574867;
Thu, 03 Aug 2023 04:36:14 -0700 (PDT)
X-Received: by 2002:a9d:6451:0:b0:6b9:667a:7211 with SMTP id
m17-20020a9d6451000000b006b9667a7211mr17790810otl.4.1691062574452; Thu, 03
Aug 2023 04:36:14 -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: Thu, 3 Aug 2023 04:36:14 -0700 (PDT)
In-Reply-To: <4e5535d7-5eb8-4c89-b89f-2547acf0955bn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=212.126.160.62; posting-account=bNHBAQoAAABiqgeSSCTRr3hH5CWb1OUI
NNTP-Posting-Host: 212.126.160.62
References: <7634e86d-da0f-41ee-bdb4-b388b9e2b69cn@googlegroups.com> <4e5535d7-5eb8-4c89-b89f-2547acf0955bn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b529bbb3-3f36-4af8-b2d0-e3b3b17de2dcn@googlegroups.com>
Subject: Re: MWL C-FIND and timezones
From: alon.dolev@positrigo.com (Alon Dolev)
Injection-Date: Thu, 03 Aug 2023 11:36:14 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2953
 by: Alon Dolev - Thu, 3 Aug 2023 11:36 UTC

Thank you very much Mathieu for the links.

On Wednesday, July 26, 2023 at 8:20:30 AM UTC+2, Mathieu Malaterre wrote:
> On Tuesday, July 18, 2023 at 11:08:27 AM UTC+2, Alon Dolev wrote:
> > Dear group,
> >
> > We are implementing a modality that does C-FIND requests to get modaliy worklist items. We use a range matching on the scheduled procedure step start date, and scheduled procedure step start time. In our system all times are handled in UTC, and we would like to commuciate with the PACS in UTC as well. It is unclear to us how we should go about that. This is what we have discovered
> >
> > - We can set Timezone Offset From UTC on the C-FIND request root dataset to +0000, but we are not sure if this means that the time we are sending is in UTC, or that the time we would like to receive is going to be in UTC, or maybe even both?
> > - There is an extended negotiation that we can do which is called Timezone query adjustment, but we are not sure how it is related to the mechanisms described above, as our tests PACS (dcm4chee) does not seem to behave differently when this is turned on or off, or maybe we are doing something wrong?
> >
> > We are starting to suspect that timezone handling is not well supported in todays PACS, and that we might better not rely on it. Does anybody have input on tha
> >
> > Any answer, however short, will be greatly appreciated.
> If you have not found them yet, did you check:
>
> * https://groups.google.com/g/comp.protocols.dicom/c/MMca_hurWOM/m/z0zC1_MPAwAJ
> * https://groups.google.com/g/comp.protocols.dicom/c/-skycy7S-e4/m/aFj4noY8dk0J

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor