Difference between revisions of "CTSC:ARRA.041310"

From NAMIC Wiki
Jump to: navigation, search
(Created page with 'Back to CTSC:ARRA supplement <br> '''Agenda''' * Implementation of retrieve portion of mi2b2 - hardware solutions * Progress update == Harvard Catalyst Medical Informatics…')
 
Line 30: Line 30:
 
'''Meeting Minutes'''
 
'''Meeting Minutes'''
 
<br>
 
<br>
−
# Chris reviewed the minimum specs for a server to communicate between the i2b2 STAR-D software and the local PACS. <br>
+
Chris reviewed the minimum specs for a server to host the i2b2 STAR-D software that would communicate with the local PACS. <br>
 
<br>
 
<br>
 
2 GHZ processor <br>
 
2 GHZ processor <br>
Line 44: Line 44:
 
Apache Axis2 1.1 <br>
 
Apache Axis2 1.1 <br>
 
Oracle 10g Express Edition (for Linux Servers) or Sql Server 2005 Express Edition (for Windows) <br>
 
Oracle 10g Express Edition (for Linux Servers) or Sql Server 2005 Express Edition (for Windows) <br>
−
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).
+
Connected to the intranet with a fixed IP address, inside firewall with PACS access but no access to outside world.   
−
# Level of Service discussion <br>
+
# "Level of Service" statement for mi2b2.  All project personnel will need to be added to their site's i2b2 IRB development protocol to cover our work on this project.  Shawn is the PI for this IRB at MGH and BWH.  He will add Kathy, Mike, Darren, Tom, and Steve at MGH and BWH.  Shawn will send the text needed for this amendment to Griffin Webber who is PI at BIDMC to add Jesse.  Who at CHB is the analogous person?  Idea of having key personnel (e.g. Chris Herrick) at MGH site from this project would apply for VPN privileges at BIDMC and CHB to that he would have access to all four sites to provide support. Host site can "turn it off" at any time if anything goes wrong.
−
Shawn and Chris envision that  
+
# Chris Herrick reported on his team's progress over the past week.  The i2b2 Star-D software is up and running in test mode.  Now working on "packaging" it so it is easy to deploy at all sites.  Will contain a miniature i2b2 version with only those components that are needed for this project.  <br>
−
# Chris Herrick reported on his team's progress over the past week: <br>
+
# Update from each site as to what configuration and how long before server will be in place.  (CHB) Paul and Bill have a laptop computer already.  (BIDMC) Jesse is applying for sign off from Radiology for project as a whole.  Hardware solution will await this team's input.  (BWH) Kathy is going to order a brand new WindowsXP desktop that she will order immediately and deploy it at the Kent Street facility computer room at the Center for Evidence Based Imaging (CEBI). (MGH) Darren discussed with his team and decided to go with a new laptop to be located on his desk, but will likely be WindowsXP. He also has to apply for sign off from Radiology for project as a whole.   
−
# 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
 
 
# Security Policy.  And that we ensure that are fully compliant with it. (encrypt development server laptops?; what ports are used; )
 
# Security Policy.  And that we ensure that are fully compliant with it. (encrypt development server laptops?; what ports are used; )
−
# 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).
+
# ARRA progress reports were just due.
 +
# (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'''
 
'''Action Items'''

Revision as of 15:30, 13 April 2010

Home < 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
Chris reviewed the minimum specs for a server to host the i2b2 STAR-D software that would communicate with 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)
Connected to the intranet with a fixed IP address, inside firewall with PACS access but no access to outside world.

  1. "Level of Service" statement for mi2b2. All project personnel will need to be added to their site's i2b2 IRB development protocol to cover our work on this project. Shawn is the PI for this IRB at MGH and BWH. He will add Kathy, Mike, Darren, Tom, and Steve at MGH and BWH. Shawn will send the text needed for this amendment to Griffin Webber who is PI at BIDMC to add Jesse. Who at CHB is the analogous person? Idea of having key personnel (e.g. Chris Herrick) at MGH site from this project would apply for VPN privileges at BIDMC and CHB to that he would have access to all four sites to provide support. Host site can "turn it off" at any time if anything goes wrong.
  2. Chris Herrick reported on his team's progress over the past week. The i2b2 Star-D software is up and running in test mode. Now working on "packaging" it so it is easy to deploy at all sites. Will contain a miniature i2b2 version with only those components that are needed for this project.
  3. Update from each site as to what configuration and how long before server will be in place. (CHB) Paul and Bill have a laptop computer already. (BIDMC) Jesse is applying for sign off from Radiology for project as a whole. Hardware solution will await this team's input. (BWH) Kathy is going to order a brand new WindowsXP desktop that she will order immediately and deploy it at the Kent Street facility computer room at the Center for Evidence Based Imaging (CEBI). (MGH) Darren discussed with his team and decided to go with a new laptop to be located on his desk, but will likely be WindowsXP. He also has to apply for sign off from Radiology for project as a whole.
  4. Security Policy. And that we ensure that are fully compliant with it. (encrypt development server laptops?; what ports are used; )
  5. ARRA progress reports were just due.
  6. (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
Retrieved from "https://www.na-mic.org/w/index.php?title=CTSC:ARRA.041310&oldid=51417"