Pinnacle 9.10 DICOM export, DICOM RT mode Varian 4DITC issues

[Daniel Cronk]

We are a veterinary institute that has recently acquired a stand alone Linear Accelerator (sans a Record & Verify system).

We have also upgraded our Pinnacle Radiation Therapy system (from 8.0d to 9.10).

We are able to export the RT Plan, RT Structure, DICOM Images and open the patient RTPLAN file on the Varian 4DITC system and have it "work" for the most part. However, when we try to include the Setup Beams from Pinnacle and open them on the 4DITC we receive an error:

Session Load Error:

The session received from the management system is not valid.

Selecting session for patient failed.

Extra Information:

The XML document load or validate operation failed.

Extra Information:

File: Session Data

Description: enumeration constraint failed

The Element: 'TreatmentDelivery Type" has an invalid value according to its data type.

When I look in the DICOM header for Treatment Delivery Type it appears to me to be correct:

>(300a,00ce)   Treatment Delivery Type   CS   1   SETUP 

Their DICOM conformance statement states:

In Extended Interface FieldType is used to distinguish between treatment and setup fields (values: TREATMENT, SETUP) while DICOM attribute Treatment Delivery Type (300A,00CE) always contains value TREATMENT. When FieldType is removed from Extended Interface, the new value SETUP for Treatment Delivery Type (300A,00CE) is used to designate setup fields. 

However, looking at Pinnacle 9.10 DICOM conformance Statement there is a bit that states:

* The Varian Private attributes are only included if Varian OBI support has been enabled and Setup beams are being exported.

Has anyone experienced anything similar to this issue or maybe have thoughts? I've been working with a couple of Physisits from Philips on the PInnacle side, but they have no further thoughts right now.

I did also see something about this on another group, but I'm not sure what it really means. Maybe this is the issue? 

In the following link (http://tinyurl.com/phppl2u), it appears that during adding the DICOMAddSCP process, it seems that one must add varian_scp before the hostname. I'm wondering if maybe this needs to be done in the setup of the ADACRTP_SCP host when it's set up?  Perhaps this is what it's talking about when it says "The Varian Private attributes are only included if Varian OBI support has been enabled and Setup beams are being exported."

So maybe it should have been

./DICOMAddSCP -r -d varian_scp ADACRTP_SCP 104 <not sure what port the pinnacle server listens to itself on, I know when I listen to myself it's a lot higher number>

[Steven Boyd]

Hi,

Try to export the set up fields as a separate trial. 

Often if the set up fields are exported as part of the same prescription the r/v see's zero does associated to active fields. 

So send over your tx fields. 

Make sure all is good. 

Then copy your tx trial and delete the treatment fields and rx. 

So just export 2 open 10x10 fields with no dose. 

It might work or I am out of practice!

Sent from my iPhone

--
--
You received this message because you are subscribed to the Google
Groups "pinnacle3-users" group.
To post to this group, send email to pinnacl...@googlegroups.com
To subscribe to this group, send email to
pinnacle3-us...@googlegroups.com
To unsubscribe from this group, send email to
pinnacle3-use...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pinnacle3-users?hl=en

---
You received this message because you are subscribed to the Google Groups "pinnacle3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pinnacle3-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.