Message-ID:

To live is always desirable. -- Eleen the Capellan, "Friday's Child", stardate 3498.9

devel / comp.protocols.dicom / Re: Path to follow for incorrect DICOM tags from devices.

Path to follow for incorrect DICOM tags from devices.

<021ac388-936f-4cd2-b344-b9cac6aefd30n@googlegroups.com>

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:ac8:7d0d:0:b0:39c:c5e0:37c0 with SMTP id g13-20020ac87d0d000000b0039cc5e037c0mr19933156qtb.537.1666451299839;
Sat, 22 Oct 2022 08:08:19 -0700 (PDT)
X-Received: by 2002:a05:6830:1dba:b0:662:968:75c0 with SMTP id
z26-20020a0568301dba00b00662096875c0mr9041031oti.158.1666451299435; Sat, 22
Oct 2022 08:08:19 -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: Sat, 22 Oct 2022 08:08:19 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=93.148.224.92; posting-account=IYNuFgoAAAC6IHIB5bZOJYBIwhUsLVsR
NNTP-Posting-Host: 93.148.224.92
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <021ac388-936f-4cd2-b344-b9cac6aefd30n@googlegroups.com>
Subject: Path to follow for incorrect DICOM tags from devices.
From: email@antoniomagni.com (Toni Magni)
Injection-Date: Sat, 22 Oct 2022 15:08:19 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 23

by: Toni Magni - Sat, 22 Oct 2022 15:08 UTC

Hi,

we have images coming into our PACS (Orthanc) from DTX Studio (https://www.dtxtudio.com) of DX and PX images acquired with a ORTHOPANTOMOGRAPH™ OP300, in which the Tag DICOM (0020,0020) Patient Orientation is anatomically incorrect (its always set to L\P, even for lateral/sagittal cephalograms, and panoramic x-rays).

What is the suggested route to follow in situations like this? Report to manufacturer and then patch the DICOM files as they come into the PACS via custom filters/patches on the PACS?

Is there maybe a public database of known DICOM issues of devices where i could post these findings (in addition to letting the manufacturer INSTRUMENTARIUM DENTAL™ know) and query for other issues of our device that i can patch?

Thanks,

--
Toni Magni, BME
Clinical Instructor
Department of Orthodontics
Case Western Reserve University

Re: Path to follow for incorrect DICOM tags from devices.

<a0de5056-f32a-4547-b07a-8614d160a3b3n@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:ae9:d806:0:b0:6f1:15cc:d870 with SMTP id u6-20020ae9d806000000b006f115ccd870mr11365467qkf.114.1666671768310;
Mon, 24 Oct 2022 21:22:48 -0700 (PDT)
X-Received: by 2002:a05:6870:1607:b0:131:dcec:98f6 with SMTP id
b7-20020a056870160700b00131dcec98f6mr21429021oae.162.1666671767897; Mon, 24
Oct 2022 21:22:47 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.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: Mon, 24 Oct 2022 21:22:47 -0700 (PDT)
In-Reply-To: <021ac388-936f-4cd2-b344-b9cac6aefd30n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=73.145.177.109; posting-account=k73DqAkAAADdoksgsJTi6tuONxlkoUr0
NNTP-Posting-Host: 73.145.177.109
References: <021ac388-936f-4cd2-b344-b9cac6aefd30n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <a0de5056-f32a-4547-b07a-8614d160a3b3n@googlegroups.com>
Subject: Re: Path to follow for incorrect DICOM tags from devices.
From: go.chris.bot@gmail.com (Chris O'Donnell)
Injection-Date: Tue, 25 Oct 2022 04:22:48 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2496

by: Chris O'Donnell - Tue, 25 Oct 2022 04:22 UTC

On Saturday, October 22, 2022 at 11:08:21 AM UTC-4, Toni Magni wrote:
> Hi,
>
> we have images coming into our PACS (Orthanc) from DTX Studio (https://www.dtxtudio.com) of DX and PX images acquired with a ORTHOPANTOMOGRAPH™ OP300, in which the Tag DICOM (0020,0020) Patient Orientation is anatomically incorrect (its always set to L\P, even for lateral/sagittal cephalograms, and panoramic x-rays).
>
> What is the suggested route to follow in situations like this? Report to manufacturer and then patch the DICOM files as they come into the PACS via custom filters/patches on the PACS?
>
> Is there maybe a public database of known DICOM issues of devices where i could post these findings (in addition to letting the manufacturer INSTRUMENTARIUM DENTAL™ know) and query for other issues of our device that i can patch?
>
> Thanks,
>
> --
> Toni Magni, BME
> Clinical Instructor
> Department of Orthodontics
> Case Western Reserve University

Report to manufacturer is the best option. If your PACS has some custom patching, then that's good news.

Never heard of a public database of violations, interesting concept but there's some problematic aspects, to say the least.

Re: Path to follow for incorrect DICOM tags from devices.

<9beb9a51-367d-492e-8b4d-86c788c70866n@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:620a:294f:b0:6ee:b598:2625 with SMTP id n15-20020a05620a294f00b006eeb5982625mr26277400qkp.415.1666677783886;
Mon, 24 Oct 2022 23:03:03 -0700 (PDT)
X-Received: by 2002:a05:6870:9722:b0:13b:8822:bf8f with SMTP id
n34-20020a056870972200b0013b8822bf8fmr6789553oaq.195.1666677783208; Mon, 24
Oct 2022 23:03:03 -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: Mon, 24 Oct 2022 23:03:02 -0700 (PDT)
In-Reply-To: <a0de5056-f32a-4547-b07a-8614d160a3b3n@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: <021ac388-936f-4cd2-b344-b9cac6aefd30n@googlegroups.com> <a0de5056-f32a-4547-b07a-8614d160a3b3n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9beb9a51-367d-492e-8b4d-86c788c70866n@googlegroups.com>
Subject: Re: Path to follow for incorrect DICOM tags from devices.
From: mathieu.malaterre@gmail.com (Mathieu Malaterre)
Injection-Date: Tue, 25 Oct 2022 06:03:03 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2735

by: Mathieu Malaterre - Tue, 25 Oct 2022 06:03 UTC

On Tuesday, October 25, 2022 at 6:22:49 AM UTC+2, go.chr...@gmail.com wrote:
> On Saturday, October 22, 2022 at 11:08:21 AM UTC-4, Toni Magni wrote:
> > Hi,
> >
> > we have images coming into our PACS (Orthanc) from DTX Studio (https://www.dtxtudio.com) of DX and PX images acquired with a ORTHOPANTOMOGRAPH™ OP300, in which the Tag DICOM (0020,0020) Patient Orientation is anatomically incorrect (its always set to L\P, even for lateral/sagittal cephalograms, and panoramic x-rays).
> >
> > What is the suggested route to follow in situations like this? Report to manufacturer and then patch the DICOM files as they come into the PACS via custom filters/patches on the PACS?
> >
> > Is there maybe a public database of known DICOM issues of devices where i could post these findings (in addition to letting the manufacturer INSTRUMENTARIUM DENTAL™ know) and query for other issues of our device that i can patch?
> >
> > Thanks,
> >
> > --
> > Toni Magni, BME
> > Clinical Instructor
> > Department of Orthodontics
> > Case Western Reserve University
> Report to manufacturer is the best option. If your PACS has some custom patching, then that's good news.
>
> Never heard of a public database of violations, interesting concept but there's some problematic aspects, to say the least.

Search for "hall of shame" in this newsgroup...

Re: Path to follow for incorrect DICOM tags from devices.

<d4834ca3-20fa-4699-a380-5456a2870c44n@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a0c:9a4e:0:b0:4b1:d537:c6b9 with SMTP id q14-20020a0c9a4e000000b004b1d537c6b9mr37115893qvd.3.1666798979048;
Wed, 26 Oct 2022 08:42:59 -0700 (PDT)
X-Received: by 2002:a05:6870:73c8:b0:132:7be6:8cb0 with SMTP id
a8-20020a05687073c800b001327be68cb0mr2524888oan.47.1666798977814; Wed, 26 Oct
2022 08:42:57 -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: Wed, 26 Oct 2022 08:42:57 -0700 (PDT)
In-Reply-To: <a0de5056-f32a-4547-b07a-8614d160a3b3n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=141.214.125.209; posting-account=Xrp7ygoAAAANK09okVApPRadJPdMPiz2
NNTP-Posting-Host: 141.214.125.209
References: <021ac388-936f-4cd2-b344-b9cac6aefd30n@googlegroups.com> <a0de5056-f32a-4547-b07a-8614d160a3b3n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d4834ca3-20fa-4699-a380-5456a2870c44n@googlegroups.com>
Subject: Re: Path to follow for incorrect DICOM tags from devices.
From: jimirrer@gmail.com (Jim Irrer)
Injection-Date: Wed, 26 Oct 2022 15:42:59 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3216

by: Jim Irrer - Wed, 26 Oct 2022 15:42 UTC

I'm not aware of a "Hall of Shame" (agreed that it's problematic), but the inverse concept of a
sort does exist, a 'Hall of Honor" if you will, of connectathon results:

https://connectathon-results.ihe.net/

Also companies generally provide a conformance statement:

https://dicom.nema.org/medical/dicom/current/output/chtml/part02/chapter_6.html

I also agree that contacting the manufacturer is the proper course of action.

Thanks,

- Jim

Jim Irrer
University of Michigan Hospital Radiation Oncology

On Tuesday, October 25, 2022 at 12:22:49 AM UTC-4, go.chr...@gmail.com wrote:
> On Saturday, October 22, 2022 at 11:08:21 AM UTC-4, Toni Magni wrote:
> > Hi,
> >
> > we have images coming into our PACS (Orthanc) from DTX Studio (https://www.dtxtudio.com) of DX and PX images acquired with a ORTHOPANTOMOGRAPH™ OP300, in which the Tag DICOM (0020,0020) Patient Orientation is anatomically incorrect (its always set to L\P, even for lateral/sagittal cephalograms, and panoramic x-rays).
> >
> > What is the suggested route to follow in situations like this? Report to manufacturer and then patch the DICOM files as they come into the PACS via custom filters/patches on the PACS?
> >
> > Is there maybe a public database of known DICOM issues of devices where i could post these findings (in addition to letting the manufacturer INSTRUMENTARIUM DENTAL™ know) and query for other issues of our device that i can patch?
> >
> > Thanks,
> >
> > --
> > Toni Magni, BME
> > Clinical Instructor
> > Department of Orthodontics
> > Case Western Reserve University
> Report to manufacturer is the best option. If your PACS has some custom patching, then that's good news.
>
> Never heard of a public database of violations, interesting concept but there's some problematic aspects, to say the least.

Subject	Author
Path to follow for incorrect DICOM tags from devices.	Toni Magni
Re: Path to follow for incorrect DICOM tags from devices.	Chris O'Donnell
Re: Path to follow for incorrect DICOM tags from devices.	Mathieu Malaterre
Re: Path to follow for incorrect DICOM tags from devices.	Jim Irrer