Add Private Halcyon RT Plan SOP Class #39
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Varian Halcyon is using a specific SOP Class for the RT Plans (https://visionrt.com/wp-content/uploads/2024/06/1016-0570-DICOM-Conformance-Statement-1.1.pdf). Right now - this specific DICOM series ends up in the DicomExportService quarantine.
This code change adds the SOP Class UID in order that the specific Dicom Series will pass the CTP pipeline.
The dcm4che project does not have it in the dictionary yet. I'm not sure if I should add an item to the source/resources/dictionary.xml. If yes, please tell me and I will do that.