2016 Summer Project Week/medical imaging webapp

• 

  Projects List

Key Investigators

• Steve Pieper (Isomics)
• Hans Meine (Uni Bremen, MEVIS)
• Marco Nolden (DKFZ)

(other interested parties are welcome!)

Project Description

Objective

• Review the state of the art in medical imaging web apps
  • Follow on from the MIWS Hackfest at BWH.
  • Discuss subsequent developments and ideas
• Consider various use cases:
  • Pure web browser application
  • Web browser + remote compute or rendering services
  • Web App widgets used in desktop application (e.g. via QtWebKit/QtWebEngine in Slicer/MITK/MeVis)
• Topics
  • Native JavaScript code for DICOM IO, Rendering, Processing
  • Organization of toolkits and libraries
  • Interacting with the community of like-minded developers

Approach, Plan

• Discuss recent developments cited in the Objective section
• Identify more valuable development priorities
  • provide useful functionality (e.g. improved DICOM patient/study/series/search browser)
  • probe any outstanding issues (e.g. test scalability or performance questions)
  • establish paradigms for ongoing development
• Finalize a prototype showing JS-C++ interaction replacing the CTK DICOM Browser Widget with a web-technology based implementation

Progress

• Investigate emerging file distribution tools
  • infinit
  • ipfs
    • ipfs ls QmYDwWrSPnYeE1z1Ae3me9XzT394YKy4ux5e85V4oCDakT
    • Brainlab demo objects QmTftaDyQCNFsceFwR2kkRMdz5VBbCzzD64VVEWiKRA2Go
• Experimental integration of ipfs-hosted data with CTest based continuous integration (WIP) https://github.com/QIICR/dcmqi/pull/22
• Identified zerorpc as a powerful solution for distributed MIC apps (based on ØMQ and MessagePack).
  • Use msgpack-numpy to support ndarrays in zerorpc (implemented via monkey-patching).
• The JS-C++ interaction lives now on an experimental branch in CTK (will move to the commontk organization soon)
  • various mechanisms for development, debug and deployment can be tested,
    • Qt resource compiler
    • separate HTML files
    • running the UI in a browser vs integrated in the CTK application, remote debugging of javascript (all accessible through buttons in the UI)