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

From NAMIC Wiki
Jump to: navigation, search
Line 27: Line 27:
 
*Discussed topices mentioned under "approach" with Andriy
 
*Discussed topices mentioned under "approach" with Andriy
 
*Conclusion: Ultimately, DICOM is the way to go
 
*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)
 
*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)
 
|}
 
|}

Revision as of 12:16, 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!
  • 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)