CTSC:ARRA.041310

Back to CTSC:ARRA supplement

Agenda

• Implementation of retrieve portion of mi2b2 - hardware solutions
• Progress update

Harvard Catalyst Medical Informatics group Meeting Minutes April 13, 2010

In attendance:

• Shawn Murphy
• Kathy Andriole (phone)
• Mike Clyne (phone)
• Wendy Plesniak
• Randy Gollub
• Chris Herrick
• Bill Telier
• Steve Pieper
• Dan Marcus (phone)
• Paul Lamonica
• Mark Anderson
• Darren Sack
• Alex Zeitsev
• Yong Gao

?

• Jesse Wei

Meeting Minutes

1. Chris reviewed the minimum specs for a server to communicate between the i2b2 STAR-D software and the local PACS.
   

2 GHZ processor
2 GB RAM
40 GB free space

Software (when we deploy):

Windows XP SP1 or CentOS (other Linux version possible)
JDK 6.0
JBoss 4.2.2
Apache Ant 1.6.5
Apache Axis2 1.1
Oracle 10g Express Edition (for Linux Servers) or Sql Server 2005 Express Edition (for Windows)
Server needs to be connected to the internet with a fixed IP address, inside firewall. Can be Linux or Windows (prefer XP can be 7).

1. Level of Service discussion
   

Shawn and Chris envision that

1. Chris Herrick reported on his team's progress over the past week:
   
2. Update from each site as to what configuration and how long before server will be in place. (CHB) Paul and Bill will talk to Charles, but think they might be ready now! (BIDMC) Jesse is planning to apply for use of server equipment centrally (Windows 7) will need sign off from Radiology. He estimates that it will take ~ month to be ready. (BWH) Kathy is likely to go WindowsXP given that she will place an order, will need specs from Chris, see Action Item below. (MGH) Darren discussed with his team and decided to go with a new laptop, but will likely be WindowsXP. He is
3. Security Policy. And that we ensure that are fully compliant with it. (encrypt development server laptops?; what ports are used; )
4. Ron also suggests that we articulate a "Level of Service" statement for the package. (include who pays what costs?)(what we offer to users)(what we offer to Department hosts, what we expect from them) May need to be staged. Now in development phase, business hours with 2 day turnaround is fine, when it is enterprise, that is not likely. We need power. Replacements within 2 days. Who to contact if there is a problem. Protocols for problems, (FAQ page).

Action Items

1. Randy, Chris & Shawn to outline draft Security Policy to review for next meeting
2. Use next meeting to outline Level of Service document together