Difference between revisions of "2016 Winter Project Week/Projects/AIMInteroperability"

From NAMIC Wiki
Jump to: navigation, search
(Just found AIM as interesting topic)
 
 
(10 intermediate revisions by 4 users not shown)
Line 6: Line 6:
 
==Key Investigators==
 
==Key Investigators==
 
* Hans Meine
 
* Hans Meine
 +
*Steve Pieper
 +
*Andriy Fedorov
  
 
==Project Description==
 
==Project Description==
−
<div style="margin: 20px;">
+
{| class="wikitable"
−
<div style="width: 27%; float: left; padding-right: 3%;">
+
! style="text-align: left; width:27%" |  Objective
−
<h3>Objective</h3>
+
! style="text-align: left; width:27%" |  Approach and Plan
 +
! style="text-align: left; width:27%" |  Progress and Next Steps
 +
|- style="vertical-align:top;"
 +
|
 +
<!-- Objective bullet points -->
 
* Evaluate [https://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-OpenSourceDevelopment AIM] as standard for image annotations, in particular w.r.t. interoperability (example: Slicer / MeVisLab)
 
* Evaluate [https://wiki.nci.nih.gov/display/AIM/Annotation+and+Image+Markup+-+AIM#AnnotationandImageMarkup-AIM-OpenSourceDevelopment AIM] as standard for image annotations, in particular w.r.t. interoperability (example: Slicer / MeVisLab)
−
</div>
+
|
−
<div style="width: 27%; float: left; padding-right: 3%;">
 
−
<h3>Approach, Plan</h3>
 
 
*Try out AIM software
 
*Try out AIM software
−
*Find out what AIM support exists in 3D Slicer already
+
*Look at [http://www.na-mic.org/Wiki/index.php/Projects:QIN:3D_Slicer_Annotation_Image_Markup AIM support in 3D Slicer]
 +
*Check [http://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_A.html#sect_TID_1500 TID 1500 measurement template in DICOM SR] and work in progress on [ftp://d9-workgrps:Private15@medical.nema.org//MEDICAL/Private/Dicom/WORKGRPS/Committee/2015/2015-12-03/New-Work-Item-Proposals/Work-Item-Proposal%20-%20AIM2.docx harmonization of common AIM use cases through encoding as DICOM TID 1500 SR instances].
 +
*Check [https://peerj.com/preprints/1541v1/ PeerJ pre-print]
 
*Estimate effort / plan further steps whether and how AIM could be supported in MeVisLab
 
*Estimate effort / plan further steps whether and how AIM could be supported in MeVisLab
−
</div>
+
|
−
<div style="width: 27%; float: left; padding-right: 3%;">
+
*Discussed topices mentioned under "approach" with Andriy
−
<h3>Progress</h3>
+
*Conclusion: Ultimately, DICOM is the way to go
−
*AIM template builder downloaded
+
**The PeerJ paper documents the QIICR approach w.r.t. DICOM usage very well (for one of QIICR's use cases) -> definite read!
−
</div>
+
**Andrey has a [http://fedorov.cloudant.com/dicom_search/.site/index.html searchable DICOM standard] online which is practically impossible to find (but better than the one under pieper's cloudant domain).
−
</div>
+
*AIM is slightly more flexible w.r.t. template building, but that flexibility also limits interoperability, and DICOM allows "private templates", too, if necessary (no template builder, though)
 +
|}

Latest revision as of 12:19, 7 January 2016

Home < 2016 Winter Project Week < Projects < AIMInteroperability

Key Investigators

  • Hans Meine
  • Steve Pieper
  • Andriy Fedorov

Project Description

Objective Approach and Plan Progress and Next Steps
  • Evaluate AIM as standard for image annotations, in particular w.r.t. interoperability (example: Slicer / MeVisLab)
  • Discussed topices mentioned under "approach" with Andriy
  • Conclusion: Ultimately, DICOM is the way to go
    • The PeerJ paper documents the QIICR approach w.r.t. DICOM usage very well (for one of QIICR's use cases) -> definite read!
    • Andrey has a searchable DICOM standard online which is practically impossible to find (but better than the one under pieper's cloudant domain).
  • AIM is slightly more flexible w.r.t. template building, but that flexibility also limits interoperability, and DICOM allows "private templates", too, if necessary (no template builder, though)
Retrieved from "https://www.na-mic.org/w/index.php?title=2016_Winter_Project_Week/Projects/AIMInteroperability&oldid=91809"