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

DICOM Support #31

Open
fizxmike opened this issue Jul 29, 2024 · 2 comments
Open

DICOM Support #31

fizxmike opened this issue Jul 29, 2024 · 2 comments

Comments

@fizxmike
Copy link
Member

Adding as feature request. In the meantime, I've attached and example from our Proton and Electron FLASH research that depends on pynetdicom (sister project of pydicom). It will need to be modified to support photon plans (add another SOPClass UID - and check that DICOM UUIDs make sense).

@LuisOlivaresJ
Copy link

Hi Michael,

I am Luis, a clinical Medical Physicist who loves Python. I would like to use pyesapi and pylinac to automate some of my QC tests.

Is it possible to export an image (for example a VMS.TPS.Model.API.Image object) as a DICOM file using a pyesapi script?

@fizxmike
Copy link
Member Author

The example script I shared above shows how to communicate with Eclipse's DICOM Daemon via pynetdicom. So, if you already have the image set ready in Eclipse, that might be the easiest way. The example script only deals with dose and plans for Protons and Electrons, but with the right modifications, it should be able to support CT images and photon plans as well. It's incomplete, that's why it's not in the main codebase yet.

In principle, one could construct (or edit) a DICOM file using pydicom filling with data retrieved through PyESAPI. Although getting the UUIDs all correct for a new set of DICOM files is something you have to manage yourself.

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

2 participants