CTSC:ARRA.101309 - Revision history

Valerie.humblet: /* Harvard Catalyst Medical Informatics group Meeting Minutes October 13, 2009 */

2009-10-19T14:42:32Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 13, 2009

2009-10-16T02:46:25Z

Use case 2

2009-10-16T02:45:29Z

Use case 1

2009-10-16T02:43:23Z

Uses cases

2009-10-16T02:43:14Z

Uses cases

2009-10-16T02:42:52Z

Discussion

2009-10-16T02:31:33Z

2009-10-16T02:19:38Z

2009-10-16T02:12:11Z

Use case 2

2009-10-16T02:05:52Z

Use case 2

@@ Line 17: / Line 17: @@
 * Shawn Murphy
 * Diane Keogh
-* Mike Mendez
+* Mike Mendis
 * Steve Pieper
 * Richard Robertson

@@ Line 54: / Line 54: @@
 * In general, Osirix can connect directly to the PACS, it just needs to be configured the right way.
 * Problem with heavy download: what happens if a PI decides to download 6,000 images?
-** As Shawn mentioned, we learned that at BWH and CHB, Pis are able to get request through the PACS, it is a good thing but we have to make sure it does not bring down the system.
+** As Shawn mentioned, we learned that at BWH and CHB, Pi's are able to get request through the PACS, it is a good thing but we have to make sure it does not bring down the system.
 ** At CHB some PI's tried before and of course it crashed the system.
 ** At BWH the workflow is controlled.

@@ Line 42: / Line 42: @@
 ** At CHB, surgeon have access to the PACS system and it is not reviewed by the Radiology Department. They search patient from their medical record number.
 * Red flag rose by Rick Robertson from CHB:
-** The Radiology department already has problems with groups who access medical imaging data without asking the radiologists. It leads to different groups working on the same subject without collaborating with each others. He feels that by making the retrieval of clinical data easier, we will make it even worst.
+** The Radiology department already has problems with groups who access medical imaging data without asking the radiologists. It leads to different groups working on the same subject without collaborating with each others. He feels that by making the retrieval of clinical data easier, it will make the situation even worst.
 <br>

← Older revision		Revision as of 02:43, 16 October 2009
Line 30:		Line 30:

	Randy presented a couple of [[media:usecasesARRA.ppt \| slides]] with different use cases. The goal of the meeting was to discuss the first ones and learn what are the mechanisms in place at each institutions.		Randy presented a couple of [[media:usecasesARRA.ppt \| slides]] with different use cases. The goal of the meeting was to discuss the first ones and learn what are the mechanisms in place at each institutions.
−

	===Use case 1===		===Use case 1===

← Older revision		Revision as of 02:43, 16 October 2009
Line 31:		Line 31:
	Randy presented a couple of [[media:usecasesARRA.ppt \| slides]] with different use cases. The goal of the meeting was to discuss the first ones and learn what are the mechanisms in place at each institutions.		Randy presented a couple of [[media:usecasesARRA.ppt \| slides]] with different use cases. The goal of the meeting was to discuss the first ones and learn what are the mechanisms in place at each institutions.

−	~~<br>~~

	===Use case 1===		===Use case 1===

@@ Line 64: / Line 64: @@
 == Discussion==
-* Shawn pointed that the group must be educated on how Radiology at the different institutions identify a specific image session. The accession number is a unique identifier but some image sessions might contain several accession numbers.
+* Shawn pointed that the group must be educated on how Radiology at the different institutions identify a specific image session. The accession number is an unique identifier but some image sessions might contain several accession numbers.
 * The goal of the mi2b2 project is to create an infrastructure that will make search easier but will have a layer of oversight and access control. To do so we want to build tools in parallel to what is already in place and respect each institutions way to do things so far.
-* Charles mentioned the query by imaging parameters. As Kathy noticed, it is not easily done with the commercial systems but the info are in the DICOM header. Right now building a new function to the PACS is out of the scope of the project. After a query (for example by patient ID and scan date), the data can be sent to XNAT where a more refined  search can be done.
+* For the next meeting:

@@ Line 30: / Line 30: @@
 Randy presented a couple of [[media:usecasesARRA.ppt | slides]] with different use cases. The goal of the meeting was to discuss the first ones and learn what are the mechanisms in place at each institutions.
 ===Use case 1===
@@ Line 44: / Line 46: @@
 ** The Radiology department already has problems with groups who access medical imaging data without asking the radiologists. It leads to different groups working on the same subject without collaborating with each others. He feels that by making the retrieval of clinical data easier, we will make it even worst.
 ===Use case 2===
@@ Line 57: / Line 60: @@
 ** At BWH the workflow is controlled.
-The goal of the mi2b2 project is to create an infrastructure that will make search easier but will have a layer of control so the clinical system will not be blocked. To do so we want to build tools in parallel to what is already in place and respect each institutions way to do things so far.
+<br>

@@ Line 50: / Line 50: @@
 * At CHB they can not do it without a review from Radiology. The request goes to the Informatics group. From the workstations, they can extract data from the PACS (as TIF for example).
-* At BWH the PI needs to request a CD to be burned, he must have an IRN approved and Radiology has to give its approval. When approved, the PI then gets DCOM access. They can use any approved DICOM viewer.
+* At BWH the PI needs to request a CD to be burned, he must have an IRB approved and Radiology has to give its approval. When the whole project is approved, the PI then gets DICOM access. He can use any approved DICOM viewer.
-* In general, Osirix can connect directly to PACS, it just needs to be configured the right way.
+* In general, Osirix can connect directly to the PACS, it just needs to be configured the right way.
 * Problem with heavy download: what happens if a PI decides to download 6,000 images?
-** At CHB they can try but it will most probably crash the system.
+** At CHB some PI's tried before and of course it crashed the system.
 ** At BWH the workflow is controlled.