CTSC:ARRA.041012

From NAMIC Wiki
Revision as of 19:42, 10 April 2012 by RandyGollub (talk | contribs) (Created page with 'Back to CTSC:ARRA supplement <br> <br> == Harvard Catalyst Medical Informatics group Meeting Minutes April 10, 2012 == In attendance: * David Wang * Bill Wang * Shawn Murph…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < CTSC:ARRA.041012

Back to CTSC:ARRA supplement

Harvard Catalyst Medical Informatics group Meeting Minutes April 10, 2012

In attendance:

  • David Wang
  • Bill Wang
  • Shawn Murphy
  • Randy Gollub
  • Chris Herrick
  • Steve Pieper
  • Jesse Wei (phone)
  • Kathy Andriole (phone)

Agenda

  1. mi2b2 software update
  2. manuscript
  3. To Do List

mi2b2 software update

  • In the newly designed workflow for the mi2b2 software version 1.2 that allows one or more XNAT instances and/or DICOM receivers such as OSIRIX-MD to be specified per project. We can now move images from a PACS to our mi2b2 server cache and then to the user's desired location(s). Uses DICOM commands not through REST calls.
  • User interface design is now the focus of software development in version 1.2. Goal is to enable users to be able to view the images that they have downloaded into their own specified location and have the information persist from session to session.

manuscript

  • No progress in past 4 weeks. Will be primary focus of next meeting. ;)

To Do List

  • Discussed the idea of integrating our mi2b2 software with the Clinical Trial Processor (CTP). CTP is a Java based software tool developed by the CaBIG community comprised of a DICOM listener that can be configured to anonymize/de-identify files and a DICOM server to store the images. Shawn and Chris will look into this.
  • In past meetings we discussed the idea that at MGH (and perhaps other of our sites) that we might query and retrieve for images from their Radiology Department archives rather than the Clinical PACS. This needs to be further discussed in future meetings since it might be a much more stable architecture (fewer upgrades, etc) and also might allow for increased access as mi2b2 grows.