Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Get (300A,000C) RTPlanGeometry Dicom tag #102

Open
OoDimoO opened this issue Dec 16, 2022 · 1 comment
Open

Feature Request: Get (300A,000C) RTPlanGeometry Dicom tag #102

OoDimoO opened this issue Dec 16, 2022 · 1 comment

Comments

@OoDimoO
Copy link

OoDimoO commented Dec 16, 2022

Hi there,

I'm a new user of EvilDicom and must say it is a very usefull tool that I use to massively export DICOM to a machine used by students.
At the moment, I export all approved plans and remove the ones I don't want with a python script.
I would like to be able to choose not to export the verification plans even though they are approved.
According to my knowledge, the difference between a verification plan and one designed for the treatment is in the DICOM tag (300A,000C) RTPlanGeometry.
In this tag, the value is "VERIFICATION" for the verification plan and "PATIENT" for the treatment.
So far, sorting plans using this small difference has worked for me with my python scripts, so I wonder if it would be possible for you to implement this as an attribut of the CFindPlanIOD class.

I thank you for all the efforts you put into this package.

Best regards,

Dimitri

@OoDimoO
Copy link
Author

OoDimoO commented Dec 16, 2022

Hi there,

Damn Friday afternoons, I did a little mistake that I will correct right now:
The DICOM Tag (300A,000C) RTPlanGeometry takes the value PATIENT/TREATMENT_DEVICE wether it is verification/treatment
and also the DICOM tag (300A, 000A) Plan Intent changes from VERIFICATION to CURATIVE depending on the type verification/treatment.

One of these tags or both would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant