Message-ID:

It is not every question that deserves an answer. -- Publilius Syrus

devel / comp.protocols.dicom / Re: Accession Number not coming into PACS

Accession Number not coming into PACS

<f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com>

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a37:a095:: with SMTP id j143mr201946qke.277.1633552846108;
Wed, 06 Oct 2021 13:40:46 -0700 (PDT)
X-Received: by 2002:ac8:7ed2:: with SMTP id x18mr346404qtj.213.1633552845908;
Wed, 06 Oct 2021 13:40:45 -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, 6 Oct 2021 13:40:45 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=24.9.10.150; posting-account=FM-BrQoAAABh0R1L0lYwVjUuEPyfbZbF
NNTP-Posting-Host: 24.9.10.150
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com>
Subject: Accession Number not coming into PACS
From: billlamb62@gmail.com (Bill Lamb)
Injection-Date: Wed, 06 Oct 2021 20:40:46 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 3

by: Bill Lamb - Wed, 6 Oct 2021 20:40 UTC

We have an ultrasound machine that displays the Accession Number when you query the Worklist. When you scan the patient and send the images to the PACS the Accession Number and Description do not come over. What is the reason this is happening?

Thank You,
Bill

Re: Accession Number not coming into PACS

<5a9d724f-91f4-43ed-bbf1-14cfcefafcaan@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:6214:4eb:: with SMTP id cl11mr2528503qvb.43.1633587498015;
Wed, 06 Oct 2021 23:18:18 -0700 (PDT)
X-Received: by 2002:ad4:4203:: with SMTP id k3mr2272796qvp.8.1633587497751;
Wed, 06 Oct 2021 23:18:17 -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, 6 Oct 2021 23:18:17 -0700 (PDT)
In-Reply-To: <f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=212.204.96.130; posting-account=FpWjmwoAAADouxZodjPwb9TZUXzY1wOz
NNTP-Posting-Host: 212.204.96.130
References: <f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5a9d724f-91f4-43ed-bbf1-14cfcefafcaan@googlegroups.com>
Subject: Re: Accession Number not coming into PACS
From: markussabin@gmail.com (Markus Sabin)
Injection-Date: Thu, 07 Oct 2021 06:18:18 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 31

by: Markus Sabin - Thu, 7 Oct 2021 06:18 UTC

Let me make an educated guess.

Our company offers a consulting service for testing DICOM interfaces. Mainly modality manufacturers are doing this with us. Not transferring the Accession Number from worklist results to acquired images is something that we find in almost every project. It seems that there is a very common misconception of what a DICOM type 2 attribute is.

What it is: "You may leave it empty if you do not know a correct value for it" -> explicitly conveying the information "I do not have that information"
How many implementors read it: "You may leave it empty if you want"

Obviously, when the modality receives the Acc# via worklist, it cannot claim not to have the information, but this seems to be easy to miss.

I would bet one box of finest franconian beer (shipping not included) that it is a bug in the modality. :-) If you would like assistance in verifying and obtaining evidence for this, you are welcome to PM me.

Best Regards,

Markus

billl...@gmail.com schrieb am Mittwoch, 6. Oktober 2021 um 22:40:47 UTC+2:
> We have an ultrasound machine that displays the Accession Number when you query the Worklist. When you scan the patient and send the images to the PACS the Accession Number and Description do not come over. What is the reason this is happening?
>
> Thank You,
> Bill

Re: Accession Number not coming into PACS

<b877e8cd-f343-406b-8ad0-7ba766a06335n@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:6214:1083:: with SMTP id o3mr4607140qvr.57.1633619399938;
Thu, 07 Oct 2021 08:09:59 -0700 (PDT)
X-Received: by 2002:ac8:5705:: with SMTP id 5mr2857693qtw.184.1633619399711;
Thu, 07 Oct 2021 08:09:59 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!border1.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: Thu, 7 Oct 2021 08:09:59 -0700 (PDT)
In-Reply-To: <5a9d724f-91f4-43ed-bbf1-14cfcefafcaan@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:282:8301:bf40:9c13:2d63:3e40:fb26;
posting-account=FM-BrQoAAABh0R1L0lYwVjUuEPyfbZbF
NNTP-Posting-Host: 2601:282:8301:bf40:9c13:2d63:3e40:fb26
References: <f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com> <5a9d724f-91f4-43ed-bbf1-14cfcefafcaan@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b877e8cd-f343-406b-8ad0-7ba766a06335n@googlegroups.com>
Subject: Re: Accession Number not coming into PACS
From: billlamb62@gmail.com (Bill Lamb)
Injection-Date: Thu, 07 Oct 2021 15:09:59 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 36

by: Bill Lamb - Thu, 7 Oct 2021 15:09 UTC

On Thursday, October 7, 2021 at 12:18:19 AM UTC-6, marku...@gmail.com wrote:
> Let me make an educated guess.
>
> Our company offers a consulting service for testing DICOM interfaces. Mainly modality manufacturers are doing this with us. Not transferring the Accession Number from worklist results to acquired images is something that we find in almost every project. It seems that there is a very common misconception of what a DICOM type 2 attribute is.
>
> What it is: "You may leave it empty if you do not know a correct value for it" -> explicitly conveying the information "I do not have that information"
> How many implementors read it: "You may leave it empty if you want"
>
> Obviously, when the modality receives the Acc# via worklist, it cannot claim not to have the information, but this seems to be easy to miss.
>
> I would bet one box of finest franconian beer (shipping not included) that it is a bug in the modality. :-) If you would like assistance in verifying and obtaining evidence for this, you are welcome to PM me.
>
> Best Regards,
>
> Markus
> billl...@gmail.com schrieb am Mittwoch, 6. Oktober 2021 um 22:40:47 UTC+2:
> > We have an ultrasound machine that displays the Accession Number when you query the Worklist. When you scan the patient and send the images to the PACS the Accession Number and Description do not come over. What is the reason this is happening?
> >
> > Thank You,
> > Bill
Can you tell me how we can fix the problem. It seems as though it is not using the Study UID from the worklist, but the ultrasound is creating it's own UID, therefore the Accession Number is not coming over.

Re: Accession Number not coming into PACS

<ea061849-12ba-44fd-b318-15789e4145b0n@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a37:bb86:: with SMTP id l128mr3928156qkf.411.1633621547875;
Thu, 07 Oct 2021 08:45:47 -0700 (PDT)
X-Received: by 2002:aed:27cc:: with SMTP id m12mr3932146qtg.253.1633621547678;
Thu, 07 Oct 2021 08:45:47 -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: Thu, 7 Oct 2021 08:45:47 -0700 (PDT)
In-Reply-To: <b877e8cd-f343-406b-8ad0-7ba766a06335n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:282:8301:bf40:9c13:2d63:3e40:fb26;
posting-account=FM-BrQoAAABh0R1L0lYwVjUuEPyfbZbF
NNTP-Posting-Host: 2601:282:8301:bf40:9c13:2d63:3e40:fb26
References: <f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com>
<5a9d724f-91f4-43ed-bbf1-14cfcefafcaan@googlegroups.com> <b877e8cd-f343-406b-8ad0-7ba766a06335n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ea061849-12ba-44fd-b318-15789e4145b0n@googlegroups.com>
Subject: Re: Accession Number not coming into PACS
From: billlamb62@gmail.com (Bill Lamb)
Injection-Date: Thu, 07 Oct 2021 15:45:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

by: Bill Lamb - Thu, 7 Oct 2021 15:45 UTC

On Thursday, October 7, 2021 at 9:10:01 AM UTC-6, Bill Lamb wrote:
> On Thursday, October 7, 2021 at 12:18:19 AM UTC-6, marku...@gmail.com wrote:
> > Let me make an educated guess.
> >
> > Our company offers a consulting service for testing DICOM interfaces. Mainly modality manufacturers are doing this with us. Not transferring the Accession Number from worklist results to acquired images is something that we find in almost every project. It seems that there is a very common misconception of what a DICOM type 2 attribute is.
> >
> > What it is: "You may leave it empty if you do not know a correct value for it" -> explicitly conveying the information "I do not have that information"
> > How many implementors read it: "You may leave it empty if you want"
> >
> > Obviously, when the modality receives the Acc# via worklist, it cannot claim not to have the information, but this seems to be easy to miss.
> >
> > I would bet one box of finest franconian beer (shipping not included) that it is a bug in the modality. :-) If you would like assistance in verifying and obtaining evidence for this, you are welcome to PM me.
> >
> > Best Regards,
> >
> > Markus
> > billl...@gmail.com schrieb am Mittwoch, 6. Oktober 2021 um 22:40:47 UTC+2:
> > > We have an ultrasound machine that displays the Accession Number when you query the Worklist. When you scan the patient and send the images to the PACS the Accession Number and Description do not come over. What is the reason this is happening?
> > >
> > > Thank You,
> > > Bill
> Can you tell me how we can fix the problem. It seems as though it is not using the Study UID from the worklist, but the ultrasound is creating it's own UID, therefore the Accession Number is not coming over.
The Images are now coming over with the Accession Number since the Manufacturer did a software upgrade to the machine. The images are coming over with a green background and pink images. Is this a Compression issue.

Re: Accession Number not coming into PACS

<9c0e6b92-553a-4b3e-8ce6-f0b138d2b69cn@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:622a:283:: with SMTP id z3mr6292899qtw.324.1633626488572;
Thu, 07 Oct 2021 10:08:08 -0700 (PDT)
X-Received: by 2002:a37:43d8:: with SMTP id q207mr4325239qka.476.1633626488341;
Thu, 07 Oct 2021 10:08:08 -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: Thu, 7 Oct 2021 10:08:08 -0700 (PDT)
In-Reply-To: <ea061849-12ba-44fd-b318-15789e4145b0n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:282:8301:bf40:9c13:2d63:3e40:fb26;
posting-account=FM-BrQoAAABh0R1L0lYwVjUuEPyfbZbF
NNTP-Posting-Host: 2601:282:8301:bf40:9c13:2d63:3e40:fb26
References: <f7736af0-262d-4c24-b3f5-af21da6f3550n@googlegroups.com>
<5a9d724f-91f4-43ed-bbf1-14cfcefafcaan@googlegroups.com> <b877e8cd-f343-406b-8ad0-7ba766a06335n@googlegroups.com>
<ea061849-12ba-44fd-b318-15789e4145b0n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9c0e6b92-553a-4b3e-8ce6-f0b138d2b69cn@googlegroups.com>
Subject: Re: Accession Number not coming into PACS
From: billlamb62@gmail.com (Bill Lamb)
Injection-Date: Thu, 07 Oct 2021 17:08:08 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 44

by: Bill Lamb - Thu, 7 Oct 2021 17:08 UTC

On Thursday, October 7, 2021 at 9:45:49 AM UTC-6, Bill Lamb wrote:
> On Thursday, October 7, 2021 at 9:10:01 AM UTC-6, Bill Lamb wrote:
> > On Thursday, October 7, 2021 at 12:18:19 AM UTC-6, marku...@gmail.com wrote:
> > > Let me make an educated guess.
> > >
> > > Our company offers a consulting service for testing DICOM interfaces. Mainly modality manufacturers are doing this with us. Not transferring the Accession Number from worklist results to acquired images is something that we find in almost every project. It seems that there is a very common misconception of what a DICOM type 2 attribute is.
> > >
> > > What it is: "You may leave it empty if you do not know a correct value for it" -> explicitly conveying the information "I do not have that information"
> > > How many implementors read it: "You may leave it empty if you want"
> > >
> > > Obviously, when the modality receives the Acc# via worklist, it cannot claim not to have the information, but this seems to be easy to miss.
> > >
> > > I would bet one box of finest franconian beer (shipping not included) that it is a bug in the modality. :-) If you would like assistance in verifying and obtaining evidence for this, you are welcome to PM me.
> > >
> > > Best Regards,
> > >
> > > Markus
> > > billl...@gmail.com schrieb am Mittwoch, 6. Oktober 2021 um 22:40:47 UTC+2:
> > > > We have an ultrasound machine that displays the Accession Number when you query the Worklist. When you scan the patient and send the images to the PACS the Accession Number and Description do not come over. What is the reason this is happening?
> > > >
> > > > Thank You,
> > > > Bill
> > Can you tell me how we can fix the problem. It seems as though it is not using the Study UID from the worklist, but the ultrasound is creating it's own UID, therefore the Accession Number is not coming over.
> The Images are now coming over with the Accession Number since the Manufacturer did a software upgrade to the machine. The images are coming over with a green background and pink images. Is this a Compression issue.
I changed the compression to uncompressed and the images come over just fine.

Subject	Author
Accession Number not coming into PACS	Bill Lamb
Re: Accession Number not coming into PACS	Markus Sabin
Re: Accession Number not coming into PACS	Bill Lamb
Re: Accession Number not coming into PACS	Bill Lamb
Re: Accession Number not coming into PACS	Bill Lamb