Sorry, I should have been more clear. We have the raw data loaded into our repository and mapped to patients using our MPI. However, we have NOT done any other mappings or loaded the data into i2b2. We were not sure on what the hierarchy within i2b2 should but have since been looking within Babel at what KU and UTSW have done. It looks like both sites have the same hierarchy (Cancer Identification, Demographic, Follow-up, etc). Is this a standard hierarchy based on the NAACCR data? Any guidance/advice/tips for navigating this would be greatly appreciated.
Even though we don't have the data loaded into i2b2 (yet) I think we can still use the data in its current form to run the queries and to get back counts. Regards, Justin Dale Manager - Research Development and Support University of Minnesota Academic Health Center - Office of Information Systems Phone: 612.624.9747 Fax: 612.624.7458 [email protected] On Thu, Aug 7, 2014 at 7:26 AM, Russ Waitman <[email protected]> wrote: > Terrific news Justin! > > > > We were just having a KUMC HERON planning session and noting we need to > use Breast Cancer as a leading case for cross site characterization. Our > ability to do this across UTSW, KUMC, and UNM will be outstanding. Can > you share your latest i2b2 concepts with Nathan so he can post it on > babel. That will let Betsy and the methods team see what we’ve got, > > > > Russ > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Justin Dale > *Sent:* Wednesday, August 06, 2014 11:02 AM > *To:* [email protected] > *Subject:* NAACCR queries > > > > At Minnesota, we now have the NAACCR data loaded into our repository. I > believe there were talks about doing some "pen-and-paper" query across > sites who have this data available. If this is still an option we would > really like to participate. > > > > > Justin Dale > > Manager - Research Development and Support > > University of Minnesota > > Academic Health Center - Office of Information Systems > > Phone: 612.624.9747 > > Fax: 612.624.7458 > > [email protected] >
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
