CTSC:ARRA.040511 - Revision history

RandyGollub at 20:33, 11 April 2011

2011-04-11T20:33:49Z

Valerie.humblet at 19:35, 11 April 2011

2011-04-11T19:35:27Z

Valerie.humblet at 15:54, 5 April 2011

2011-04-05T15:54:07Z

Valerie.humblet at 15:37, 5 April 2011

2011-04-05T15:37:45Z

Valerie.humblet at 15:30, 5 April 2011

2011-04-05T15:30:40Z

Valerie.humblet at 15:09, 5 April 2011

2011-04-05T15:09:39Z

Valerie.humblet at 15:06, 5 April 2011

2011-04-05T15:06:19Z

Valerie.humblet at 14:53, 5 April 2011

2011-04-05T14:53:14Z

Valerie.humblet: Created page with 'Back to CTSC:ARRA supplement

== Harvard Catalyst Medical Informatics group Meeting Minutes April 5, 2011 == In attendance: * Bill Wang * Valerie Humblet * Yong Ga…'

2011-04-05T14:50:44Z

Created page with 'Back to CTSC:ARRA supplement <br> <br> == Harvard Catalyst Medical Informatics group Meeting Minutes April 5, 2011 == In attendance: * Bill Wang * Valerie Humblet * Yong Ga…'

New page

Back to [[CTSC:ARRA supplement]]
<br>
<br>
== Harvard Catalyst Medical Informatics group Meeting Minutes April 5, 2011 ==

In attendance:
* Bill Wang
* Valerie Humblet
* Yong Gao
* Chris Herrick
* Shawn Murphy
* Steve Pieper
* Bill Tellier
* Darren Sack
* Bill Hanlon
* Alex Zeitsev
* Ron Kikinis

=== mi2b2 software update ===

@@ Line 15: / Line 15: @@
 * Alex Zeitsev
 * Bill Hanlon (phone)
-* Katie Andriole (phone)
+* Kathy Andriole (phone)
 * Mark Anderson (phone)
@@ Line 22: / Line 22: @@
 *Continue working on multi PACS. Bill and Chris worked out interaction with UI, need to pass back and forward institutions
-*  Working on getting BWH up and running. Katie said that it is fine to have the server in Needham.
+*  Working on getting BWH up and running. Kathy said that it is fine to have the server in Needham.
 * Started options for encryption-decryption of images. Dave looked at what is supported through image J. DICOM images should work fine, offer format must be tested.
 * Baby brain project at MGH: Bill satisfied with testing, he identified a couple of issues to be fixed.
 **Structured reports are still missing, they don't show up in the move. One thing to do is to check the format of those reports, maybe they are pdf, maybe they are text only in DICOM.
-**Time out issue: how we processed images now is c-move initiated, we wait for response and check if we got the right images. If the initiator does not get a response under 375 sec, the connection is dropped. It seems that PACS still send the images but it is not synchronized. The team is changing the logics and put together a monitoring progress to send a message that an initiation was created.
+**Time out issue: how we processed images now is c-move initiated, we wait for response and check if we got the right images. If the initiator does not get a response under 375 sec, the connection is dropped. It seems that PACS still send the images but it is not synchronized. The team is changing the logic and will put together a monitoring progress to send a message that an initiation was created.
 ===Planning for upcoming months===
@@ Line 34: / Line 34: @@
 ** User is distributed the mi2b2 workbench. Must be ready to run on PC and MAC. We are assuming the it is inside firewall, on approved clients.
 ** mi2b2 server component that is running the mi2b2 cell
-** i2b2 server: project management server. This component will communicate directly with the user. Each time for every detailed request, it will be a new project created, that project will be enabled with a list of MRN  known by the project manager. At Partners there is a define request for data, it is defined by a specific set of patients. At CHB it also has to be project based, they will need a similar structure.
+** i2b2 server: project management server. This component will communicate directly with the user. Each time for every detailed request, it will be a new project created, that project will be enabled with a list of MRN  known by the project manager. At Partners there is a defined request for data, it is defined by a specific set of patients. At CHB it also has to be project based, they will need a similar structure.
-** Once they have the list of MRN, they go to the mi2b2 server to request the images. Images will be send to the mi2b2 cache then send back to the user's image location (they can store it where they want: local drive, server). We could set up the workbench so it does the move of the images. Users need to move the data to the specific location because we don't want the cache to get jammed. They must specify a location that has enough disk space for the images. If there is too much traffic, cache management will be crucial. Images will be encrypted as long as they stay in the temporary space then be unencrypted when sent in the specified location.
+** Once they have the list of MRNs, they go to the mi2b2 server to request the images. Images will be sent to the mi2b2 cache then sent back to the user's image location (they can store it where they want: local drive, server). We could set up the workbench so it does the move of the images. Users need to move the data to the specific location because we don't want the cache to get jammed. They must specify a location that has enough disk space for the images. If there is too much traffic, cache management will be crucial. Images will be encrypted as long as they stay in the temporary space then be unencrypted when sent to the specified location.

← Older revision		Revision as of 19:35, 11 April 2011
Line 18:		Line 18:
	* Mark Anderson (phone)		* Mark Anderson (phone)

−
−	* Ron Kikinis
−	* Yong Gao

	=== mi2b2 software update ===		=== mi2b2 software update ===

@@ Line 38: / Line 38: @@
 ** mi2b2 server component that is running the mi2b2 cell
 ** i2b2 server: project management server. This component will communicate directly with the user. Each time for every detailed request, it will be a new project created, that project will be enabled with a list of MRN  known by the project manager. At Partners there is a define request for data, it is defined by a specific set of patients. At CHB it also has to be project based, they will need a similar structure.
-** Once they have the list of MRN, they got to the mi2b2 server to request the images. Images will go back to the user's image location (they can store it where they want: local drive, server). The vision is that users can put anything they want into the workbench.
+** Once they have the list of MRN, they go to the mi2b2 server to request the images. Images will be send to the mi2b2 cache then send back to the user's image location (they can store it where they want: local drive, server). We could set up the workbench so it does the move of the images. Users need to move the data to the specific location because we don't want the cache to get jammed. They must specify a location that has enough disk space for the images. If there is too much traffic, cache management will be crucial. Images will be encrypted as long as they stay in the temporary space then be unencrypted when sent in the specified location.

@@ Line 37: / Line 37: @@
 ** User is distributed the mi2b2 workbench. Must be ready to run on PC and MAC. We are assuming the it is inside firewall, on approved clients.
 ** mi2b2 server component that is running the mi2b2 cell
-** I2b2 server: project management server. This component will communicate directly with the user. Each time for every detailed request, it will be a new project created, that project will be enabled with a list of MR numbers known by the project manager. At Partners there is a define request for data, it is defined by a specific set of patients. At CHB it also has to be project based, they will need a similar structure.
+** i2b2 server: project management server. This component will communicate directly with the user. Each time for every detailed request, it will be a new project created, that project will be enabled with a list of MRN  known by the project manager. At Partners there is a define request for data, it is defined by a specific set of patients. At CHB it also has to be project based, they will need a similar structure.

@@ Line 16: / Line 16: @@
 * Bill Hanlon (phone)
 * Katie Andriole (phone)
@@ Line 23: / Line 24: @@
 === mi2b2 software update ===
-* Past week lot of moving pieces:
+*Continue working on multi PACS. Bill and Chris worked out interaction with UI, need to pass back and forward institutions
-** Continue working on multi PACS. Bill and Chris worked out interaction with UI, need to pass back and forward institutions
+*  Working on getting BWH up and running. Katie said that it is fine to have the server in Needham.
-** Working on getting BWH up and running. Katie said that it is fine to have the server in Needham.
+* Started options for encryption-decryption of images. Dave looked at what is supported through image J. DICOM images should work fine, offer format must be tested.
-** Started options for encryption-decryption of images. Dave looked at what is supported through image J. DICOM images should work fine, offer format must be tested.
+* Baby brain project at MGH: Bill satisfied with testing, he identified a couple of issues to be fixed.
-** Baby brain project at MGH: Bill satisfied with testing, he identified a couple of issues to be fixed.
+**Structured reports are still missing, they don't show up in the move. One thing to do is to check the format of those reports, maybe they are pdf, maybe they are text only in DICOM.
-***Structured reports are still missing, they don't show up in the move. One thing to do is to check the format of those reports, maybe they are pdf, maybe they are text only in DICOM.
+**Time out issue: how we processed images now is c-move initiated, we wait for response and check if we got the right images. If the initiator does not get a response under 375 sec, the connection is dropped. It seems that PACS still send the images but it is not synchronized. The team is changing the logics and put together a monitoring progress to send a message that an initiation was created.
-***Time out issue: how we processed images now is c-move initiated, we wait for response and check if we got the right images. If the initiator does not get a response under 375 sec, the connection is dropped. It seems that PACS still send the images but it is not synchronized. The team is changing the logics and put together a monitoring progress to send a message that an initiation was created.

@@ Line 10: / Line 10: @@
 * Shawn Murphy
 * Steve Pieper
-* Vincent
+* Vincent Roch
 * Darren Sack
 * Bill Hanlon (phone)
 * Ron Kikinis
 * Yong Gao
 === mi2b2 software update ===