RetroBBS - comp.protocols.dicom - Re: How are different DICOM files linked in a patient data structure

How are different DICOM files linked in a patient data structure

<b5ec566d-ad40-4b7a-ace3-6582d9ae5bb3n@googlegroups.com>

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:622a:18d:b0:31f:e8e:4660 with SMTP id s13-20020a05622a018d00b0031f0e8e4660mr22522469qtw.176.1659002479305;
Thu, 28 Jul 2022 03:01:19 -0700 (PDT)
X-Received: by 2002:a9d:7ac6:0:b0:61d:1a12:fd93 with SMTP id
m6-20020a9d7ac6000000b0061d1a12fd93mr2582826otn.65.1659002479032; Thu, 28 Jul
2022 03:01:19 -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: Thu, 28 Jul 2022 03:01:18 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=2a00:23c8:3f08:d901:9985:6682:7b52:28e9;
posting-account=PIOFvQoAAAAxCiTK2CzT5qiPaQnkGUTt
NNTP-Posting-Host: 2a00:23c8:3f08:d901:9985:6682:7b52:28e9
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b5ec566d-ad40-4b7a-ace3-6582d9ae5bb3n@googlegroups.com>
Subject: How are different DICOM files linked in a patient data structure
From: monvilleedelweiss@gmail.com (Edelweiss Monville)
Injection-Date: Thu, 28 Jul 2022 10:01:19 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1580

by: Edelweiss Monville - Thu, 28 Jul 2022 10:01 UTC

I would like to connect with developers dealing with DICOM files.
I would like to know which DICOM tag/attribute contains the link to other DICOM files that are part of a patient data structure.
For example, there is a relationship between a patient's CT scan and the RT Structure-Set built on it.
The two DICOM files should share the frame of reference.
Which DICOM tag contains the shared frame of reference in the CT Dicom file and the RTSTRUCT DICOM file?
Thank you so much
Maura

Re: How are different DICOM files linked in a patient data structure

<b4b5bb4e-24ff-4cee-b869-6b94ee28448cn@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:6214:d4f:b0:474:2b0:ee25 with SMTP id 15-20020a0562140d4f00b0047402b0ee25mr2951857qvr.78.1659094635700;
Fri, 29 Jul 2022 04:37:15 -0700 (PDT)
X-Received: by 2002:a05:6808:1642:b0:331:567c:54e1 with SMTP id
az2-20020a056808164200b00331567c54e1mr1317080oib.232.1659094635406; Fri, 29
Jul 2022 04:37:15 -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, 29 Jul 2022 04:37:15 -0700 (PDT)
In-Reply-To: <b5ec566d-ad40-4b7a-ace3-6582d9ae5bb3n@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: <b5ec566d-ad40-4b7a-ace3-6582d9ae5bb3n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b4b5bb4e-24ff-4cee-b869-6b94ee28448cn@googlegroups.com>
Subject: Re: How are different DICOM files linked in a patient data structure
From: jimirrer@gmail.com (Jim Irrer)
Injection-Date: Fri, 29 Jul 2022 11:37:15 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 4236

by: Jim Irrer - Fri, 29 Jul 2022 11:37 UTC

On Thursday, July 28, 2022 at 6:01:20 AM UTC-4, monville... at gmail.com wrote:
> I would like to connect with developers dealing with DICOM files.
>
> I would like to know which DICOM tag/attribute contains the link to other DICOM files that are part of a patient data structure.
> For example, there is a relationship between a patient's CT scan and the RT Structure-Set built on it.
> The two DICOM files should share the frame of reference.
> Which DICOM tag contains the shared frame of reference in the CT Dicom file and the RTSTRUCT DICOM file?
> Thank you so much
> Maura

Maura -

The CT defines a frame of reference, and the RTSTRUCT uses it. They are explicitly linked using the FrameOfReferenceUID, as in:

0020,0052 FrameOfReferenceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.3

Refer to: https://dicom.innolitics.com/ciods/ct-image/frame-of-reference/00200052

The RTSTRUCT file also references the individual CT slice SOPInstanceUIDs. Below is the relevant portion of the metadata from
an RTSTRUCT file. Hope this helps:

3006,0009 StructureSetTime : 072025
3006,0010 ReferencedFrameOfReferenceSequence :
Item: 1 / 1
0020,0052 FrameOfReferenceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.3
3006,0012 RTReferencedStudySequence :
Item: 1 / 1
0008,1150 ReferencedSOPClassUID : 1.2.840.10008.3.1.2.3.2
0008,1155 ReferencedSOPInstanceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.1
3006,0014 RTReferencedSeriesSequence :
Item: 1 / 1
0020,000E SeriesInstanceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.4
3006,0016 ContourImageSequence :
Item: 1 / 315
0008,1150 ReferencedSOPClassUID : 1.2.840.10008.5.1.4.1.1.2 (CT Image Storage)
0008,1155 ReferencedSOPInstanceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.5
Item: 2 / 315
0008,1150 ReferencedSOPClassUID : 1.2.840.10008.5.1.4.1.1.2 (CT Image Storage)
0008,1155 ReferencedSOPInstanceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.6
Item: 3 / 315
0008,1150 ReferencedSOPClassUID : 1.2.840.10008.5.1.4.1.1.2 (CT Image Storage)
0008,1155 ReferencedSOPInstanceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.7
Item: 4 / 315
0008,1150 ReferencedSOPClassUID : 1.2.840.10008.5.1.4.1.1.2 (CT Image Storage)
0008,1155 ReferencedSOPInstanceUID : 1.3.6.1.4.1.22361.17483843774714.95164608.1659093688971.8
.
.
.

Re: How are different DICOM files linked in a patient data structure

<825a8b62-a28e-4857-8288-e2f1c2d984edn@googlegroups.com>

copy mid

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

copy link Newsgroups: comp.protocols.dicom

X-Received: by 2002:a05:620a:2909:b0:6b6:a94:a988 with SMTP id m9-20020a05620a290900b006b60a94a988mr2647139qkp.350.1659099708219;
Fri, 29 Jul 2022 06:01:48 -0700 (PDT)
X-Received: by 2002:a05:6808:124d:b0:325:788d:e23d with SMTP id
o13-20020a056808124d00b00325788de23dmr1613194oiv.267.1659099706613; Fri, 29
Jul 2022 06:01:46 -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, 29 Jul 2022 06:01:46 -0700 (PDT)
In-Reply-To: <b5ec566d-ad40-4b7a-ace3-6582d9ae5bb3n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=108.168.21.130; posting-account=qLZeeAoAAAAVcal4IxtRDM9GcvA-u_4g
NNTP-Posting-Host: 108.168.21.130
References: <b5ec566d-ad40-4b7a-ace3-6582d9ae5bb3n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <825a8b62-a28e-4857-8288-e2f1c2d984edn@googlegroups.com>
Subject: Re: How are different DICOM files linked in a patient data structure
From: darcymason@gmail.com (Darcy Mason)
Injection-Date: Fri, 29 Jul 2022 13:01:48 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 1348

by: Darcy Mason - Fri, 29 Jul 2022 13:01 UTC

"They ought to make butt-flavored cat food." --Gallagher

devel / comp.protocols.dicom / Re: How are different DICOM files linked in a patient data structure

Subject	Author
How are different DICOM files linked in a patient data structure	Edelweiss Monville
Re: How are different DICOM files linked in a patient data structure	Jim Irrer
Re: How are different DICOM files linked in a patient data structure	Darcy Mason