DICOM Roadmap Dec2011: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Tasks =
= Tasks =


== Complete GDCM work (Alex) ==
== Task 1: Complete GDCM work (Alex) ==
* Finish adding support for DICOM RT and streaming
# Finish adding support for
* Do not pursue DICOM Networking from GDCM
## DICOM RT (ITK-113)
## Streaming  (ITK-112)
* Do *NOT* pursue DICOM Networking from GDCM


== Create ITK::DCMTK Module ==
== Task 2: Create ITK::DCMTK Module ==
* Use ITK module support to include DCMTK with ITK compilation
# Use ITK module support to include DCMTK with ITK compilation (ITK-2716, 2756, 2757, 2774)
* Offer DCMTK Reader/Writer in ITK's IO factory
# Offer DCMTK Reader/Writer in ITK's IO factory (ITK-2758)
* Define data structures for specifying which DICOM Object files should be composed into a volume (when reading) or which DICOM Object files were created when saving a volume to disk.  The application can optionally serialize these data structures (e.g. in sqlite) so that previously parsed data can be quickly loaded into ITK without needing to be re-parsed.
# Define data structures for specifying which DICOM Object files should be composed into a volume (when reading) or which DICOM Object files were created when saving a volume to disk.  The application can optionally serialize these data structures (e.g. in sqlite) so that previously parsed data can be quickly loaded into ITK without needing to be re-parsed. (NOTE ALEX: To be defined, I don't understand)  (ITK-2759)
## Ideally datastructure can also be used by GDCM for reading/writing


== Create DICOM-PACS Module for ITK (?) ==
== Task 3: Create DICOM-PACS Module for ITK (?) (ITK-2760) ==
* Share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK
# Share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK
** This is the code used to issue a query and receive a list of files
This is the code used to issue a query and receive a list of files
** The list of files should use the datastructure from ITK::DCMTK Module (Task 2)
The list of files should use the datastructure from ITK::DCMTK Module (Task 2.3)
* Update ITK to share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK
# Update ITK to share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK
** Offer as DICOM-PACS module in ITK
## Offer as DICOM-PACS module in ITK
** Searches returned should be easily passed to the ITK::DCMTK IO facility (Task 2) for reading once transfer has been completed.
## Searches returned should be easily passed to the ITK::DCMTK IO facility (Task 2.2) for reading once transfer has been completed.
** Also, when multiple DICOM objects have been written to disk, the same data structure for writing them should be able to be passed to the DICOM-PACS Module for upload to a PACS
## Also, when multiple DICOM objects have been written to disk, the same data structure (Task 2.3) for writing them should be able to be passed to the DICOM-PACS Module for upload to a PACS


== Slicer DICOM-Objects->itk::Image via DCMTK ==
== Task 4: Slicer DICOM-Objects->itk::Image via DCMTK (NAMIC)==
* Update Slicer so that reading/writing DICOM Objects to/from itk::Image is done via ITK's DCMTK
* Update Slicer so that reading/writing DICOM Objects to/from itk::Image is done via ITK's DCMTK


== Setup DICOM-PACS Testing ==
== Task 5: Setup DICOM-PACS Testing (ITK-2762) ==
* Install DICOM Server
# Install DICOM Server
** [http://www.na-mic.org/Wiki/index.php/CTSC:ARRA:dcm4chee_install DCM4CHEE]
## [http://www.na-mic.org/Wiki/index.php/CTSC:ARRA:dcm4chee_install DCM4CHEE]
* Create DICOM PACS Tests
# Create DICOM PACS Tests
** ITK-only tests
## ITK-only tests (alex+drew)
** ITK+CTK tests
## ITK+Slicer/CTK tests (?)
** Slicer tests
## Slicer/CTK tests (NAMIC)
* Install tests in CTK and ITK
# Install tests in CTK and ITK
 
= Meetings =
* [[ITK_Release_4/DICOM/Meeting_2011.09.01_Roadmap]]

Latest revision as of 09:24, 4 December 2011

Tasks

Task 1: Complete GDCM work (Alex)

  1. Finish adding support for
    1. DICOM RT (ITK-113)
    2. Streaming (ITK-112)
  • Do *NOT* pursue DICOM Networking from GDCM

Task 2: Create ITK::DCMTK Module

  1. Use ITK module support to include DCMTK with ITK compilation (ITK-2716, 2756, 2757, 2774)
  2. Offer DCMTK Reader/Writer in ITK's IO factory (ITK-2758)
  3. Define data structures for specifying which DICOM Object files should be composed into a volume (when reading) or which DICOM Object files were created when saving a volume to disk. The application can optionally serialize these data structures (e.g. in sqlite) so that previously parsed data can be quickly loaded into ITK without needing to be re-parsed. (NOTE ALEX: To be defined, I don't understand) (ITK-2759)
    1. Ideally datastructure can also be used by GDCM for reading/writing

Task 3: Create DICOM-PACS Module for ITK (?) (ITK-2760)

  1. Share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK

This is the code used to issue a query and receive a list of files The list of files should use the datastructure from ITK::DCMTK Module (Task 2.3)

  1. Update ITK to share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK
    1. Offer as DICOM-PACS module in ITK
    2. Searches returned should be easily passed to the ITK::DCMTK IO facility (Task 2.2) for reading once transfer has been completed.
    3. Also, when multiple DICOM objects have been written to disk, the same data structure (Task 2.3) for writing them should be able to be passed to the DICOM-PACS Module for upload to a PACS

Task 4: Slicer DICOM-Objects->itk::Image via DCMTK (NAMIC)

  • Update Slicer so that reading/writing DICOM Objects to/from itk::Image is done via ITK's DCMTK

Task 5: Setup DICOM-PACS Testing (ITK-2762)

  1. Install DICOM Server
    1. DCM4CHEE
  2. Create DICOM PACS Tests
    1. ITK-only tests (alex+drew)
    2. ITK+Slicer/CTK tests (?)
    3. Slicer/CTK tests (NAMIC)
  3. Install tests in CTK and ITK

Meetings

Retrieved from "https://public.kitware.com/Wiki/index.php?title=DICOM_Roadmap_Dec2011&oldid=44071"