Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

If you can't understand it, it is intuitively obvious.


devel / comp.protocols.dicom / Re: Best practice to implement SNOMED CT in DICOM Structured Reports

SubjectAuthor
* Best practice to implement SNOMED CT in DICOM Structured ReportsJohannes Bretscher
`- Re: Best practice to implement SNOMED CT in DICOM Structured ReportsAndrey Fedorov

1
Best practice to implement SNOMED CT in DICOM Structured Reports

<c28d6f02-cbbb-4e75-8d3f-427e9cbcd1f4n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:6214:29ed:b0:4ac:85f8:851 with SMTP id jv13-20020a05621429ed00b004ac85f80851mr2941920qvb.3.1662713732652;
Fri, 09 Sep 2022 01:55:32 -0700 (PDT)
X-Received: by 2002:a05:6808:1313:b0:344:973a:3669 with SMTP id
y19-20020a056808131300b00344973a3669mr2999903oiv.175.1662713732405; Fri, 09
Sep 2022 01:55:32 -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: Fri, 9 Sep 2022 01:55:32 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=91.196.200.15; posting-account=p0NeJQoAAAD6MTIDBhRjE6QnrANyvrnO
NNTP-Posting-Host: 91.196.200.15
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c28d6f02-cbbb-4e75-8d3f-427e9cbcd1f4n@googlegroups.com>
Subject: Best practice to implement SNOMED CT in DICOM Structured Reports
From: johannes.bretscher@airamed.de (Johannes Bretscher)
Injection-Date: Fri, 09 Sep 2022 08:55:32 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 1837
 by: Johannes Bretscher - Fri, 9 Sep 2022 08:55 UTC

I have an application that uses DICOM as communication interface. To report results of calculated measurements I need to use an internationally accepted standard and decided on SNOMED CT. Now, are there some best practices to implement SNOMED CT in a DICOM Structured Report? For example, I have the volume of a brain region which might be

439749006 |Volume of structure by imaging measurement|:
363698007|finding site|=4958002 |Amygdaloid structure|,
767525000 |Unit|=258773002 |Milliliter|

And then somehow the actual measurement added. Are there experiences, best practices or similar to organise a series of measurements like that and other measurements I make, like lesion counts, in a DICOM Structured Report?

Re: Best practice to implement SNOMED CT in DICOM Structured Reports

<fcb99d33-bf25-4806-ab4d-6c582e542abdn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:58ca:0:b0:344:5cbe:4c9a with SMTP id u10-20020ac858ca000000b003445cbe4c9amr14728133qta.36.1662780565854;
Fri, 09 Sep 2022 20:29:25 -0700 (PDT)
X-Received: by 2002:a05:6870:40cc:b0:126:ddb9:55e8 with SMTP id
l12-20020a05687040cc00b00126ddb955e8mr6729505oal.281.1662780565450; Fri, 09
Sep 2022 20:29:25 -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: Fri, 9 Sep 2022 20:29:25 -0700 (PDT)
In-Reply-To: <c28d6f02-cbbb-4e75-8d3f-427e9cbcd1f4n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=173.48.76.65; posting-account=HItBBgoAAABRvKHgQ0-cHJqH2Lj570Je
NNTP-Posting-Host: 173.48.76.65
References: <c28d6f02-cbbb-4e75-8d3f-427e9cbcd1f4n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <fcb99d33-bf25-4806-ab4d-6c582e542abdn@googlegroups.com>
Subject: Re: Best practice to implement SNOMED CT in DICOM Structured Reports
From: andrey.fedorov@gmail.com (Andrey Fedorov)
Injection-Date: Sat, 10 Sep 2022 03:29:25 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 36
 by: Andrey Fedorov - Sat, 10 Sep 2022 03:29 UTC

We presented some initial work in this direction in this manuscript: https://peerj.com/articles/2057/, which followed by this library that can be helpful in creating such SRs: https://github.com/QIICR/dcmqi.

dcmqi works for saving volumetric measurements defined over segmentations. highdicom is a python library that is more flexible in that regard supporting a broad range of measurements over planar annotations: https://github.com/herrmannlab/highdicom.

NCI Imaging Data Commons contains collections that are accompanied by measurement saved as SRs (although I believe all of those are for regions defined by segmentations): https://imaging.datacommons.cancer.gov/explore/, including the collections described here: https://aapm.onlinelibrary.wiley.com/doi/full/10.1002/mp.14445 and here: https://www.nature.com/articles/s41598-019-45766-z.

Those publications, examples and tools should be helpful, but if you have more specific questions, please let us know!

Andrey

On Friday, September 9, 2022 at 4:55:34 AM UTC-4, johannes....@airamed.de wrote:
> I have an application that uses DICOM as communication interface. To report results of calculated measurements I need to use an internationally accepted standard and decided on SNOMED CT. Now, are there some best practices to implement SNOMED CT in a DICOM Structured Report? For example, I have the volume of a brain region which might be
>
> 439749006 |Volume of structure by imaging measurement|:
> 363698007|finding site|=4958002 |Amygdaloid structure|,
> 767525000 |Unit|=258773002 |Milliliter|
>
> And then somehow the actual measurement added. Are there experiences, best practices or similar to organise a series of measurements like that and other measurements I make, like lesion counts, in a DICOM Structured Report?

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor