Difference between revisions of "CTSC:ARRA.011210"
From NAMIC Wiki
| Line 36: | Line 36: | ||
[[image:mi2b2.png]] | [[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. | ||
| + | ** 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. | ||
| + | ** (*) 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. | ||
| + | ** patient: in i2b2 there is a structure to ensure that the access tho their 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. How is XNAT prepared to deal with MRN? | ||
Revision as of 18:50, 15 January 2010
Home < CTSC:ARRA.011210Back to CTSC:ARRA supplement
Agenda
- i2b2 to XNAT to DICOM workflow
Harvard Catalyst Medical Informatics group Meeting Minutes January 12, 2010
In attendance:
- Valerie Humblet
- Mike Mendis
- Shawn Murphy
- Bill Tellier
- Mark Anderson
- Randy Gollub
- Yong Gao
- Paul Lamonica
- Steve Piper
- Wendy Plesniak
- Alex Zeitsev
Discussion
- There are 3 components in this project:
- the software development part.
- 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.
- i2b2 to XNAT to DICOM workflow
- 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.
- 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.
- (*) 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.
- patient: in i2b2 there is a structure to ensure that the access tho their 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. How is XNAT prepared to deal with MRN?
