Documentation/Nightly/Extensions/VirtualFractureReconstruction

Introduction and Acknowledgements

Extension: Virtual Fracture Reconstruction Acknowledgments: This work has been funded by the Austrian Science Fund. Author: Karl Fritscher, UMIT, BWH, MGH , contact: kfritscher@gmail.com Contributors: Peter Karasev, STeve Pieper, Ron Kikinis Module Description Example of a fractured shoulder with 8 fragments The reposition of bone fragments after a fracture, a process also referred to as fracture reduction, is a crucial task during the operative treatment of complex bone fractures. The repositioning of fracture fragments often requires a trial and error approach, which leads to a significant prolongation of the surgery and causes additional trauma to the fragments and the surrounding soft tissue. Wound healing failure, infections, or joint stiffness can be the consequence. Therefore, there is a clear trend towards the development of less invasive techniques to reconstruct complex fractures. In order to support this trend, software tools for calculating and visualizing the optimal way of repositioning fracture fragments based on the usage of segmented CT images as input data have been developed. In several studies, they have successfully demonstrated their potential to decrease operation times and increase reduction accuracy. However, existing software tools are often restricted to particular types of fractures and require a large amount of user interaction. Hence, the main objective of the proposed project is to overcome these limitations by developing an algorithmic pipeline that is calculating and visualizing the optimal way of repositioning fracture fragments with a minimal amount of user interaction and without restrictions to particular types of fractures. For this purpose, texture information coming from CT image, surface properties of the bone fragments as well as prior knowledge about the shape of the healthy (=non-fractured) bone are used for the reconstruction process. The module shall provide the possibility to perform a fully automated fracture reconstruction, but also to perform user guided reconstruction for very complex fractures with a large number of (small) bone fragments. Release Notes The extension consists of two modules. One CLI Module and one loadable module. The CLI module is providing the algorithmic core functionality for the fragment alignment process, whereas the loadable module manages the automated reconstruction pipeline and integrates user interaction. Please note that this module is under active development, and is being made available for the purposes of beta testing and feedback evaluation! The functionality, GUI and workflows may change in the subsequent releases of the module. Moreover, parts of the original algorithm are written in CUDA. Due to some limitations for Slicer extensions, this CUDA code can currently not be provided in this extension. The CUDA part of the code is implementing a more flexible registration algorithm (EM-ICP), which can potentially lead to better reconstruction results. If you are interested in using this extended version of the code, please contact me. Use Cases The extensions provides the possibility to reconstruction/realign fracture fragments and visualize the correct reconstruction of the fracture and switch between reconstructed and not reconstructed fragment position for individual fragments. In combination with a volume rendering a better/more detailed pre-surgical planning process shall be supported. Furthermore, the optimal reconstruction provided by the extension can a also act as a reference for post-operative quality assessment of the "real" reconstruction. Tutorials Panels and their use Using the first tab of the loadable module the user should provide the following input data: -3D CT image(volume) of non fractured bone (='Reference image') -3D labelmap of reference bone (='Reference labelmap') -3D image (volume) containing fractured bone (= 'Fragment image') -Multiple labelmaps containing one label for each fragment OR one labelmap containing labels for ALL fragments (='Fragment labelmaps') After providing the input data the 'Initialize reconstruction'-button should be pressed in order to create 3D models of the labelmaps and initialize the reconstruction process First tab of the loadable module If the user wants to provide a better manual interaction the transform sliders (from within the fracture reconstruction) module can be used. Better initialization will decrease the calculation times for the subsequent alignment process and potentially lead to better results. The "Reset manual transform" button to reset the postion of each fragment to the state prior to the manual interaction. Transform sliders for manual interaction After the initialization process is finished the second tab will be opened. The 2D and 3D views will be updated and a surface rendering of the fragments and reference bone will be provided. The user can change colors, opacity and visibility for each single fragment. Moreover, in this section, the user should select the fragment(s) he wants to align. If no fragments are selected all fragments will be aligned after starting the 'Start fragment alignment'-button. In this first step of the reconstruction process the fragments will be aligned to the reference bone. Second tab of the loadable module Updated 2D and 3D views after initialization step In order to set/adjust parameters for this first reconstruction step, the corresponding parameter settings tab ("Parameter settings for step 1") can be used. Explanations for all parameters are available within the module using tooltips. Again the user has the possibility to manually pre-align one or more fragments by selecting the fragment and reposition the fragments using the Transform sliders (Rotation and Translation sliders) Parameter section for first reconstruction step After the first step of the reconstruction is finished and user can inspect the intermediate result. 2D and 3D views will be update according to the calculated transformations. At this point the user, the following scenarios are possible: 1) Good registration - Accept registration without performing further registration (fine tuning part will be skipped). 2) Good registration - Accept registration and perform fine tuning 3) Registration not good enough - Go back to previous tab and alter parameters. BEFORE going back to the previous tab, the user should select which fragments shall be re- aligned (with different parameters). If no fragments are selected all fragments will be pre-aligned again. 4) Registration not good enough - Perform manual repositioning using transform sliders and accept registration or continue with fine tuning step. In any case the user can switch between views of aligned and unaligned fragments in the 3D and 2D viewers using the "toggle aligned <--> unaligned" button. Third tab of the loadable module after first step of reconstruction is finished Updated 2D and 3D views after first step of reconstruction. In this case only 2 of the 3 fragments were selected for registration in the second ("Fragment models") tab By pressing the "Start fine tuning" button the second part of the reconstruction process in which the fragments will be aligned against each other (without using the reference bone) will be started. The parameters for this step can be changed in the corresponding parameter tab ("Parameters for fine tuning") Parameter section for first reconstruction step After the calculations for the fine tuning step are finished, the last tab will be opened ("Result step 2"). Again 2D and 3D views will be updated accordingly and the same 4 scenarios as in the previous step are possible. Final tab of the loadable module after second step of reconstruction process Updated 2D and 3D views after final step of reconstruction. Note that the visible gaps are due to missing bone that has been "simulated" in this (toy) example. This view was generated using a wireframe representatioin of the fragments in combination with a volume rendering of CT dataset of the (healthy) reference bone

References

• [http://???

Information for Developers

• Source code of the module: https://github.com/???