Projects:ARRA:SlicerWF:MigrationJavaClients2QT

Integration of Workflow Clients with Slicer4

---

Front-End GUI (NEW):

Development Toolkit / Language: QT/C++

*Two tier GUI integration:

1. QT Widget Palette for listing available Workflow Applications Callable from Development Tools Menu

2. QT Pop-up Windows for controlling Workflow Application. Callable from dispatching palette 1) as QT child dialog widget. The pop-up approach is proposed for ease navigation between WF GUI and Slicer4 GUI (volume edit window, cropping, etc)Major functionality: - project/data organizing
- workflow pipelines invocation
- loading Slicer scenes into parent Slicer4 instance

Workflow and Web Services invocation:

1. Java stubs (implemented)
2. File Binding (implemented)
3. RESTFul web service calls (if needed. Note: non-commercial QT does not support SOAP protocol)

Workflow and Web Services deployment:

1. BPEL Modules on Application Server for workflow pipelines (implemented)
2. SOAP Web services for CLI with Slicer modules
3. RESTFul web services as stubs between Slicer QT Modules and web services (if needed – most probably, file binding and Java stubs will suffice)

Case Studies / Scenarios

1. Basic EM Segmentation (initial project with minimal features but with full integration with Slicer)
2. PET/CT registration and SUV computation
3. Universal registration suite (longitudinal studies with multimodal images)
4. More complex EM Segmentation scenarios (with SPECTRE module, Lesion and WM hyper-intensity segmentation...)