ITK/Release 4/DICOM: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(→TCons) |
(→Goals) |
||
Line 4: | Line 4: | ||
* Improve the support for DICOM needs by the ITK community | * Improve the support for DICOM needs by the ITK community | ||
# DICOM communication layer (PACS connection) | |||
# Streaming | |||
# type checking | |||
# minimum DICOM skeleton generation | |||
= Discussions = | = Discussions = |
Revision as of 04:20, 22 April 2011
Improving DICOM Support
Goals
- Improve the support for DICOM needs by the ITK community
- DICOM communication layer (PACS connection)
- Streaming
- 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:
design proposal
TCons
- TCon 2011/April/22, Minutes 2011_04_22
- TCon 2011/April/15, Minutes 2011_04_15
- TCon 2010/10/11, Minutes 2010_10_11