Difference between revisions of "CTSC:ARRA.071310"

From NAMIC Wiki
Jump to: navigation, search
(Created page with 'Back to CTSC:ARRA supplement <br> '''Agenda''' * Update * uxp and UI design: workflow analysis <br> == Harvard Catalyst Medical Informatics group Meeting Minutes July 13,…')
 
 
Line 20: Line 20:
 
* Randy Gollub
 
* Randy Gollub
 
* Jesse Wei
 
* Jesse Wei
* Bill Tellier or
+
* Bill Tellier
* Paul Lamonica
 
 
* Mark Anderson (phone)
 
* Mark Anderson (phone)
 
* Charles Mc Govern
 
* Alex Zeitsev
 
* Yong Gao
 
* Katie Andriole (phone)
 
  
 
<br>
 
<br>
Line 37: Line 31:
 
* Chris reports that the phase 2 software is now ready for deployment.  The MGH site will be first.  
 
* Chris reports that the phase 2 software is now ready for deployment.  The MGH site will be first.  
 
* BIDMC Radiology IT team project is still on waiting status and Jesse continues to monitor progress.  Most recent estimate of date for final review is August.
 
* BIDMC Radiology IT team project is still on waiting status and Jesse continues to monitor progress.  Most recent estimate of date for final review is August.
 +
 +
===Need to establish an appropriate repository for mi2b2 source code===
 +
* Discussed pros and cons of various options (continue as part of i2b2, make it part of CDash, set up another tool).  Long term goals are to have a software repository that can be open to the public, able to have contributions made from the community, and to completely protect all site specific information.  Plan is for Shawn to add Steve to the Partners i2b2 IRB so he can view source code and also learn about the i2b2 code repository.  After he reviews the situation he will come back to this group to to make a recommendation.
 +
 +
===Osirix===
 +
 +
* The question was raised as to whether Osirix, the most mature stand alone DICOM viewing tool (Mac only), would be of any use in the mi2b2 project.  Group sees some value in thinking about how to develop a mi2b2 to Osirix plug-in as a way of greatly enhancing the dissemination of our final product.  Will revisit this in the future.
  
 
=== Workflow analysis===
 
=== Workflow analysis===
Temp!
+
 
* Recap from last week presentation: there are 3 steps (site selection and finding patients; finding studies and destination selection; transfer and view )performed in series but an user will be able to log in and jump to any step depending on what he saved during his last session (what is savable? The scoutlist, the patient list, the study set, the individual images).  
+
* Discussed new revision based on input from last week now has 5 stages: 1. Select site/department; 2. Scout for information available on system using site-specific identifiers; 3. Form a "Study Set" to request; 4. Chose a Transfer destination and request studies; 5. Check transfer status & view transferred images.
* Scout list vs patient list: a scout list is a list of MRN that the user will type to see if they are in the system. He will get back a list of MRN found (the patient list, confirmed present at the site searched) vs not found.
+
* Is there a need for a scout study list? Yes, some people will already have a list of accession numbers that they want to refine into a study set. Investigators must be able to jump into step 2 (finding studies and destination selection), some of them might have used another mechanism than step 1 to get the accession numbers.
+
* Cynthia and Wendy have generated a list of questions about the specific details that can be learned by the automatic search functions to use in our filters. Jesse points to standard DICOM feature lists. He offered to share screen shots of the "drill down" query terms on his system.
* What is filtrable? Many people ask to retrieve images by date and MRN. Another filtering concept to consider is the modality.
 
* What is persistent? We want to keep a clean break between data coming from i2b2 and data coming from other sources. If needed (for example when searching by modality), we might have to insert some of the i2b2 ontology tools for both sources.
 
* Darren mentioned that some PACS (such as cardio) might not generate a specific ID like the radiology PACS. There will thus be an option to append data from the different PACS at the same institution. Ex: PI searches MGH cardiology PACS, get a patient list. He will then reload the same MRN into MGH oncology PACS and append the results.
 

Latest revision as of 16:04, 13 July 2010

Home < CTSC:ARRA.071310

Back to CTSC:ARRA supplement

Agenda

  • Update
  • uxp and UI design: workflow analysis


Harvard Catalyst Medical Informatics group Meeting Minutes July 13, 2010

In attendance:

  • Bill Wang
  • Wendy Plesniak
  • Chris Herrick
  • Darren Sack
  • Shawn Murphy
  • Cynthia Lee
  • Steve Pieper
  • Randy Gollub
  • Jesse Wei
  • Bill Tellier
  • Mark Anderson (phone)


Meeting Minutes

Update

  • Chris reports that the phase 2 software is now ready for deployment. The MGH site will be first.
  • BIDMC Radiology IT team project is still on waiting status and Jesse continues to monitor progress. Most recent estimate of date for final review is August.

Need to establish an appropriate repository for mi2b2 source code

  • Discussed pros and cons of various options (continue as part of i2b2, make it part of CDash, set up another tool). Long term goals are to have a software repository that can be open to the public, able to have contributions made from the community, and to completely protect all site specific information. Plan is for Shawn to add Steve to the Partners i2b2 IRB so he can view source code and also learn about the i2b2 code repository. After he reviews the situation he will come back to this group to to make a recommendation.

Osirix

  • The question was raised as to whether Osirix, the most mature stand alone DICOM viewing tool (Mac only), would be of any use in the mi2b2 project. Group sees some value in thinking about how to develop a mi2b2 to Osirix plug-in as a way of greatly enhancing the dissemination of our final product. Will revisit this in the future.

Workflow analysis

  • Discussed new revision based on input from last week now has 5 stages: 1. Select site/department; 2. Scout for information available on system using site-specific identifiers; 3. Form a "Study Set" to request; 4. Chose a Transfer destination and request studies; 5. Check transfer status & view transferred images.
  • Cynthia and Wendy have generated a list of questions about the specific details that can be learned by the automatic search functions to use in our filters. Jesse points to standard DICOM feature lists. He offered to share screen shots of the "drill down" query terms on his system.