What else for tomorrow?

MCW is scheduled to scribe.
https://docs.google.com/document/d/185CYDURwRRYPMhe32zXn1YgaCUKWyMmFDtxXKlyew60/edit#

agenda snapshot:

  1.  Convene, take roll, review records and plan next meeting(s)

     *   11:00 a.m. Central Time.
​Meeting ID and access code: 
817-393-381<https://global.gotomeeting.com/meeting/join/817393381>; call +1 
(571) 317-3131

     *   Roll; Reminder - put site after your name in 
GoToMeeting<https://global.gotomeeting.com/meeting/join/817393381> preferences 
GPC DevTeams<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams> 
represented? KUMC, UIOWA, MCW, MCRI,  UNMC, UTHSCSA, UTSW, MU, IndianaU, Utah, 
Allina, Intermountain

        *   Today's scribe: MCW

     *   Comments on the agenda? (ref 
SoftwareDev#tracking<https://informatics.gpcnetwork.org/trac/Project/wiki/SoftwareDev#tracking>)
 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 
(i.e. not intended for discussion)

        *   None this week

     *   Next meeting(s): Jan 7; scribe: Intermountain

        *   Note scribe 
rotation<https://docs.google.com/document/d/1fPoDn0pdVvC-Mct58X7wkGD2rNiId8aNZ9JG_WCbcf4/edit#heading=h.zbjzupqx0rh7>
 appendix

        *   CDM refresh comes out Jan 6; due ~Jan 27

  2.  GPC DROC Feasibility Request 
#57<http://listserv.kumc.edu/pipermail/gpc-dev/2019q4/005411.html> Dr. Chetan 
P. Hans from Mizzou

     *   Data received from Intermountain, MCW, Marshfield, Utah, Missouri, 
Allina, Indiana

     *   KUMC - (10 Dec): query hanging; working with MU folks

  3.  
Milestone:next-d<https://informatics.gpcnetwork.org/trac/Project/milestone/next-d>
 due Dec 18

     *   #713<https://informatics.gpcnetwork.org/trac/Project/ticket/713> NextD 
data refresh<https://informatics.gpcnetwork.org/trac/Project/ticket/713> - 
UIOWA, UNMC, MCW, IU, KUMC, UTSW, MU

  4.  
Milestone:grouse-refresh-2<https://informatics.gpcnetwork.org/trac/Project/milestone/grouse-refresh-2>

     *   #733<https://informatics.gpcnetwork.org/trac/Project/ticket/733> 
GROUSE Refresh 2019 - 
UNMC<https://informatics.gpcnetwork.org/trac/Project/ticket/733> - submitted 
Dec 10

     *   #731<https://informatics.gpcnetwork.org/trac/Project/ticket/731> 
GROUSE Refresh 2019 - 
KUMC<https://informatics.gpcnetwork.org/trac/Project/ticket/731> - ETA: Dec 20

     *   #734 (GROUSE Refresh 2019 - 
Marshfield)<https://informatics.gpcnetwork.org/trac/Project/ticket/734#comment:17>
 reopened Nov 29
owner: dbudine @ KUMC

     *   #751<https://informatics.gpcnetwork.org/trac/Project/ticket/751> 
GROUSE Refresh 2019 - 
Indiana<https://informatics.gpcnetwork.org/trac/Project/ticket/751> - ETA ~Dec 
3 (staff turnover)

     *   #740<https://informatics.gpcnetwork.org/trac/Project/ticket/740> GPC 
feasibity queries using datamarts submitted for GROUSE
<https://informatics.gpcnetwork.org/trac/Project/ticket/740>Nathan @ KUMC has 
just started work on using CDM as an i2b2 datamart.

  5.  #688<https://informatics.gpcnetwork.org/trac/Project/ticket/688> SSDMF / 
DeathDataSharing<https://informatics.gpcnetwork.org/trac/Project/wiki/DeathDataSharing>
 All GPC sites have access to the national death database

     *   Last update(s): Nov 12, …
UIowa doesn’t see the Nov update. DC to check. DC sent encryption / hash keys 
Dec 11.

     *   BG: “can KUMC please advise on what basis sites can incorporate SSDMF 
data into their local data holdings (e.g., research data warehouses) aside from 
/ in addition to informing deceased patients in the CDM proper (e.g., is there 
a license agreement, is this part of the GPC DSA, etc?)? UIOWA would like to 
use the SSDMF to flag deceased patients in our research warehouse generally, 
such that patients who are deceased will also be flagged in the CDM. Before we 
take this step we want to be sure we have permission.”

_______________________________________________
Gpc-dev mailing list
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to