| Re: Constructiuon of SOP instance [message #52300] |
Sun, 28 January 2007 21:36  |
Paul Sommer
Messages: 9
Registered: December 2006
|
Junior Member |
|
|
On Jan 26, 7:30 am, Laurens <mr....@inter.nl.net> wrote:
> Hi Folks,
>
> I'm trying to get my DICOM-file imported in another program (Siemens
> E.Soft) to be analysed. My program writes the DICOM with the
> idlFFdicomEx-library, which seems to go just fine.
> But, my export isn't imported into the program; I compared header of
> both a file that actually does import and my own file that doesn't
> import, and the difference appears to hide in the SOP Instance UID.
>
> iirc, that should be just an unique ID, but it isn't...when I change
> that header (0008,0018) into something else (eg. add 2 to it) it doesn't
> work anymore. So I wondered how this UID is being generated and how I
> can create it in a way that it'll be accepted by other programs?
> Normally, the idlFFdicomEx-class automatically generates this header,
> but I think there might be a problem there...
>
> Is there anyone around who can shed some light over this? Anyone with
> Siemens e.soft knowledge would be very nice hehe, but if we can
> understand that SOP Instance UID a bit better we are already helped I
> think...
>
> Kind regards,
>
> Laurens
Please contact me directly for more info. I have documentation on how
to extend eSoft with IDL that I "think" I can share with you. After
you contact me, we can figure out if the content can be released,
etc. If your work is for research and not clinical development, we
should be okay. Thanks.
-Paul
psommer@ittvis.com
303-402-4679
|
|
|
|
|
|
| Re: Constructiuon of SOP instance [message #52658 is a reply to message #52384] |
Fri, 16 February 2007 06:09  |
Laurens
Messages: 41
Registered: May 2006
|
Member |
|
|
Robbie wrote:
> The IDL Broker exhibits very strange behaviour if you don't generate
> both a new SOP instance *and* SeriesUID. If you are creating multiple
> secondary capture images, then use the same new SeriesUID for all
> output images, and use a separate SOP instance for each output image.
> This makes the Output Series unique from the Input Series.
>
> You should use the UID generation function included on your E.Soft
> workstation. Otherwise, you can use the one I included in my
> GDLffDICOM package.
>
> Robbie
>
>
By the way, I found this:
http://sophorus.mine.nu/genuid
would that suffice?
|
|
|
|
| Re: Constructiuon of SOP instance [message #52659 is a reply to message #52384] |
Fri, 16 February 2007 05:56 |
Laurens
Messages: 41
Registered: May 2006
|
Member |
|
|
Robbie wrote:
> The IDL Broker exhibits very strange behaviour if you don't generate
> both a new SOP instance *and* SeriesUID. If you are creating multiple
> secondary capture images, then use the same new SeriesUID for all
> output images, and use a separate SOP instance for each output image.
> This makes the Output Series unique from the Input Series.
>
> You should use the UID generation function included on your E.Soft
> workstation. Otherwise, you can use the one I included in my
> GDLffDICOM package.
>
> Robbie
>
>
yeah going to use yours, the e.soft DLM didn't work out for me (it
didn't like IDL 6.3 :()
Can ya tell me where i can find yours?
Thnx, Laurens
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
