CTSC:ARRA.061510

Back to CTSC:ARRA supplement

Agenda

• mi2b2 installation update
• preparation for advisory board meeting.

Harvard Catalyst Medical Informatics group Meeting Minutes June 8, 2010

In attendance:

• Shawn Murphy
• Bill Wang
• Cynthia Lee
• Steve Pieper
• Yong Gao
• Chris Herrick
• Wendy Plesniak
• Darren Sack
• Charles McGow
• Valerie Humblet
• Jesse Wei
• Mark Anderson (by phone)
• Carl (by phone)

Meeting Minutes

• mi2b2 STAR-D site installation update:
  • Progress: able to retrieve image to middle layer using cmove, upload to file repository -
  • next phase: taking user interface design and working logic into that new design.
  • talked with Mike Darcy at USC about what they're doing. They are using dcm4chee as a caching mechanism -- problem is that there is no delete command for dcm4chee... (but this exists on the console, so Steve, Chris feel this functionality must be there somewhere?)
  • Discuss another tool called "PixelMed"
  • Steve also describes dcmtk.
  • (Sketchy notes while I was getting network set up -- can Chris update these with more detail?)

• advisory board meeting preparation
  • want to present where we are with each site
  • how close are we to being able to deliver
  • what are our plans for the next six months.
  • Shawn wants to be able to say we are only moving test images for the next six months during testing.
  • These are real patients, all modalities, move things over to XNAT.
  • We will not be supporting an actual study at this point -- just in testing phase.
  • Collaborations with WashU: XNAT people are off preparing their example for how to receive images from mi2b2 STAR-D using webservices.
    • Their example will tell us how to describe image data of interest using an xml wrapper
    • log in and be authenticated.
    • upload it using webservices API (this should be pretty close.
    • send our team the play-by-play 'how-to' documentation.
  • How will mi2b2 and XNAT coordinate authentication?
    • STAR-D has images. May want to send them to Project A, Project B, or Project C on XNAT.
    • STAR-D has an administrative password for XNAT. It will use that admin password to comm with XNAT.
    • STAR-D will request a sessionID giving user name and password: XNAT will give access to any project with compatible permissions.
  • Keeping an Audit Trail: Should we generate an audit trail that lists
    • who accessed,
    • what data was retreived and
    • and where it went?
  • No UI issues yet for the advisory board.

• UI design and concepts