Difference between revisions of "2015 Refinement Registration Module"

From NAMIC Wiki
Jump to: navigation, search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
<gallery>
+
{|
Image:PW-Summer2015.png|[[2015_Summer_Project_Week#Projects|Projects List]]
+
| Case 25
</gallery>
+
|[[Image:RegResults.png |thumb|600px|Enabled switching through registration results]]  
 +
|}
  
 
==Key Investigators==
 
==Key Investigators==
Line 13: Line 14:
 
<h3>Objective</h3>
 
<h3>Objective</h3>
 
* Module for registration of the prostate was developed in Slicer 4. See code [https://github.com/PeterBehringer/Registration here]
 
* Module for registration of the prostate was developed in Slicer 4. See code [https://github.com/PeterBehringer/Registration here]
* Our objective is to make the module more generic, so that in can also be used by clinical staff for other procedures that require registration
+
* Our objective is to make the module more generic, so that in can also be used by clinical staff during more procedures that require preop/intraop or intraop/intraop registration
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
Line 24: Line 25:
 
<h3>Progress</h3>
 
<h3>Progress</h3>
 
* The module is functional
 
* The module is functional
 +
* Presented the module to several expert clinicians
 +
* Got valuable feedback on how to improve usability and code
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 14:59, 24 June 2015

Home < 2015 Refinement Registration Module
Case 25
Enabled switching through registration results

Key Investigators

  • Peter Behringer
  • Andriy Fedorov

Project Description

Objective

  • Module for registration of the prostate was developed in Slicer 4. See code here
  • Our objective is to make the module more generic, so that in can also be used by clinical staff during more procedures that require preop/intraop or intraop/intraop registration

Approach, Plan

  • Present the module to interested members of the community
  • Get feedback about the workflow and usability
  • Identify potential additional use cases and functionalities that make the module more generic

Progress

  • The module is functional
  • Presented the module to several expert clinicians
  • Got valuable feedback on how to improve usability and code