sorry, I made that in consultation with Ashok. We were going to start putting the materials there when they came in. thanks for filling it out.
________________________________ James C McClay, MS, MD, FACEP Associate Professor, Emergency Department Chair, Biomedical Informatics Graduate Program University of Nebraska Medical Center Omaha, NE 68198-1150 [email protected]<mailto:[email protected]> ________________________________ From: Greater Plains Collaborative Software Development [[email protected]] on behalf of Dan Connolly [[email protected]] Sent: Sunday, February 16, 2014 4:52 PM To: [email protected] Subject: Re: i2b2 hardware infrastructure I see Jim M. made a link to a wiki page to collect hardware info. I had done that too, earlier. Neither of us had actually created the page, though... so just did: HardwareSizing<http://informatics.gpcnetwork.org/trac/Project/wiki/HardwareSizing> (I like WikiWord links). I added pointers to the KUMC hardware info. Others are welcome to do likewise. -- Dan ________________________________ From: Dan Connolly Sent: Thursday, February 13, 2014 10:34 AM To: Mudgapalli, Ashok; [email protected] Subject: RE: i2b2 hardware infrastructure I suggest sending your request to gpc-dev with an appropriate subject line. You might start a page in the gpc wiki<http://informatics.gpcnetwork.org/trac/Project/wiki> and suggest people contribute there, though there's a trade-off between email, where you get instant notification but if you want the results aggregated, you have to do it yourself vs wiki, where the results are naturally aggregated but you have to poll for progress. You might also give some motivation behind the request. -- Dan ________________________________ From: Mudgapalli, Ashok [[email protected]] Sent: Thursday, February 13, 2014 10:13 AM To: Dan Connolly; [email protected] Subject: RE: tools for near-realtime meeting notes Hello Dan, I would like to get the information about I2B2 hardware infrastructure information from all participating institutions. How should I proceed with this request? Thanks. Ashok The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.
