CTSC:ARRA.011210 - Revision history

Valerie.humblet: /* i2b2 to XNAT to DICOM worflow */

2010-01-19T15:54:22Z

i2b2 to XNAT to DICOM worflow

RandyGollub: /* i2b2 to XNAT to DICOM worflow */

2010-01-19T05:08:16Z

i2b2 to XNAT to DICOM worflow

RandyGollub: /* i2b2 to XNAT to DICOM architecture */

2010-01-19T05:04:31Z

i2b2 to XNAT to DICOM architecture

Valerie.humblet at 20:55, 15 January 2010

2010-01-15T20:55:12Z

Valerie.humblet: /* Project components */

2010-01-15T20:49:29Z

Project components

Valerie.humblet: /* Harvard Catalyst Medical Informatics group Meeting Minutes January 12, 2010 */

2010-01-15T20:49:17Z

Harvard Catalyst Medical Informatics group Meeting Minutes January 12, 2010

Valerie.humblet: /* i2b2 to XNAT to DICOM worflow */

2010-01-15T20:48:41Z

i2b2 to XNAT to DICOM worflow

Valerie.humblet: /* i2b2 to XNAT to DICOM architecture */

2010-01-15T20:47:18Z

i2b2 to XNAT to DICOM architecture

Valerie.humblet: /* i2b2 to XNAT to DICOM worflow */

2010-01-15T20:45:07Z

i2b2 to XNAT to DICOM worflow

Valerie.humblet: /* Harvard Catalyst Medical Informatics group Meeting Minutes January 12, 2010 */

2010-01-15T20:43:27Z

Harvard Catalyst Medical Informatics group Meeting Minutes January 12, 2010

@@ Line 46: / Line 46: @@
 <br>
-=== i2b2 to XNAT to DICOM worflow===
+=== i2b2 to XNAT to DICOM workflow===
 *Request is made from i2b2 client to look up:
-**By accession number: What are the nature of accessions for "studies" and "images" at the 4 sites
+**By accession number: What are the nature of accessions for "studies" and "images" at the 4 sites?
 **By patient: Assumed to always be a MRN
 ** i2b2 enforces that the PI is asking only for the studies he is allowed to see.

@@ Line 50: / Line 50: @@
 *Request is made from i2b2 client to look up:
 **By accession number: What are the nature of accessions for "studies" and "images" at the 4 sites
-**By patient: Assumed to always be and MRN
+**By patient: Assumed to always be a MRN
-** i2b2 enforce that the PI is asking only for the studies he is allowed to see.
+** i2b2 enforces that the PI is asking only for the studies he is allowed to see.
-** As we discussed last week, the access. # is mapped to the UID (very internal, one per image, they are part of the DICOM).
+** As we discussed last week, the accession # is mapped to the UID (very internal, one per image, they are part of the DICOM).
 <br>
 *A navigational client experience is made to identify a study or an image:
-** How can we give access to only a couple of studies and not the whole PACS: the (*) will serve as a gatekeeper and the throttle to let know that one can not access everything (ex: images from the last 5 years are OK, older no because it takes too long to get access and download).
+** How can we give access to only a couple of studies and not the whole PACS? Answer: The STAR software will serve as a gatekeeper and the throttle to limit access both in terms of when it can retrieve images and what images to retrieve (e.g. images from the last 5 years are OK, older no because it takes too long to get access and download).
 <br>

@@ Line 38: / Line 38: @@
 [[image:mi2b2.png]]
-*In the picture above, it is clear now that (*) will be an intermediary to the PACS and XNAT. i2b2 will not communicate directly with the PACS. Anything build in i2b2 will communicate with (*) and then (*) will communicate with the PACS.
+*In the picture above, it is clear now that the software to be developed by this project, represented by the STAR icon in the figure, will be an intermediary between the PACS and XNAT. i2b2 will not communicate directly with the PACS. Anything built in i2b2 will communicate with STAR and then STAR will communicate with the PACS.
-* i2b2 structure is made with projects and users. Every message from i2b2 always includes who the user is and information about the project (IRB etc). We have to understand how to coordinate the user/project structure from i2b2 in XNAT. Randy mentioned that Dan Marcus has just been asked to support communication between i2b2 and XNAT.
+* i2b2 structure is organized by projects and users. Every message from i2b2 always includes who the user is and information about the project (IRB etc). We have to understand how to coordinate the user/project information structure from i2b2 with that of XNAT. Randy mentioned that Dan Marcus has just been asked to support communication between i2b2 and XNAT for another project at Emory University.
-* (*) will need to be able to log into XNAT and send the images to the right place. The most difficult part will probably to send back the new data from XNAT to i2b2.
+* STAR will need to be able to log into XNAT and send the images to the right place. The most difficult part will probably be to send back the new data from XNAT to i2b2.
-* patient: in i2b2 there is a structure to ensure that the access tho the HIPAA data is limited. There is a data management cell in i2b2 to deal with the medical record number (MRN).  (*) will need the MRN to retrieve data.
+* patient: in i2b2 there is a structure to ensure that the access to the HIPAA data is limited. There is a data management cell in i2b2 to deal with the medical record number (MRN).  STAR will need the MRN to retrieve data.
-* How is XNAT prepared to deal with MRN? According to Yong, XNAT does not allow you to stock any HIPAA controlled data.
+* How is XNAT prepared to deal with MRNs? According to Yong, XNAT does not allow you to store any HIPAA controlled data.
 * Each project will be formed around an IRB, then around a set of patients, then a set of users allowed to use the data associated with the project.
 <br>

@@ Line 4: / Line 4: @@
 '''Agenda'''
-# i2b2 to XNAT to DICOM workflow
+i2b2 to XNAT to DICOM architecture and workflow
 == Harvard Catalyst Medical Informatics group Meeting Minutes January 12, 2010 ==

@@ Line 28: / Line 28: @@
 ===Project components===
-** the software development part.
+* the software development part.
-** the department engagement (Randy is working on setting up meetings with the different institutions to work on policy issues).
+* the department engagement (Randy is working on setting up meetings with the different institutions to work on policy issues).
-** the studies: we need the science, it is essential to get a couple of publications to validate the project.
+* the studies: we need the science, it is essential to get a couple of publications to validate the project.
 <br>

← Older revision		Revision as of 20:48, 15 January 2010
Line 62:		Line 62:
	** Would this be possible?		** Would this be possible?
	** The description is not always the best place to look for hint but for example one could look for bolus injection to make sure contrast agent was used.		** The description is not always the best place to look for hint but for example one could look for bolus injection to make sure contrast agent was used.
		+
		+	<br>
		+	* Transfer is specified (to be discussed at next meeting)
		+	** Target location
		+	** Set up XNAT to receive image
		+
		+	<br>
		+	*Request is queued (to be discussed at next meeting)
		+	**Log of transfer is available
		+	**Notification that transfer is complete is made