CTSC:ARRA.100609 - Revision history

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

2009-10-15T17:55:33Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 6, 2009

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

2009-10-14T14:40:39Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 6, 2009

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

2009-10-14T14:40:16Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 6, 2009

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

2009-10-08T16:24:48Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 6, 2009

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

2009-10-08T16:24:30Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 6, 2009

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

2009-10-08T16:23:47Z

Harvard Catalyst Medical Informatics group Meeting Minutes October 6, 2009

RandyGollub at 15:27, 7 October 2009

2009-10-07T15:27:54Z

RandyGollub at 15:11, 7 October 2009

2009-10-07T15:11:30Z

RandyGollub at 14:55, 7 October 2009

2009-10-07T14:55:03Z

RandyGollub at 14:44, 7 October 2009

2009-10-07T14:44:53Z

@@ Line 23: / Line 23: @@
 * Shawn Murphy
 * Diane Keogh
-* Mike Mendez
+* Mike Mendis
 * Steve Pieper
 * Richard Robertson
@@ Line 95: / Line 95: @@
 <br>
-* Mike Mendez
+* Mike Mendis
-Mike is a software development engineer and a project manager for i2b2 who has many years of experience working with Shawn Murphy.
+Mike is a software development engineer and a project manager (team lead)  for i2b2 who has many years of experience working with Shawn Murphy.
 <br>

@@ Line 168: / Line 168: @@
 * Randy proposed to do a demonstration to teach what SHRINE and i2b2 can offer so far.
 * Ron suggested a discussion of what XNAT central has done.
 '''5. Key links'''
 [http://wiki.ihe.net/index.php?title=Cross_Enterprise_Document_Sharing IHE], [http://www.himss.org/ASP/index.asp HIMSS], [http://www.rsna.org/Publications/rsnanews/September-2009/RSNA2009_feature.cfm RSNA XDS]

← Older revision		Revision as of 14:40, 14 October 2009
Line 168:		Line 168:
	* Randy proposed to do a demonstration to teach what SHRINE and i2b2 can offer so far.		* Randy proposed to do a demonstration to teach what SHRINE and i2b2 can offer so far.
	* Ron suggested a discussion of what XNAT central has done.		* Ron suggested a discussion of what XNAT central has done.
		+
		+	'''5. Key links'''
		+
		+	[http://wiki.ihe.net/index.php?title=Cross_Enterprise_Document_Sharing IHE], [http://www.himss.org/ASP/index.asp HIMSS], [http://www.rsna.org/Publications/rsnanews/September-2009/RSNA2009_feature.cfm RSNA XDS]

@@ Line 147: / Line 147: @@
 '''3. Scope of work'''
-* Shawn gave a of the scope of the project highlighting key points where decisions need to be made by this group for how to achieve our goals.
+* Shawn gave a  [[media: XNAT_working_2.ppt |presentation]] of the scope of the project highlighting key points where decisions need to be made by this group for how to achieve our goals.
 ** One goal is to be able to request medical images from within i2b2 with an accession number. A key question is how to implement the request for the medical image data from the PACS.  For instance, software could be built to automatically send a request to the clinical PACS directly or their could be intermediary steps.  The extracted images are then envisioned to be sent to a Centralized repository (XNAT) likely one at each institution.
 ** After de-indentification, the images will be sent to XNAT (see www.XNAT.org).  XNAT is an open source software developed at Wash U by Dan Marcus. It is a system designed for clinical research and its has its own specifications (how the data need to be stored, data manipulation etc).

@@ Line 147: / Line 147: @@
 '''3. Scope of work'''
-* Shawn gave a [[media: XNAT_working.ppt |presentation]] of the scope of the project highlighting key points where decisions need to be made by this group for how to achieve our goals.
+* Shawn gave a of the scope of the project highlighting key points where decisions need to be made by this group for how to achieve our goals.
 ** One goal is to be able to request medical images from within i2b2 with an accession number. A key question is how to implement the request for the medical image data from the PACS.  For instance, software could be built to automatically send a request to the clinical PACS directly or their could be intermediary steps.  The extracted images are then envisioned to be sent to a Centralized repository (XNAT) likely one at each institution.
 ** After de-indentification, the images will be sent to XNAT (see www.XNAT.org).  XNAT is an open source software developed at Wash U by Dan Marcus. It is a system designed for clinical research and its has its own specifications (how the data need to be stored, data manipulation etc).

@@ Line 24: / Line 24: @@
 * Diane Keogh
 * Mike Mendez
-* Steve Piper
+* Steve Pieper
 * Richard Robertson
 * Stephan Voss
@@ Line 148: / Line 148: @@
 * Shawn gave a [[media: XNAT working.ppt |presentation]] of the scope of the project highlighting key points where decisions need to be made by this group for how to achieve our goals.
-** One goal is to be able to request medical images from within i2b2 with an accession number. A key question is how to implement the request for the medical image data from the PACS.  For instance, software could be built to automatically send a request to the clinical PACS directly or their could be intermediary steps.  The extracted images are then envisioned to be sent to a Centralized repository (XNAT) likely one at each institution. If a research PACS exists, it gets easier, again we don't want to put burden on the clinical staff, the people in charge of the clinical PACS etc.
+** One goal is to be able to request medical images from within i2b2 with an accession number. A key question is how to implement the request for the medical image data from the PACS.  For instance, software could be built to automatically send a request to the clinical PACS directly or their could be intermediary steps.  The extracted images are then envisioned to be sent to a Centralized repository (XNAT) likely one at each institution.
-** After de-indentification, the images will be sent to XNAT.  XNAT is an open source software developed at Wash U by Dan Marcus. It is a system designed for clinical research and its has its own specifications (how the data need to be stored, data manipulation etc).
+** After de-indentification, the images will be sent to XNAT (see www.XNAT.org).  XNAT is an open source software developed at Wash U by Dan Marcus. It is a system designed for clinical research and its has its own specifications (how the data need to be stored, data manipulation etc).
-** XNAT has a plug-in that can go into i2b2. So the PI who requests the images stays in i2b2 and views the images to do his research project. From that, he will derive new data that will then be put into the i2b2 database. So in the next 2 years, there will be no image data sharing yet, we will only share at the data level,
+** The architectures of XNAT and i2b2 are compatible such that the use of plug-ins will allow a PI who requests the images to stay in the i2b2 environment and still use the viewing capabilities of XNAT for his/her research project. Once the data are in the XNAT environment, the PI is free to analyze the data using whatever tools he/she requires.  Derived new data can then be entered into the i2b2 database. It is envisioned that over the next 2 years, there will be no image data sharing across institutions, we will we are working on an implementation that will support that in the future.
-* Ramin proposed an alternative that is a much simpler solution then replicate the data and it does not require the same need for security and privacy. This alternative would be to provide image viewer tools. For example in RPDR, one can find all the data for a patient. It would be great to add a link to be able to view the images. It is a simpler model that could take care of 70 % of the research needs.
+* Ramin proposed an alternative that he described as is a much simpler solution that does not require the same need for security and privacy. This alternative would be to provide image viewer tools linked to the PACS. For example in RPDR, one can find all the data for a patient. It would be great to add a link to be able to view the images. He proposed that this simpler model could take care of 70 % of the research needs.  There was spirited discussion illuminating the need for further clarification of the end goals of this project (see next week's agenda).
-** With such a solution came the problem of post-processing often used in research. If the PI is only able to view the images, he will not be able to use all the specialized research tools available.
+** The discussion logically evolved to the problem of determining the image post-processing needs most often used in research. If the PI is only able to view the images, he will not be able to use all the specialized research tools available.
-* Shawn defined 3 use cases for this project:
+* Shawn briefly defined 3 use cases for this project:
-** The researcher who tries to confirm a diagnosis. He can used a client based viewing tool.
+** The clinical researcher who tries to confirm a diagnosis. He can used a client based viewing tool.
-** The researcher who wants to view the images and evaluate them but don't need post-processing.
+** The clinical researcher who wants to view the images and evaluate them but doesn't need post-processing.
-** The researcher that we really want to serve: the one that has built a software to do post-processing automatically and needs the DICOM images to run his tool. XNAT does that very well.
+** The clinical researcher that we really want to serve: the one that wishes to apply non-clinical image analysis software to do post-processing automatically and needs the DICOM images. XNAT supports this final use case very well.
 <br>
-'''4. Conclusions'''
+'''4. Some conclusions'''
 * The goal of this project is not to create a mirror PACS.
-* Each institution should bring their own requirements to be able to know what the oversights are.
+* Each institution should bring to future meetings (with such a defined agenda) their own institutional requirements for oversights so we can assess similarities and differences.
-* There is a need to clarify who will determine access to imaging data when someone put a request. It is also important that people understand how data will be access and shared.
+* There is a need to clarify who can request what data and the process of how access to imaging data will be gained when someone places a request.
-* Each institution has to decide who is the right people that should attend the meetings. Having a defined agenda ahead of time would help making that decision, almost on a weekly basis.
+* Each institution has to decide who from their team should attend future meetings of this project. Having a defined agenda ahead of time would help making that decision, it is likely at this early stage senior leadership will be invaluable on almost on a weekly basis, but that will hopefully quickly evolve to more strategic work.
 * Randy proposed to do a demonstration to teach what SHRINE and i2b2 can offer so far.
 * Ron suggested a discussion of what XNAT central has done.

@@ Line 65: / Line 65: @@
 * Ramin Khorasani
-Ramin is vice chair of Radiology at BWH, he is also the Director of Medical Imaging Information Technology and the Director of the clinical PACS system. His goal is to support the research effort by making clinical data available easily as long as it does not disrupt the clinical practice.
+Ramin is Vice Chair of Radiology at BWH, he is also the Director of Medical Imaging Information Technology and the Director of the clinical PACS system.  His goal is to support the research effort by making clinical data available easily as long as it does not disrupt clinical practice.
 <br>
 * Shawn Murphy
-Shawn is the co-investigator on this supplement. He is also one of the Core Leaders for the i2b2 (Informatics for Integrating Biology and the Bedside) project. There are 3 i2b2 instances: BIDMC, CHB and Partners. So far i2b2 focus on a collection of codes from patient, the database is filled with informations from billing, labs etc but nothing from imaging. Being able to deliver images in the context of research is very important. <br>
+Shawn is the co-lead investigator on this supplement. He is also one of the Core Leaders for the i2b2 (Informatics for Integrating Biology and the Bedside) project. There are 3 i2b2 instances: BIDMC, CHB and Partners. So far all i2b2 efforts focus on collection of medical procedure, billing lab and other codes from patient care; however, the database completely lacks medical imaging data. He notes that medical imaging provides critically important phenotypic information.  <br>
-The infrastructure that will be build during the next 2 years must be scalable to big volume of data. There will be a need for flexibility, different departments at different institutions will have different workflows.
+The infrastructure that will be built during the next 2 years must be scalable to very large volumes of data (n = 10,000 +). He notes that there will be a need for flexibility, as the Radiology departments at each institution will have different workflows.
 <br>
 * Todd Perlstein
-Todd is a Fellow in Cardiovascular Medicine at BWH, his interest is on cardiac ultrasound. He is also a member of the Catalyst Imaging Consortium. He will provide the group with good test cases for clinical research. For example, his group has collected  a lot of cardiac US but so far has no access to it for secondary use.
+Todd is a Fellow in Cardiovascular Medicine at BWH, his interest is in cardiac ultrasound (US). He is also a member of the Catalyst Imaging Consortium. He will provide the group with good test cases for clinical research. For example, his group has collected  a lot of cardiac US data but so far he has no access to it for secondary research use.
 <br>
 * Alexander Zaitsev
-Alex is a member of the SPL lab at BWH. Right now he is working on supplement 3D Slicer and Extensible Neuroimaging Archive Toolkit (XNAT) with workflow management system. Provide integration and interoperability between 3D Slicer, XNAT Services and 3-rd party image processing applications and high performance computing systems. Implement it as within currently developed Structural Planning and Implementation in Neurological Exploration (SPINE) System.
+Alex is a member of the Surgical Planning Lab (SPL) lab at BWH. Right now he is working on supplementing the 3D Slicer software and Extensible Neuroimaging Archive Toolkit (XNAT) with a workflow management system. This capability will provide integration and interoperability between 3D Slicer, XNAT Services and 3-rd party image processing applications and high performance computing systems to enable the automatic image processing of very large data sets. The initial implementation of it is within the Structural Planning and Implementation in Neurological Exploration (SPINE) System deployed at BWH under the direction of Charles Guttmann.
 <br>
 *Stephan Voss
-Stefan Voss is a radiologist specialized in pediatric oncology at CHB. He is also a member of the Catalyst Imaging Consortium. He defines himself as an end-user of image data, he is involved in several large multi-centers clinical trials.
+Stefan Voss is a radiologist specialized in pediatric oncology at CHB. He is also a member of the Catalyst Imaging Consortium. He defines himself as an end-user of image data, he is involved in several large multi-center clinical trials that are part of the Children's Oncology Group (COG).  He has considerable experience with using image analysis and managements tools, many of which have not worked well.
 <br>
 * Richard Robertson
-Rick is the Clinical Radiologist-in-Chief and the Medical Director of Radiology Informatics at CHB. He wants to understand the scope of the project to make sure that the right representative from his institution attends the weekly meetings.
+Rick is the Clinical Radiologist-in-Chief and the Medical Director of Radiology Informatics at CHB. He wants to understand the scope of the project to make sure that the right representative from his institution attends the weekly meetings.  He will pay particular care to ensure proper oversight for accessing and moving the medical imaging data.
 <br>
 * Mike Mendez
-Mike is a software development engineer and a project manager for i2b2.
+Mike is a software development engineer and a project manager for i2b2 who has many years of experience working with Shawn Murphy.
 <br>
 * Ron Kikinis
-Ron is the founding Director of the Surgical Planning Laboratory at BWH. He has been doing full time research on image processing, 3D Slicer, Multi-centers studies (BIRN). <br>
+Ron is the founding Director of the Surgical Planning Laboratory at BWH. He has been doing full time research on image processing, 3D Slicer, multi-centers studies (such as BIRN) for many decades. <br>
-Research needs its own PACS, its own workflow. XNAT will fulfill a need for research because it is more flexible that the clinical PACS.
+Research needs its own PACS, its own workflow. XNAT will fulfill a need for research because it is more flexible than the clinical PACS.
 <br>
 * Yong Gao
-Yong is computer scientist working part-time or the Catalyst. He works towards data sharing across sites and is setting up XNAT instances at CHB and MGH.
+Yong is computer scientist working part-time for the Catalyst. He works towards data sharing across sites and is setting up XNAT instances at CHB and MGH.
 <br>
 * Wendy Plesniak.
-Wendy is a Research Fellow in the Surgical Planning Laboratory at BWH. She has a lot of expertise on interface design and mapping use cases with the technology.
+Wendy is a Research Fellow in the Surgical Planning Laboratory at BWH. She has a lot of expertise on interface design and mapping use cases to the technology.
 <br>
@@ Line 125: / Line 125: @@
 <br>
-* Steve Piper
+* Steve Pieper
-Steve is a medical image analyst, he is the founder of Isomics. That company provides specialized services to academic and business clients in the fields of software development, image analysis, and technical management with applications in medical research, product development, and manufacturing. He has a lot of experience in multi-institutions software venture. One of his main concern is to make sure that teh research work will not affect the clinical practice.
+Steve is a medical image analyst, he is the founder of Isomics. That company provides specialized services to academic and business clients in the fields of software development, image analysis, and technical management with applications in medical research, product development, and manufacturing. He has a lot of experience in multi-institutions software venture. One of his main concerns is to make sure that the research work will not affect clinical practice.
 <br>
 * Jesse Wei
-Jesse is a radiologist at BIDMC, he is also the director of informatics for the Radiology department. He is very interested by the possibility to integrate images with i2b2.
+Jesse is a radiologist at BIDMC, he is also the director of informatics for the Radiology department. He is very interested by the possibility to integrate images with i2b2 and sees the benefit of this project both locally for use by BIDMC faculty as well as more broadly.
 <br>
@@ Line 147: / Line 147: @@
 '''3. Scope of work'''
-* Shawn gave a [[media: XNAT working.ppt |presentation]] of the scope of the project.
+* Shawn gave a [[media: XNAT working.ppt |presentation]] of the scope of the project highlighting key points where decisions need to be made by this group for how to achieve our goals.
-** One goal is to be able to request images in i2b2 with an accession number. Then a request could be forwarded to the clinical PACS directly or the images can be send to a repository (XNAT). If a research PACS exists, it gets easier, again we don't want to put burden on the clinical staff, the people in charge of the clinical PACS etc.
+** One goal is to be able to request medical images from within i2b2 with an accession number. A key question is how to implement the request for the medical image data from the PACS.  For instance, software could be built to automatically send a request to the clinical PACS directly or their could be intermediary steps.  The extracted images are then envisioned to be sent to a Centralized repository (XNAT) likely one at each institution. If a research PACS exists, it gets easier, again we don't want to put burden on the clinical staff, the people in charge of the clinical PACS etc.
-** After deindentification, the images will be sent to XNAT. XNAT is an open source software developed at Wash U by Dan Marcus. It is a system designed for clinical research and its own specificities (how the data need to be stored, data manipulation etc).
+** After de-indentification, the images will be sent to XNAT.  XNAT is an open source software developed at Wash U by Dan Marcus. It is a system designed for clinical research and its has its own specifications (how the data need to be stored, data manipulation etc).
 ** XNAT has a plug-in that can go into i2b2. So the PI who requests the images stays in i2b2 and views the images to do his research project. From that, he will derive new data that will then be put into the i2b2 database. So in the next 2 years, there will be no image data sharing yet, we will only share at the data level,
 * Ramin proposed an alternative that is a much simpler solution then replicate the data and it does not require the same need for security and privacy. This alternative would be to provide image viewer tools. For example in RPDR, one can find all the data for a patient. It would be great to add a link to be able to view the images. It is a simpler model that could take care of 70 % of the research needs.

@@ Line 39: / Line 39: @@
 * Randy welcomed all the participants and gave a very brief introduction about the ARRA supplement. The Administrative Supplement award was received on September 30, the official dates of the project are 9/24/09- 9/23/11.
 * Lee Nadler, as PI of the Harvard Catalyst is also the PI of this supplement.  Bruce Rosen, as Director of the Catalyst Imaging Consortium and a visionary in the development of medical imaging informatics is also providing leadership for the project.
-* Shawn Murphy and Randy Gollub are co-leading the operational aspects of the effort.  Shawn will be the lead on the technical design.  Randy will be in charge of all the administrative tasks.  She is currently working with each site to establish their subcontracts. The first thing that Shawn and Randy did when the funding of the supplement was announced was to offer a full time job to a Computational Engineer that has many years of experience in research imaging data management. He was recently interviewed in person by the full Catalyst Imaging Consortium membership who gave him their strong endorsement.  He will join the team in a couple of months.
+* Shawn Murphy and Randy Gollub are co-leading the operational aspects of the effort.  Shawn will be the lead on the technical design.  Randy will be in charge of all the administrative tasks.  She is currently working with each site to establish their subcontracts. The first thing that Shawn and Randy did when the funding of the supplement was announced was to offer a full time job to a Computational Engineer that has many years of experience in research imaging data management. He was recently interviewed in person by the full Catalyst Imaging Consortium membership who gave him their strong endorsement.  He will join the team in a couple of months after completing the transition of his current responsibilities to others and moving to Boston.
 <br>
@@ Line 50: / Line 50: @@
 * Randy Gollub
-Randy is from MGH (neuroimaging), she is the co-director of the Catalyst Imaging Consortium and the co-Investigator on this ARRA supplement.
+Randy is from MGH (Psychiatry and Radiology), she is the co-director of the Catalyst Imaging Consortium and the co-Investigator on this ARRA supplement.  Her motivation to complete the aims of this project is to enable some of the wealth of clinical imaging data accessible for secondary use for research.  Randy brings expertise in the design, acquisition and analysis of human neuroimaing studies and in the domain of human subject protections, valuable since the issue of patient privacy will require a lot of effort in this project.
 <br>
 * Diane Keogh
-Diane is the Director of Research Computing at Partners HealthCare. She is usually not involved in individual projects but will provide support to this group.
+Diane is the Director of Research Computing at Partners HealthCare. She is usually not involved in individual projects but, since she finds this particular project so compelling and important, she will provide her direct support to this group.
 <br>