Difference between revisions of "2012 Summer Project Week:XNATSlicerIntegration"

From NAMIC Wiki
Jump to: navigation, search
Line 43: Line 43:
 
The XNAT-Slicer module utilizes the DICOM Details Popup (from the DICOM module) after a user loads a scan folder of DICOM images from the XNAT-Slicer module.  While this communication is incredibly useful, we believe a few adjustments to the DICOM module would streamline the workflow of XNAT-Slicer.<br><br>
 
The XNAT-Slicer module utilizes the DICOM Details Popup (from the DICOM module) after a user loads a scan folder of DICOM images from the XNAT-Slicer module.  While this communication is incredibly useful, we believe a few adjustments to the DICOM module would streamline the workflow of XNAT-Slicer.<br><br>
  
<b>1 - Refreshing:</b><br>After downloading a scan in the XNAT-Slicer module, the "DICOM Details" popup lists the downloaded DICOMs only when the popup hasn't yet been used in the current Slicer session.  If the popup has already been used/opened, the "DICOM Details" popup does not list the new set, in spite of being successfully inserted in the cache/database.  In this scenario, when the user restarts Slicer and opens the DICOM module, they will find that the "DICOM Details" popup contains the newly downloaded set.  This is likely the result of a highly controlled "refresh" condition in reading the updated database.  This may be by design, and "fixing" it may be involved.  <br> Next step: Inquire if the popup can be refreshed or a one-off "Details Popup" window can be developed that will allow the developer to control its behavior.<br><br>
+
<i>1 - Refreshing:</i><br>After downloading a scan in the XNAT-Slicer module, the "DICOM Details" popup lists the downloaded DICOMs only when the popup hasn't yet been used in the current Slicer session.  If the popup has already been used/opened, the "DICOM Details" popup does not list the new set.  This is  in spite of the downloaded files being successfully inserted in Slicer's SQL DICOM database.  In this scenario, when the user restarts Slicer and opens the DICOM module, they will find that the "DICOM Details" popup contains the newly downloaded set.  This is likely the result of a highly controlled "refresh" condition in reading the updated database.  This may be by design, and "fixing" it may be involved.  <br> Next step: Inquire if the popup can be refreshed or a one-off "Details Popup" window can be developed that will allow the developer to control its behavior.<br><br>
  
<b>2 - Customization:</b><br>If a user downloads a DICOM folder off of XNAT, it would be nice to have the ability to load a customized "DICOM Details" popup where the only DICOM set presented is the one the user just downloaded.  Right now, the popup lists all DICOM sets downloaded by the user.<br> Next Step: inquire what the effort would be to create such a customized popup.
+
<i>2 - Customization:</i><br>If a user downloads a DICOM folder off of XNAT, it would be nice to have the ability to load a customized "DICOM Details" popup where the only DICOM set presented is the one the user just downloaded.  Right now, the popup lists all DICOM sets downloaded by the user.<br> Next Step: inquire what the effort would be to create such a customized popup.
  
 
==Delivery Mechanism==
 
==Delivery Mechanism==

Revision as of 15:50, 11 June 2012

Home < 2012 Summer Project Week:XNATSlicerIntegration

Key Investigators

  • Washington University in St. Louis: Daniel Marcus, Sunil Kumar
  • Isomics: Steve Pieper

Objective

Allow data exchange between XNAT and Slicer. A detailed objective list can be found here.

Approach, Plan

Phase 1: Develop a beta module that fulfills the outlined objectives.
Phase 2: Solidify UI and functionality though user testing.
Phase 3: Port the REST API-based UI into a web-based UI.

Progress

As of June 2012, a beta version of this widget is being tested.


Known Issues

Crashing Frequency During "Update Scene" Workflow (MEDIUM)

The module tends to crash more frequently during the "Update Scene" workflow.
Next step: define a replicatable test.

DICOM Details Popup (NICE TO HAVE)

The XNAT-Slicer module utilizes the DICOM Details Popup (from the DICOM module) after a user loads a scan folder of DICOM images from the XNAT-Slicer module. While this communication is incredibly useful, we believe a few adjustments to the DICOM module would streamline the workflow of XNAT-Slicer.

1 - Refreshing:
After downloading a scan in the XNAT-Slicer module, the "DICOM Details" popup lists the downloaded DICOMs only when the popup hasn't yet been used in the current Slicer session. If the popup has already been used/opened, the "DICOM Details" popup does not list the new set. This is in spite of the downloaded files being successfully inserted in Slicer's SQL DICOM database. In this scenario, when the user restarts Slicer and opens the DICOM module, they will find that the "DICOM Details" popup contains the newly downloaded set. This is likely the result of a highly controlled "refresh" condition in reading the updated database. This may be by design, and "fixing" it may be involved.
Next step: Inquire if the popup can be refreshed or a one-off "Details Popup" window can be developed that will allow the developer to control its behavior.

2 - Customization:
If a user downloads a DICOM folder off of XNAT, it would be nice to have the ability to load a customized "DICOM Details" popup where the only DICOM set presented is the one the user just downloaded. Right now, the popup lists all DICOM sets downloaded by the user.
Next Step: inquire what the effort would be to create such a customized popup.

Delivery Mechanism

This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)

  1. Slicer Module - YES

Known Issues

References