Difference between revisions of "ITKv4 DICOM Communications Discussion"

From KitwarePublic
Jump to navigationJump to search
m (Fixing up the wording of the sentence)
m (Fixed a typo in the name of the linked page)
Line 15: Line 15:
== Storage ==
== Storage ==
== Query/Retrieve ==
== Query/Retrieve ==
For an explanation of how to use DICOM to query a PACS, please see this page:  [[DICOM_QueryRetrieve_Explaned]]
For an explanation of how to use DICOM to query a PACS, please see this page:  [[DICOM_QueryRetrieve_Explained]]

Revision as of 14:47, 5 August 2010

Use this page to discuss and capture scenarios for using DICOM Query/Retrieve (Q/R) to load images from source (PACS) systems.

Scenarios

  • User wants to query a PACS system for a particular series. The user only knows the Patient ID, Date of Exam and Series Description to look for. Ultimately, the user wants this loaded in memory as an ITK Image object.

Standards

Most of the documentation for Verification, Storage and Query/Retrieve functionality can be found in Part 4 of the DICOM Standard.

Toolkits

  • GDCM is currently used for DICOM File I/O. At this time it does not support the communications aspects of DICOM, such as StoreSCU/StoreSCP, C-FIND, C-MOVE, etc. Are there plans to add this functionality to GDCM?
  • DCMTK contains the code needed for DICOM communications. It is currently not integrated into the ITK toolkit. Should it be?

Service Classes

Verification

Storage

Query/Retrieve

For an explanation of how to use DICOM to query a PACS, please see this page: DICOM_QueryRetrieve_Explained