We received feedback/questions from PCORI. I have some questions for everyone regarding how refreshes/archiving should be done for it.
Here are the questions from PCORI: 1)We would like to understand more about your processes for refreshing your DataMart and creating a locked/static version of each DataMart refresh. Can you please describe your processes for us? When you refresh your DataMart, do you perform a complete update or a partial update (e.g. updating new or changed information)? 2)Given the time necessary to refresh your data, what is the latest data that will be available in the DataMart relative to the date of query receipt? For example, if we send you a DC query on July 1, what is the date of the latest information you expect to be captured in the DataMart? For UTSW, I currently have the data in Oracle and we can do a complete update every month when we update our i2b2. But, when we do so, it will wipe out and re-load all of the data. What are others doing to create a “locked/static” version? We’re also still creating our CDM from the de-identified, date shifted version of i2b2. Are other GPC sites doing the same? Or have you eliminated date shifting on the CDM? I could fairly easily use our pre-shifted version of i2b2 but want to be consistent with other sites with regards to the process. I’m also wondering if the date shifting may be causing our vitals data to look like it’s spiking around 1 year ago. I haven’t created a non-date shifted version to compare to through. Thanks, Phillip From: <[email protected]<mailto:[email protected]>> on behalf of Dan Connolly <[email protected]<mailto:[email protected]>> Date: Monday, August 1, 2016 at 1:32 PM To: "<[email protected]<mailto:[email protected]>>" <[email protected]<mailto:[email protected]>> Subject: gpc-dev 2 Aug agenda and meeting notes What else for tomorrow? * gpc-dev 2 Aug shared notes<https://docs.google.com/document/d/1dHIQMVRWR8y6BpXoX3BPD8fGXL01hw9nrjVSrb76DLA/edit>; scribe: MU ________________________________ 1. Convene, take roll, review records and plan next meeting * Meeting ID and access code: 817-393-381<https://global.gotomeeting.com/meeting/join/817393381>; call +1 (571) 317-3131 * roll: all 12DevTeams<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams> represented? KUMC, CMH, UIOWA, WISC, MCW, MCRF, UMN, UNMC, UTHSCSA, UTSW, MU, IU Reminder - put institution after your name in GoToMeeting preferences * today's scribe: MU * comments on the agenda? on last week’s notes (#12<https://informatics.gpcnetwork.org/trac/Project/ticket/12>)? Recent tickets opened/closed<https://informatics.gpcnetwork.org/trac/Project/timeline> - FYI * ... * #520 (DataBuilder limited to one terms / concepts table) created<https://informatics.gpcnetwork.org/trac/Project/ticket/520> minor * #409 (submit year 1 sustainability plan (milestone 2.7.1)) closed<https://informatics.gpcnetwork.org/trac/Project/ticket/409#comment:6> * Next Meeting: 9 Aug - scribe? Note LRU schedule<https://informatics.gpcnetwork.org/trac/Project/ticket/12#comment:92>, which nominates MCW, MCRF, … 2. Feasibility Query: National Diabetes Amputation Prevention Study (NDAMPS)<http://listserv.kumc.edu/pipermail/gpc-dev/2016q3/003065.html> Mei Liu: “Some learning points from the experience: …” 3. Milestone:tapir-trial-1 <https://informatics.gpcnetwork.org/trac/Project/milestone/tapir-trial-1>#521<https://informatics.gpcnetwork.org/trac/Project/ticket/521>identify providers in TAPIR trial<https://informatics.gpcnetwork.org/trac/Project/ticket/521>: “KUMC is going first; MCW and UTSW to follow.” 4. Next-d geocoding #508<https://informatics.gpcnetwork.org/trac/Project/ticket/508>Handling small geographic areas in geocoded data for Next-D<https://informatics.gpcnetwork.org/trac/Project/ticket/508> closed fixed: “... using a non-derived/randomly generated id for the Geo-ID to link up the tables would satisfy safe harbor ...” 5. #402<https://informatics.gpcnetwork.org/trac/Project/ticket/402> enhanced data resource from GPC Cohort Characterization study with CMS data: “the [RESDac] project was approved” * CompleteData<https://informatics.gpcnetwork.org/trac/Project/wiki/CompleteData> -> GROUSE 6. #459<https://informatics.gpcnetwork.org/trac/Project/ticket/459>How to add GPC sites to SNOW SHRINE network? <https://informatics.gpcnetwork.org/trac/Project/ticket/459>“In discussion of the health systems payor demonstration project, Russ learned that SCILHS is willing to host a SHRINE network for PCORNet.” 7. Milestone:bc-dx-px<https://informatics.gpcnetwork.org/trac/Project/milestone/bc-dx-px> - #448 done! Yay! How many hours of effort did it take? I have estimates from MCW, UMN. I'd appreciate estimates from UIOWA, MCRF, WISC, UNMC, UTSW. 8. Milestone:cohort-char-bc-db <https://informatics.gpcnetwork.org/trac/Project/milestone/cohort-char-bc-db>#358<https://informatics.gpcnetwork.org/trac/Project/ticket/358>NAACCR ETL: update all [8 participating] sites to include summary of treatment etc.<https://informatics.gpcnetwork.org/trac/Project/ticket/358> * Participating sites * KUMC - ETL done locally; need to update babel * UIOWA * WISC * MCW * MCRF * UMN * UNMC * UTSW - full marks! * Other sites * CMH * IU * MU * UTHSCSA ________________________________ -- Dan ________________________________ UT Southwestern Medical Center The future of medicine, today.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
