Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

An algorithm must be seen to be believed. -- D. E. Knuth


devel / comp.protocols.dicom / Implementation of ImageType (0008,0008) tag

SubjectAuthor
* Implementation of ImageType (0008,0008) tagNick Hobson
`* Re: Implementation of ImageType (0008,0008) tagDavid Gobbi
 +- Re: Implementation of ImageType (0008,0008) tagDavid Gobbi
 `* Re: Implementation of ImageType (0008,0008) tagNick Hobson
  `- Re: Implementation of ImageType (0008,0008) tagrobertvanommen@gmail.com

1
Implementation of ImageType (0008,0008) tag

<55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a37:6c2:0:b0:6a3:4196:5b5f with SMTP id 185-20020a3706c2000000b006a341965b5fmr856953qkg.513.1652970080253;
Thu, 19 May 2022 07:21:20 -0700 (PDT)
X-Received: by 2002:ac8:5ad0:0:b0:2f3:e37a:e768 with SMTP id
d16-20020ac85ad0000000b002f3e37ae768mr3929017qtd.592.1652970080005; Thu, 19
May 2022 07:21:20 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.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, 19 May 2022 07:21:19 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=65.153.178.82; posting-account=fZ4deAoAAAD6ZMDPBFFgLCMfsLXE-gTP
NNTP-Posting-Host: 65.153.178.82
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com>
Subject: Implementation of ImageType (0008,0008) tag
From: nhobson8686@gmail.com (Nick Hobson)
Injection-Date: Thu, 19 May 2022 14:21:20 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2028
 by: Nick Hobson - Thu, 19 May 2022 14:21 UTC

Hi all, I'm looking for more details on the way the ImageType (0008,0008) tag is typically used in PACS implementations.

We take CT images for patient-specific pedicle screw guide design, so require certain specs on those images for quality. One spec we currently reject is this Image Type being anything other than ‘Original\Primary’ due to uncertainty about whether pixel values have changed. I have a sense that ‘Original\Secondary’ images should be usable in at least most if not all cases, since this is most often just going to reflect a pull from PACS rather than direct from scanner, and any post-processing or pixel value changes should change this tag to 'Derived\Secondary', but need a way to determine this with certainty.

Is there anything within the DICOM header that would allow me to make this determination? Or, barring that, something within the documentation of specific PACS implementations?

Re: Implementation of ImageType (0008,0008) tag

<a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:2724:b0:6a0:a446:7023 with SMTP id b36-20020a05620a272400b006a0a4467023mr6378230qkp.286.1653054799019;
Fri, 20 May 2022 06:53:19 -0700 (PDT)
X-Received: by 2002:ac8:5a46:0:b0:2f3:eb45:e465 with SMTP id
o6-20020ac85a46000000b002f3eb45e465mr7770700qta.126.1653054798841; Fri, 20
May 2022 06:53:18 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.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: Fri, 20 May 2022 06:53:18 -0700 (PDT)
In-Reply-To: <55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=198.48.161.196; posting-account=oJk4vAoAAAAuHqwGdLwYUlL776upyWJ3
NNTP-Posting-Host: 198.48.161.196
References: <55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com>
Subject: Re: Implementation of ImageType (0008,0008) tag
From: david.gobbi@gmail.com (David Gobbi)
Injection-Date: Fri, 20 May 2022 13:53:19 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2259
 by: David Gobbi - Fri, 20 May 2022 13:53 UTC

On Thursday, 19 May 2022 at 08:21:21 UTC-6, Nick Hobson wrote:

> I have a sense that ‘Original\Secondary’ images should be usable in at least most if not all cases, since this is most often just going to reflect a pull from PACS rather than direct from scanner, and any post-processing or pixel value changes should change this tag to 'Derived\Secondary'

My understanding is that 'Original\Secondary' usually indicates secondary capture, such as film scans or screen captures of the original. In any case, the ImageType will never change simply because an image is pushed to or pulled from a PACS.

Can you provide additional information about any 'Original\Secondary' images you have encountered? In general, only 'Original\Primary' guarantees that you are getting the original pixel values. Images that are 'Original\Secondary' might have distorted values, additional noise, or lower quality. That doesn't mean they are unsuitable, but it does mean that the primary image is preferable if available.

Re: Implementation of ImageType (0008,0008) tag

<18b38c16-1ecb-4a21-966e-1fcd9292b8afn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:d87:b0:67b:311c:ecbd with SMTP id q7-20020a05620a0d8700b0067b311cecbdmr6445253qkl.146.1653056750174;
Fri, 20 May 2022 07:25:50 -0700 (PDT)
X-Received: by 2002:a05:622a:507:b0:2f3:cde7:bb3a with SMTP id
l7-20020a05622a050700b002f3cde7bb3amr7934744qtx.107.1653056749998; Fri, 20
May 2022 07:25:49 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.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: Fri, 20 May 2022 07:25:49 -0700 (PDT)
In-Reply-To: <a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=198.48.161.196; posting-account=oJk4vAoAAAAuHqwGdLwYUlL776upyWJ3
NNTP-Posting-Host: 198.48.161.196
References: <55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com> <a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <18b38c16-1ecb-4a21-966e-1fcd9292b8afn@googlegroups.com>
Subject: Re: Implementation of ImageType (0008,0008) tag
From: david.gobbi@gmail.com (David Gobbi)
Injection-Date: Fri, 20 May 2022 14:25:50 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1292
 by: David Gobbi - Fri, 20 May 2022 14:25 UTC

Additionally, your 'Original\Secondary' CTs might be MPRs, resampled from the primary.

Re: Implementation of ImageType (0008,0008) tag

<1d3f8416-c26f-453c-b094-381d9b2e81aan@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:188:b0:2f9:1ceb:6a0e with SMTP id s8-20020a05622a018800b002f91ceb6a0emr3206523qtw.285.1653066317015;
Fri, 20 May 2022 10:05:17 -0700 (PDT)
X-Received: by 2002:ad4:5aac:0:b0:461:da84:360c with SMTP id
u12-20020ad45aac000000b00461da84360cmr8850983qvg.103.1653066316809; Fri, 20
May 2022 10:05:16 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.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: Fri, 20 May 2022 10:05:16 -0700 (PDT)
In-Reply-To: <a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=65.153.178.82; posting-account=fZ4deAoAAAD6ZMDPBFFgLCMfsLXE-gTP
NNTP-Posting-Host: 65.153.178.82
References: <55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com> <a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <1d3f8416-c26f-453c-b094-381d9b2e81aan@googlegroups.com>
Subject: Re: Implementation of ImageType (0008,0008) tag
From: nhobson8686@gmail.com (Nick Hobson)
Injection-Date: Fri, 20 May 2022 17:05:17 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3653
 by: Nick Hobson - Fri, 20 May 2022 17:05 UTC

On Friday, May 20, 2022 at 7:53:20 AM UTC-6, david...@gmail.com wrote:
> On Thursday, 19 May 2022 at 08:21:21 UTC-6, Nick Hobson wrote:
>
> > I have a sense that ‘Original\Secondary’ images should be usable in at least most if not all cases, since this is most often just going to reflect a pull from PACS rather than direct from scanner, and any post-processing or pixel value changes should change this tag to 'Derived\Secondary'
> My understanding is that 'Original\Secondary' usually indicates secondary capture, such as film scans or screen captures of the original. In any case, the ImageType will never change simply because an image is pushed to or pulled from a PACS.
>
> Can you provide additional information about any 'Original\Secondary' images you have encountered? In general, only 'Original\Primary' guarantees that you are getting the original pixel values. Images that are 'Original\Secondary' might have distorted values, additional noise, or lower quality. That doesn't mean they are unsuitable, but it does mean that the primary image is preferable if available.

Hi David thanks for the reply. Maybe I need to back up and broaden my question to just what exactly can cause this tag to change from Original\Primary -> Original\Secondary?

My interpretation of the Value 1 'Pixel Characteristics' of this tag was that any pixel value change would be covered by 'Derived' and that the definition for 'Original' (- is the image an ORIGINAL Image; an image whose pixel values are based on original or source data) meant that the pixel values are directly transferred from the original, but I suppose the phrase 'based on' makes this suspect.

As far as I can tell, these are not secondary captures (none of the associated tags present, e.g. Conversion Type or Secondary Capture Device ID) nor MPRs (no relevant tags present there either).

The most consistent thing I'm noticing is that these images usually have been written to physical media (e.g. CD/DVD) - but it doesn't seem to be the case that this always causes the Secondary type either, so maybe I'm wrong in thinking that could be a cause.

Maybe I need to just catch one of these as it comes in and track down the radiology center and try to follow their whole process to see what's causing the change?

Re: Implementation of ImageType (0008,0008) tag

<9efdae2a-fed7-4a2c-a53f-979cb400aa0fn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:620a:46a1:b0:6a0:465e:ccca with SMTP id bq33-20020a05620a46a100b006a0465ecccamr8219481qkb.631.1653114170568;
Fri, 20 May 2022 23:22:50 -0700 (PDT)
X-Received: by 2002:ac8:4e4d:0:b0:2f9:2f21:5868 with SMTP id
e13-20020ac84e4d000000b002f92f215868mr86958qtw.97.1653114170351; Fri, 20 May
2022 23:22:50 -0700 (PDT)
Path: i2pn2.org!rocksolid2!i2pn.org!usenet.blueworldhosting.com!feed1.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: Fri, 20 May 2022 23:22:50 -0700 (PDT)
In-Reply-To: <1d3f8416-c26f-453c-b094-381d9b2e81aan@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=87.213.169.236; posting-account=7V7y7goAAABQ65Zw2wkzIKXUitag5Y9E
NNTP-Posting-Host: 87.213.169.236
References: <55efb3a9-6887-43b4-9320-676940d537ffn@googlegroups.com>
<a4218fac-45fe-4329-990f-be01a81e8a29n@googlegroups.com> <1d3f8416-c26f-453c-b094-381d9b2e81aan@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9efdae2a-fed7-4a2c-a53f-979cb400aa0fn@googlegroups.com>
Subject: Re: Implementation of ImageType (0008,0008) tag
From: robertvanommen@gmail.com (robertvanommen@gmail.com)
Injection-Date: Sat, 21 May 2022 06:22:50 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 1523
 by: robertvanommen@gmail - Sat, 21 May 2022 06:22 UTC

our Canon CT default transversal images are: 0008,0008 ImageType DERIVED\PRIMARY\MPR
so rejecting everything other than ‘Original\Primary’ could lead to rejecting too much.

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor