CTSC:ARRA.080911

From NAMIC Wiki
Revision as of 15:30, 9 August 2011 by RandyGollub (talk | contribs) (Created page with 'Back to CTSC:ARRA supplement <br> <br> == Harvard Catalyst Medical Informatics group Meeting Minutes August 9, 2011 == In attendance: * Bill Wang * David Wang * Shawn Murp…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < CTSC:ARRA.080911

Back to CTSC:ARRA supplement

Harvard Catalyst Medical Informatics group Meeting Minutes August 9, 2011

In attendance:

  • Bill Wang
  • David Wang
  • Shawn Murphy
  • Vincent Roch
  • Randy Gollub
  • Valerie Humblet
  • Bill Tellier
  • Yong Gao
  • Steve Pieper
  • Darren Sack
  • Alex Zeitsev
  • Bill Hanlon (phone)
  • Kathy Andriole (phone)

mi2b2 software update

  • Bill reports that mi2b2 Version 6 is now deployed at MGH on the production server.
  • The BWH servers are still not deployed, hope to do this by end of August. As an interim step we might be able to temporarily reconfigure the MGH servers to work with the BWH PACS. Will need to work with the BWH team to enable this.
  • No word yet from BIDMC or CHB.

Future planning

It is now time to:

  1. develop training materials (manuals, tutorials, etc)
  2. develop our maintanence strategy
  3. choose a website for deployment (leaning towards the i2b2 Community wiki)
  4. plan peer reviewed article(s); choose target journal(s) Journal of Digital Imaging (JDI) is one option.
  5. schedule next presentation to Advisory Board. Shawn suggests doing this 3 times, once each for Partners, BIDMC and CHB. At each meeting invite the mi2b2 leaders, Advisory Board members and representative SVPs from each institution. Site leaders to help do the organization. Randy will work on this.

Training Materials

Suggest the following components:

  1. Installation guide
  2. Architecture
  3. Messaging guide (for integration with other i2b2 cells)
  4. User & Project Manager documentation (including how to query the RPDR/i2b2 Access database to the MRNs and accession numbers)
  5. Administrator (top level across all projects) documentation (e.g. SQL query to retrieve audit logs, access information)