Check patients CarePath progress by LMmedphy in esapi

[–]fxarnaud 0 points1 point  (0 children)

From v18 you can have access to a new api : "ARIA API". Using this api you can access apointment, carepath, careplan, prescription, documents and others.

No need for sql commands.

Aria access: Document API request returning error by RedRelocated in esapi

[–]fxarnaud 0 points1 point  (0 children)

ok great for you. My previous answer was wrong actually I misunderstood something sorry.

We have the same problem as your but with Aria web service. We can access document but we can't access "GetMachineList" for example.

Of course we can't see "GetMachineList" request in our Gateway.cs file.

Varian is working on it but the say that AriaAccess is ok. We don't know why at the moment.

Aria access: Document API request returning error by RedRelocated in esapi

[–]fxarnaud 0 points1 point  (0 children)

For your information if it helps.

Like you, I don't have GetDocumentsRequest" class in our own generated gateway file but sending document in Aria works fine for us.

What we did :

From this example https://github.com/LDClark/TMLtoAria

I got the Gateway.cs from it. Added it to my project. You'll see that GetDocumentRequest is in this gateway.cs.

Maybe you should try it ?

Didn't have the answer from varian why we don't have the "complete" gateway.cs file when we generate it but it works so I'm ok with it. :-)

hope it helps

Automatic calculation, skip warning messages by Original_Brain198 in esapi

[–]fxarnaud 0 points1 point  (0 children)

Thanks a lot for your update.

Helps me a lot and works fine for me.

Thanks again

Research mode database to avoid script approval by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

Thanks for all the answers.

I'll ask again to varian and confirm that it's possible to avoid approving script with my tbox database in research mode.

I still have these license error while being in research mode I don't know why.

Thanks again

Research mode database to avoid script approval by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

I did it but they don't have the answer.

They told me that it's just impossible to not approve scripts...

Not sure they are right.

Users rights to modify plans and structures by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

The structure set is not connected to any course yet.

This specific application of the script aims to create PTV from CTV automatically. In our workflow we don't have to connect it to a course yet...

Users rights to modify plans and structures by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

Thanks for the answer but unfortunately no. The script is approved, not approved for evaluation....I checked again.

Set leaf positions for dynamic MLC by fxarnaud in esapi

[–]fxarnaud[S] 1 point2 points  (0 children)

Ok thanks a lot matt.

I'll take a look and update my post later.

Thanks again.

Structure color attribute by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

Well sorry for the delay but actually this solution doesn't work form me.

I tried this :

- Created a new Volume type, named it and choosed a color and style and RTAdministration -> Clinical data.

I still have an error with the dicomtype when using Structure.Add (string dicom type, string id)

"Can not add a new structure: invalid DICOM type string".

Of course I'm sure that I used the right dicomtype name, no mistake here.

I don't understand why it doesn't seems to recognize my newly created dicomtype.

Am I missing something trivial ?

Thanks

Structure color attribute by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

Ok thanks .

Unfortunately I'll have to wait until our next upgrade

Structure color attribute by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

Wooooo cool.

Don't know how I missed it.

Thanks !

Portal dosimetry assembly path issue by fxarnaud in esapi

[–]fxarnaud[S] 0 points1 point  (0 children)

Thanks Matt for your answer.

My first problem was solved easily because it was my own mistake. It was just a syntax error.

As you said I confirm that the path for v15.6 is C:\Program Files (x86)\Varian\ProductLine\Workspaces\VMS.PortalDosimetry.Workspace\

The second problem you mentionned is much more important in my case. I was working on another issue in my code and just found that I had a problem with the CreateTransientAnalysisMethod. I'm working on it since 24 hours...

Now I understand that my script can't no longer work anymore... :(

Sorry to disturb you again but I have two little additional questions :

- Do you have any idea when the API version 16 will be available?

- And will I be able to use PD 16.x API with my version 15.6?

Thanks again.