DICOM export into Pinnacle

[NickH]

Hi,

I'm exporting some plans out of Pinnacle, modifying them in CERR and
then doing a DICOM export of the plan. I wanted to then re-import this
back into Pinnacle but am getting an error "invalid license key" when
I try to import into Pinnacle.

I was wondering if anyone has successfully imported into Pinnacle CERR
exported plans in the DICOM format? If so how did you go about it?

Regards,

Nick

[Joe Deasy]

Interesting. I guess this is a Pinnacle issue?

Once they are exported, there are of course no Matlab licensing
issues.

- Joe

[Charles Wang]

Dear Joe Deasy,

  This is definitively a Pinnacle issue, not related to CERR at all.

 

  Pinnacle treatment planning system as for v7.4 and v6.2 in our department only accept DICOM image with manufacturor tag (0008,0070) being "philips" or licensed companies by local dealer, and other manufacturor tag will be invalid license during importing DICOM images.

Another big issue must be aware is that Pinnacle export error Y coordinates in their RTOG export files (intentionally ? to avoid user to dig into their format to resend data back to Pinnacle ). If you try to export via DICOM and RTOG both and compare their coordinates, you will find that problem.

 

Best regard,

   Thank you, Joe, for your excellent and flexible CERR.

    Charles

 

2008/10/22 Joe Deasy <j.o....@gmail.com>

[Khullar, Divya]

Charles,

I figured out this problem just last week in our clinic. I am not sure if this is intentionally done but the older version of pinnacle would export RTOG data without the shift in co-ordinates. There is both X and Y shift. Some one in our clinic is trying to work with Pinnacle on this. If I hear something will let you know.

 

Best

Divya

 

Divya Khullar
Washington University School of Medicine
Department of Radiation Oncology
Campus Box 8224
4921 Parkview Place
St. Louis, MO 63110
Phone : (314)747-2973
Pager : (314)253-1927
Fax     : (314)362-8521
 
****************************************************************************************************************************************************************
This email message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product, or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message from your computer.  Thank you.
****************************************************************************************************************************************************************

---

[Charles Wang]

Hi Divya,

Thank you for your information. There is only Y shift (-512  x pixel spacing 0.97mm = -480)  between DICOM and RTOG data exported from Our Pinnacle TPS (v7.4).  X and Z coordinate is matched.

I found that negated the yOffset in export_image_plane_module_field.m  could  have a walkaround.

 

offset(1) =  scanstruct.uniformScanInfo.xOffset - spacing(1)*(dim(2)-1)/2;
offset(2) = -scanstruct.uniformScanInfo.yOffset - spacing(2)*(dim(1)-1)/2;
offset(3) = -(scanstruct.scanInfo(end).zValue);

 

I suspect that it was introduced from the data source (ie. Pinnacle) or there may be a bug in RTOG importing routine, because all data including contours, dose, and images in planC have the same Y shift.

 

Best regards,

    Charles

 

2008/10/23 Khullar, Divya <dkhu...@radonc.wustl.edu>

[NickH]

Hi All,

Thanks for your very useful advice so far. I agree, it seems to be on
the Pinnacle side that the problem resides.

From what I can gather, it is possible to import a DICOMRT dose
structure into Pinnacle, provided the corrections to the coordinate
system (as described by Charles) is applied? Is this done the same way
as you would an image set? I am as yet unsuccessful, still getting the
license error even when changing the manufacturer's tag to 'philips'
or 'ADAC' etc.

I am currently attempting to do it the 'brute force' way by saving the
dose grid in the relevant binary format and replacing the binary file
in the back end of Pinnacle.

My apologies for steering the conversation away from CERR to Pinnacle,
but I think it still maintains some relevance. I agree with Charles,
CERR is a fantastic application and extremely flexible.

Regards,

Nick

On Oct 24, 2:07 am, "Charles Wang" <cywang...@gmail.com> wrote:
> Hi Divya,
> Thank you for your information. There is only Y shift (-512  x pixel spacing
> 0.97mm = -480)  between DICOM and RTOG data exported from Our Pinnacle TPS
> (v7.4).  X and Z coordinate is matched.
> I found that negated the yOffset in export_image_plane_module_field.m
> could  have a walkaround.
>
> offset(1) =  scanstruct.uniformScanInfo.xOffset - spacing(1)*(dim(2)-1)/2;
> offset(2) = -scanstruct.uniformScanInfo.yOffset - spacing(2)*(dim(1)-1)/2;
> offset(3) = -(scanstruct.scanInfo(end).zValue);
>
> I suspect that it was introduced from the data source (ie. Pinnacle) or
> there may be a bug in RTOG importing routine, because all data including
> contours, dose, and images in planC have the same Y shift.
>
> Best regards,
>     Charles
>

> 2008/10/23 Khullar, Divya <dkhul...@radonc.wustl.edu>

> >  ------------------------------
>
> > *From:* cerr-...@googlegroups.com [mailto:cerr-...@googlegroups.com] *On
> > Behalf Of *Charles Wang
> > *Sent:* Wednesday, October 22, 2008 7:12 PM
> > *To:* cerr-...@googlegroups.com
> > *Subject:* [cerr-forum:574] Re: DICOM export into Pinnacle

>
> > Dear Joe Deasy,
>
> >   This is definitively a Pinnacle issue, not related to CERR at all.
>
> >   Pinnacle treatment planning system as for v7.4 and v6.2 in our department
> > only accept DICOM image with manufacturor tag (0008,0070) being "philips" or
> > licensed companies by local dealer, and other manufacturor tag will be
> > invalid license during importing DICOM images.
>
> > Another big issue must be aware is that Pinnacle export error Y
> > coordinates in their RTOG export files (intentionally ? to avoid user to dig
> > into their format to resend data back to Pinnacle ). If you try to export
> > via DICOM and RTOG both and compare their coordinates, you will find that
> > problem.
>
> > Best regard,
>
> >    Thank you, Joe, for your excellent and flexible CERR.
>
> >     Charles
>

> > 2008/10/22 Joe Deasy <j.o.de...@gmail.com>