CTK DICOM Web Services: Difference between revisions
From Commontk
Jump to navigationJump to search
mNo edit summary |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
** Approach: | ** Approach: | ||
*** Improve DCMTK | *** Improve DCMTK | ||
*** | *** Kick the tires of the dcm4che implementation | ||
== Useful links == | == Useful links == | ||
Latest revision as of 10:59, 12 May 2014
Home < CTK DICOM Web Services- Investigate web service approach (WG27)
- Pros: Easily go accross firewall, leverage caching from commercial app
- Approach:
- Improve DCMTK
- Kick the tires of the dcm4che implementation
Useful links
Presentation: "Image Access Everywhere, DICOM Web Services" James F Philbin
dcm4che: Version 4.1.0.Alpha3 (and above)
DICOM Supplements
DICOM Part 18: Web Access to DICOM Persistent Objects (WADO)
Web Access to DICOM Persistent Objects by RESTful Services (WADO-RS); supplement 161
Store Over the Web by RESTful Services (STOW-RS); supplement 163
Query based on ID for DICOM Objects by RESTful Services (QIDO-RS); supplement 166
Server Options RESTful Services; supplement 170 (pc)
Not directly related is Supplement 157, "Multi-Frame Converted Legacy Images" , which is a more convenient way of handling large stacks of planar images (i.e. convert multiple single-slice images into a single multi-dimensional image).
