DICOM Roadmap Dec2011: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
Agouaillard (talk | contribs) |
Agouaillard (talk | contribs) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
== Task 1: Complete GDCM work (Alex) == | == Task 1: Complete GDCM work (Alex) == | ||
# Finish adding support for | # Finish adding support for | ||
## DICOM RT | ## DICOM RT (ITK-113) | ||
## Streaming | ## Streaming (ITK-112) | ||
* Do *NOT* pursue DICOM Networking from GDCM | * Do *NOT* pursue DICOM Networking from GDCM | ||
== Task 2: 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. (NOTE ALEX: To be defined, I don't understand) | # 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 | ## Ideally datastructure can also be used by GDCM for reading/writing | ||
== Task 3: 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 | |||
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 | ||
| Line 22: | Line 22: | ||
## 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 | ## 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 | |||
## [http://www.na-mic.org/Wiki/index.php/CTSC:ARRA:dcm4chee_install DCM4CHEE] | |||
# Create DICOM PACS Tests | |||
## ITK-only tests (alex+drew) | |||
## ITK+Slicer/CTK tests (?) | |||
## Slicer/CTK tests (NAMIC) | |||
# Install tests in CTK and ITK | |||
= Meetings = | = Meetings = | ||
* [[ITK_Release_4/DICOM/Meeting_2011.09.01_Roadmap]] | * [[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)
- Finish adding support for
- DICOM RT (ITK-113)
- Streaming (ITK-112)
- Do *NOT* pursue DICOM Networking from GDCM
Task 2: Create ITK::DCMTK Module
- Use ITK module support to include DCMTK with ITK compilation (ITK-2716, 2756, 2757, 2774)
- 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. (NOTE ALEX: To be defined, I don't understand) (ITK-2759)
- Ideally datastructure can also be used by GDCM for reading/writing
Task 3: Create DICOM-PACS Module for ITK (?) (ITK-2760)
- 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)
- Update ITK to share (via GIT/Superbuild) DCMTK-PACS code from Slicer/CTK
- Offer as DICOM-PACS module in ITK
- 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 (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)
- Install DICOM Server
- Create DICOM PACS Tests
- ITK-only tests (alex+drew)
- ITK+Slicer/CTK tests (?)
- Slicer/CTK tests (NAMIC)
- Install tests in CTK and ITK
