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

Revision as of 12:16, 7 January 2016

Objective	Approach and Plan	Progress and Next Steps
Evaluate AIM as standard for image annotations, in particular w.r.t. interoperability (example: Slicer / MeVisLab)	Try out AIM software Look at AIM support in 3D Slicer Check TID 1500 measurement template in DICOM SR and work in progress on harmonization of common AIM use cases through encoding as DICOM TID 1500 SR instances. Check PeerJ pre-print Estimate effort / plan further steps whether and how AIM could be supported in 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! 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)

@@ Line 27: / Line 27: @@
 *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!
 *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)
 |}