Clinician and researcher end-user:
- Direct integration with PACS systems. Conformity to DICOM Standard: Query/Retrieve/Send
- Multimodal 2D and 3D image interactive visualization:
- Control of the visualisation window (Window Width/Level)
- Zoom and displacement
- Image rotation (+90, -90) and vertical and horizontal views
- Image annotations:
- Landmarks
- Measurements
- Regions of interest (ROI)
- Movie control: play forward, play back, infinite loop, speed control, etc.
- Clinical workflow navigation to easily navigate through the workflow steps. Usable interface for clinical environment
- Data: 3D images, surface meshes, volumetric meshes, signals and landmarks
- Visualization: Multiplanar reformation, OrthoSlice, MultiSlice, Direct volume rendering, XRay, Maximum-intensity projection
- IO formats: DICOM, vtk, vti, stl, Nifty, Analyze
- Available on Windows platform, 32 and 64 bits. Beta version available on Linux platform and MAC
- Included tools:
- DICOM browser and PACS connection
- Manual segmentation tool
- Surface mesh manipulation tools: Smoothing, volume closing, mesh optimization, tetra generation, ring cut, skeletonization
- Signal viewer
- Landmark selection
- Image processing tools
For developers:
- C++ language
- Plug-in architecture
- Cross-platform using standard CMake tool
- Easily integrate your own library and source code using CSnake tool
- Based on common open source libraries (VTK, ITK, MITK, BOOST, wxWidgets)
- Command line plugins to easily extend the framework
- Automated GUI generation: Used an XML to describe the parameters of a filter (compatible with 3D Slicer). Use automated GUI generation to create the graphical interface.
- Extensible Processing layer: supporting different processing data libraries integrated into the framework. For example, GIMIAS handles ITK image, VTK image, MITK image, CMGUI image and automatic conversion between them. See video here
- Extensible Rendering layer: support for different rendering libraries. CMGUI and MITK have been integrated as plugins that provide different rendering views. VTK image or a vtkPolyData can be rendered in CMGUI or MITK view. See video here
- VTK, MITK and ITK execution module: Dynamic library module can execute filters (like vtkImageThreshold) directly using a DLL (like vtkImaging.dll). This reduces the effort needed to integrate processing toolkits.