Difference between revisions of "CTSC:ARRA.062910"

From NAMIC Wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 24: Line 24:
 
* Mark Anderson (phone)
 
* Mark Anderson (phone)
 
* Alex Zeitsev (phone)
 
* Alex Zeitsev (phone)
* Karl Helmer (by phone)
+
 
  
 
<br>
 
<br>
Line 38: Line 38:
  
 
* STAR-D workflow analysis
 
* STAR-D workflow analysis
** Wendy and Cynthia have been working hard on the workflow analysis. For images only, not report, to get report, one would go to the RIS.
+
** Wendy and Cynthia presented the first draft of the workflow analysis. The goals are to design an user-friendly Star-D interface layout and behavior, to develop a consistent workflow & presentation that accommodates GUIs that are i2b2-aware and those that aren’t and to work within scope of proposed logic. It is important to note that it is for images only, not report, to get report, one would go to the RIS.
 
** 3 intuitive steps: step 1: site selection and finding patients, step 2: finding studies and destination selection, step 3: transfer status and view.
 
** 3 intuitive steps: step 1: site selection and finding patients, step 2: finding studies and destination selection, step 3: transfer status and view.
** 3 typical paths: 1. Serial top-to-bottom. Change to another site and repeat or log out. 2. Iteratively build up.
+
** 3 typical paths: 1. Serial top-to-bottom. 2. Change to another site and repeat or log out. 3. Iteratively build up.
** what can user save? They can save images. If someone wants to save a patient set, you can get scout list and delete what you don't want. Is is better to save search terms or search results? Here we start with the result, people will enter the accession numbers by hand.  
+
** What can user save? They can save images.  
** Filtering: what is filer-able? view found results, can choose/modify a patient set. For example, push a gender at the top of the list.
+
** Filtering: Filter can not condition query, instead it conditions display of query. (example:view found results, can choose/modify a patient set. For example, push a gender at the top of the list)
** Parallel uxp for STAR-D systems: with or without i2b2, from the user point of view.
+
** Parallel uxp for STAR-D systems: i2b2-aware or not. Only from the user point of view, depending if he the scout list contains i2b2 IDs or site and MRNs
** Embedded concepts
 
 
** Reentrant behavior, what is persistent?  
 
** Reentrant behavior, what is persistent?  
 +
** Embedded concept: few and clear as possible (ex: search site, scout list, query, view image, etc)
  
 
* Next meeting
 
* Next meeting
 
Continue working on the STAR-D workflow analysis.
 
Continue working on the STAR-D workflow analysis.

Latest revision as of 13:59, 30 June 2010

Home < CTSC:ARRA.062910

Back to CTSC:ARRA supplement

Agenda

  • Update from CHildren's hospital
  • Presentation of mi2b2 project at ACRIN meeting
  • uxp and UI design: workflow analysis


Harvard Catalyst Medical Informatics group Meeting Minutes June 29, 2010

In attendance:

  • Valerie Humblet
  • Bill Wang
  • Wendy Plesniak
  • Bill Tellier
  • Chris Herrick
  • Darren Sack
  • Shawn Murphy
  • Cynthia Lee
  • Charles Mc Govern
  • Jesse Wei
  • Mark Anderson (phone)
  • Alex Zeitsev (phone)



Meeting Minutes

  • Update
    • The team finished the development of the phase 2 software. It will be installed over the phase 1 software. Tests will continue this week and installation will happen the 2nd week of July. The new version moves one image at a time. MGH will be the 1st site for installation, it has Santa with all the different imaging facilities (CT, MRI, US, Nuc med). Santa has phantoms and a couple of test patients.
  • Presentation of mi2b2 project at ACRIN meeting
    • The team identified the ACRIN meeting as an excellent venue to introduce the project to a larger audience. There will be a session of the CTSA IWG on September 29 when we can present. Chris and Dan Marcus will do the presentation.
    • There is a t-con of the IWG Steering Committee scheduled for July 19, Randy would like to have a slide deck and a blur (goals, intro) to send to Dan Sullivan before the call.
  • STAR-D workflow analysis
    • Wendy and Cynthia presented the first draft of the workflow analysis. The goals are to design an user-friendly Star-D interface layout and behavior, to develop a consistent workflow & presentation that accommodates GUIs that are i2b2-aware and those that aren’t and to work within scope of proposed logic. It is important to note that it is for images only, not report, to get report, one would go to the RIS.
    • 3 intuitive steps: step 1: site selection and finding patients, step 2: finding studies and destination selection, step 3: transfer status and view.
    • 3 typical paths: 1. Serial top-to-bottom. 2. Change to another site and repeat or log out. 3. Iteratively build up.
    • What can user save? They can save images.
    • Filtering: Filter can not condition query, instead it conditions display of query. (example:view found results, can choose/modify a patient set. For example, push a gender at the top of the list)
    • Parallel uxp for STAR-D systems: i2b2-aware or not. Only from the user point of view, depending if he the scout list contains i2b2 IDs or site and MRNs
    • Reentrant behavior, what is persistent?
    • Embedded concept: few and clear as possible (ex: search site, scout list, query, view image, etc)
  • Next meeting

Continue working on the STAR-D workflow analysis.