Any chance you can elaborate with further technical details? Ideally, supply enough information that someone could reproduce your work. Can you share the SAS code that goes from Mini-Sentinel to i2b2? Or do you have any design documentation for it?
Or just elaborate on the experience. When did you start on the Mini-Sentinel to i2b2 work? How many person-months of effort would you estimate it took? What were the major challenges? etc. -- Dan ________________________________ From: Verhagen, Laurel A [[email protected]] Sent: Tuesday, June 10, 2014 6:08 PM To: Dan Connolly; [email protected] Subject: RE: gpc-dev 10 June agenda: what's up at your site? Summary from Marshfield, with elaboration on #3 as requested by Dan on the call earlier today: 1. Infrastructure: a. I2b2: upgraded to v1.6.9; debating v1.7. b. SHRINE: Set up v1.10, but plan to convert to v1.15 (or v1.16?) based on the demo Phillip gave of the metadata mapping capabilities. 2. Refreshes: a. Working on automation; historically this effort has been manual, because we’re typically adding several new data sources that result in quite a bit of QA/troubleshooting. 3. Data sources/population: a. Marshfield has unique challenges: 20+ year old proprietary EHR, health plan data, etc.; we’re also part of the Cancer Research Network and Mini-Sentinel. b. The latter two are multi-site networks with standard data models. We have SAS code (I think) that transforms and populates those models from our data warehouse tables. There are defined populations associated with each. c. As part of recent efforts to increase our GPC/i2b2 population, and switch from a Dental focus to something more global (ticket #36<https://informatics.gpcnetwork.org/trac/Project/ticket/36>), we converted our source from the data warehouse to the pre-processed Mini-Sentinel tables. This gives us QA for free. d. RxNorm: As part of a separate project, we’ve used MedEx to map as many of our drugs--orders, NLP mined old orders, and fills--as possible to RxNorm. e. NAACCR: working on pulling this to integrate. We have access, just are working through how to understand, manipulate, and load those sources. 4. PopMedNet: working on establishing the GPC node. Thanks, Laurel From: [email protected] [mailto:[email protected]] On Behalf Of Dan Connolly Sent: Monday, June 09, 2014 2:33 PM To: [email protected] Subject: RE: gpc-dev 10 June agenda: what's up at your site? What are the main (informatics related) things going on at your site? Bonus points for letting everybody know by email before tomorrow's call. Otherwise, we'll talk about it then. The work by site list<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams#WorkBySite> is getting a little stale; here's hoping we can update it. -- Dan ________________________________ From: Dan Connolly Sent: Monday, June 09, 2014 12:16 PM To: [email protected]<mailto:[email protected]> Subject: gpc-dev 10 June agenda: in progress I'm running a bit behind today; stay tuned... -- Dan ________________________________ The contents of this message may contain private, protected and/or privileged information. If you received this message in error, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained within. Please contact the sender and advise of the erroneous delivery by return e-mail or telephone. Thank you for your cooperation.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
