Difference between revisions of "CTSC:ARRA.012610"

From NAMIC Wiki
Jump to: navigation, search
Line 28: Line 28:
  
 
* DICOM conformance statement of each PACS
 
* DICOM conformance statement of each PACS
−
** The goal is to make sure that each PACs has the right functionality so we can be sure that the functions we are building are working against the different PACS.
+
** The goal is to make sure that each PACS has the right functionalities so we can be sure that the functions we are building are working against the different PACS.
 
** Sometimes the statement might be something difficult to manipulate.  
 
** Sometimes the statement might be something difficult to manipulate.  
 
** The persons responsible for this task are:
 
** The persons responsible for this task are:
Line 50: Line 50:
 
* Put phantoms into mi2b2 test PACS system on cloud computing infrastructure:
 
* Put phantoms into mi2b2 test PACS system on cloud computing infrastructure:
 
** We want to get images from each PACS from the different institutions. In the interest of patient privacy, we will use phantoms.
 
** We want to get images from each PACS from the different institutions. In the interest of patient privacy, we will use phantoms.
−
** We have to check that there are phantoms available and that the info in the dICOM header is intact:
+
** We have to check that there are phantoms available and that the info in the DICOM header is intact:
 
** The persons responisble for this task are:
 
** The persons responisble for this task are:
 
*** Jesse Wei (BIDMC)
 
*** Jesse Wei (BIDMC)

Revision as of 03:25, 2 February 2010

Home < CTSC:ARRA.012610

Back to CTSC:ARRA supplement

Agenda

i2b2 to XNAT to DICOM architecture and workflow

Harvard Catalyst Medical Informatics group Meeting Minutes January 19, 2010

In attendance:

  • Valerie Humblet
  • Mike Mendis
  • Shawn Murphy
  • Bill Tellier
  • Mark Anderson
  • Randy Gollub
  • Yong Gao
  • Wendy Plesniak
  • Alex Zeitsev
  • Charles McGow
  • Dan Marcus
  • Ron Kikinis
  • Jesse Wei
  • Karl Helmer


  • DICOM conformance statement of each PACS
    • The goal is to make sure that each PACS has the right functionalities so we can be sure that the functions we are building are working against the different PACS.
    • Sometimes the statement might be something difficult to manipulate.
    • The persons responsible for this task are:
      • Steve Piper (mi2b2)
      • Jesse Wei (BIDMC)
      • Bill Tellier and Paul Lamonica (CHB)
      • Katie Andriole (BWH), to be confirmed
      • Thomas Schultz (MGH)


  • Obtain samples from DICOM queries:
    • CFIND, CGET, CECHO and CCANCEL
    • Steve will be the one to understand what we want from the DICOM conformance statement
    • Important considerations:
      • Hierarchical versus relational CFIND. The first one is the standard, you need to know who the patient is before getting the images then the serie that has the modality in it. The second one is more flexible.
      • Understanding use of accession numbers in CFIND statement.


  • Put phantoms into mi2b2 test PACS system on cloud computing infrastructure:
    • We want to get images from each PACS from the different institutions. In the interest of patient privacy, we will use phantoms.
    • We have to check that there are phantoms available and that the info in the DICOM header is intact:
    • The persons responisble for this task are:
      • Jesse Wei (BIDMC)
      • Bill Tellier (CHB)
      • Mark Anderson (BWH)
      • to be designated (MGH)


Retrieved from "https://www.na-mic.org/w/index.php?title=CTSC:ARRA.012610&oldid=48216"