-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
make a dimse back end #18
Comments
I'm looking forward this! |
@pieper Not entirely sure what you are looking for. We have a few items that we have built the may be useful. For starters, I have a node:12.8.0-alpine container that has dcmtk-3.6-4 built inside. https://github.com/MichaelLeeHobbs/nodejs-dcmtk Additionally, I have the beginnings of a node dcmtk library. So far it really only has what we needed. If you are interested I will check that I can release it into open source. For example
The code thus far is very solid but it does need some refactoring for hard code values. The event symbols need a refactor as well to fix a lack of consistency. |
Thanks @MichaelLeeHobbs - this does look useful. @emelalkim has been working on this branch and the basics are working but there is definitely more to do. |
This might be what you want: https://www.npmjs.com/package/dicomweb-proxy |
Looks excellent @knopkem 👍 |
It's done. Have fun. |
From time to time people ask about using viewers like OHIF with a traditional (non-DICOMweb) PACS. It would be conceivable to implement this in dicomweb-server if someone had enough motivation.
One possible implementation could be to build a bridge to dcmtk or other native toolkit (e.g. like https://github.com/jmhmd/dcmtk-node) or to use the pure javascript code (https://github.com/OHIF/dicom-dimse).
The text was updated successfully, but these errors were encountered: