CTSC:ARRA.010510
From NAMIC Wiki
Revision as of 19:49, 8 January 2010 by Valerie.humblet (talk | contribs) (→Harvard Catalyst Medical Informatics group Meeting Minutes January 5, 2010)
Home < CTSC:ARRA.010510
Back to CTSC:ARRA supplement
Agenda
- DICOM query retrieve tool
Harvard Catalyst Medical Informatics group Meeting Minutes January 5, 2010
In attendance:
- Valerie Humblet
- Mike Mendis
- Shawn Murphy
- Bill Tellier
- Mark Anderson
- Bill Hanlon
- Todd Perlstein
- Jesse Wei
- The goals of the meetings were:
- to review where we are in the mi2b2 architecture
- to go through the workflow
- to get a couple of assignments and output samples
- Architecture:
- i2b2: PI makes a query, requests images with medical record number (MRN) or accession number. We need to define what is a study at the different institutions. The MRN will probably not be enough, one will need to add the date or the modality etc.
- PACS: Images are extracted and send to XNAT.
- XNAT: new derived data send back to i2b2.
- Accession number: if we send an accession number (acc.#), will we get a study or an image?
- BWH and MGH: it leads to s study. For billing purpose, there are different acc.# for the same study (ex: if one order an MRI/MRA, 2 acc # are generated but they lead to the same study.
- CHB: acc.# leads to a study.
- BIDMC: one acc.# per patient encounter.
- UID:
- In theory, no 2 images will ever have the same UID.
- Each manufacturer is assigned numbers.
- UID is created by the modality.
- You don't need to know it to get data from the PACS, PACS works with acc.#
- UID is for internal accounting and unique identification. If you derived data, you need another UID.