ITK/Release 4/DICOM: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 13: | Line 13: | ||
== how to test against PACS automatically ? == | == how to test against PACS automatically ? == | ||
( thanks to | ( thanks to Steve Pieper) | ||
<pre> | |||
I had a chance to ask Lawrence Tarbox of Washington University your question | I had a chance to ask Lawrence Tarbox of Washington University your question | ||
about dicom testing. Lawrence is a participant in CTK and a long-time dicom | about dicom testing. Lawrence is a participant in CTK and a long-time dicom | ||
| Line 27: | Line 28: | ||
http://www.dvtk.org/ | http://www.dvtk.org/ | ||
</pre> | |||
=== Contestants === | === Contestants === | ||
Revision as of 18:03, 21 April 2011
Improving DICOM Support
Goals
- Improve the support for DICOM needs by the ITK community
- DICOM communication layer (PACS connection)
- type checking
- minimum DICOM skeleton generation
Discussions
Communications Discussions
how to test against PACS automatically ?
( thanks to Steve Pieper)
I had a chance to ask Lawrence Tarbox of Washington University your question about dicom testing. Lawrence is a participant in CTK and a long-time dicom standards participant too (he's actually working on the hosted application specification, which we should ultimately be compatible with). For PACS-like testing, he pointed to two well established efforts, linked below. Lawrence knows people involved in these and thinks they might be receptive to seeing integration with ctest and cdash if you want to pursue that. In any case I think we can learn a lot from these efforts. http://www.ihe.net/Connectathon/ (look for the MESA test suite) http://www.dvtk.org/
Contestants
Seting up a dcm4che server:
