What else for tomorrow?

  *   shared notes for 10 
Oct<https://docs.google.com/document/d/1dDpw2vV7Zk8Aq3TO56FUDMkYXrB-brEI0w_lKYVPKXM/edit>;
 scribe: MCRF

snapshot:

________________________________


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

     *   11:00am 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 institution after your name in GoToMeeting 
preferences

        *   all 12 GPC 
DevTeams<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams> 
represented? KUMC, CMH, UIOWA, WISC, MCW, MCRF/MCRI, UMN, UNMC, UTHSCSA, UTSW, 
MU, IU

        *   Today’s meeting is joint with the Cancer RCR project

        *   today's scribe: MCRF

     *   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 
(i.e. not intended for discussion)

        *   ...none this week...

     *   Next Meeting:  24 Oct. scribe: ???

        *   17 Oct cancelled due to conflict with GPC LEC 16-17 
Oct<http://www.gpcnetwork.org/?q=2017LEC>

        *   Note LRU scribe schedule in 
#12<https://informatics.gpcnetwork.org/trac/Project/ticket/12#comment:97>

  2.  
HackathonFive<https://informatics.gpcnetwork.org/trac/Project/wiki/HackathonFive>
 plann Feb 2018

     *   Dates for HackathonFive 
survey<https://redcap.kumc.edu/surveys/?s=RY8FAAJ7J3>

  3.  
Milestone:cancer-rcr-1<https://informatics.gpcnetwork.org/trac/Project/milestone/cancer-rcr-1>
 due 13 Oct
​Cancer RCR Aim 
1<https://docs.google.com/spreadsheets/d/1fY5rR0W4tUEslxjLcXo0J9kDcP2IY7G_i_7mKGr2S9o/edit#gid=1874960144>
 schedule spreadsheet; RCR listserv: 
gpc-rcr<http://listserv.kumc.edu/mailman/listinfo/gpc-rcr>

     *   Putting med info in CDM (row 6)
RW: to meet with Keith M. of DRN OC done:
[Gpc-rcr] using Cancer RCR project for testing CDM 4.0 med    admin 
table<http://listserv.kumc.edu/pipermail/gpc-rcr/2017-October/000011.html>   
Russ Waitman

     *   Site status (Brian G / UIOWA will add details below)

        *   UNMC

        *   Indiana University (IU)

        *   Louisiana State University (LSU) Health

        *   Marshfield Clinic: LV

        *   Medical College of Wisconsin (MCW)

        *   Missouri University (MU)

        *   Medical University of South Carolina (MUSC)

        *   U Florida

        *   UIOWA - Smith

        *   KUMC - Chandaka / Connolly 
#640<https://informatics.gpcnetwork.org/trac/Project/ticket/640>

        *   UMN - McKay

        *   UTSW

        *   Vanderbilt

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

     *   #581 (Crosswalk files for the remaining 4 GPC sites back from GDIT) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/581#comment:14> 
fixed

     *   #623 (training for GROUSE SQL queries) closed 
fixed<https://informatics.gpcnetwork.org/trac/Project/ticket/623#comment:3>

     *   #595 (collect several i2b2 datamarts for GROUSE) closed
<https://informatics.gpcnetwork.org/trac/Project/ticket/595#comment:39>Gold 
stars for getting datamarts in before the LEC: MCW, UNMC, MCRF / MCRI, and UTSW

     *   #644 (collect remaining i2b2 datamarts for GROUSE) 
created<https://informatics.gpcnetwork.org/trac/Project/ticket/644> - anybody 
want to race with IU for the next gold star?

  5.  
Milestone:snow-shrine-1<https://informatics.gpcnetwork.org/trac/Project/milestone/snow-shrine-1>,
 
Milestone:snow-shrine-2<https://informatics.gpcnetwork.org/trac/Project/milestone/snow-shrine-2>

     *   #631<https://informatics.gpcnetwork.org/trac/Project/ticket/631> 
NAACCR Tumor Registry query via GPS SNOW 
SHRINE<https://informatics.gpcnetwork.org/trac/Project/ticket/631> - UMN too!

        *   See also 
NAACCR_ETL<https://informatics.gpcnetwork.org/trac/Project/wiki/NAACCR_ETL>,   
#185 (GPC cancer tumor registry ontology) 
reopened<https://informatics.gpcnetwork.org/trac/Project/ticket/185#comment:11>

     *   #532<https://informatics.gpcnetwork.org/trac/Project/ticket/532> SNOW 
SHRINE node at UNMC with SCILHS PCORnet ontology
<https://informatics.gpcnetwork.org/trac/Project/ticket/532>News?

     *   #575<https://informatics.gpcnetwork.org/trac/Project/ticket/575> SNOW 
SHRINE 1.20.1 install for IU
<https://informatics.gpcnetwork.org/trac/Project/ticket/575>News?

     *   #411<https://informatics.gpcnetwork.org/trac/Project/ticket/411> align 
SNOW SHRINE terminology with SCILHS Ontology
<https://informatics.gpcnetwork.org/trac/Project/ticket/411>SNOW Shrine 
Ontology<http://listserv.kumc.edu/pipermail/gpc-dev/2017q4/004314.html>   
Andrew Hangsleben: “Out of curiosity, is there any reason we aren't using the 
PCORnet ontology directly in shrine instead of the shrine ontology + adapter 
mappings?
Reeder: “That was a SCHILS decision. Our goal was to be compatible with their 
shrine, and that is how they did it.   We followed.”
Hangsleben: “but it might be simpler in the future if we used the PCORnet 
ontology. Then we could use an adapter mappings file that maps every term to 
itself like the ACT Shrine setup. Plus there would be no need to maintain the 
duplicate ontology in the database.”

  6.  
Milestone:next-d<https://informatics.gpcnetwork.org/trac/Project/milestone/next-d>

     *   #546<https://informatics.gpcnetwork.org/trac/Project/ticket/546> 
Oracle port of 
NextDextractionCode_12.1.16.sql<https://informatics.gpcnetwork.org/trac/Project/ticket/546>

        *   Github #12 lab_review.csv and/or med_info.csv out-dates create 
table statements<https://github.com/kumc-bmi/nextd-study-support/issues/12>

        *   Github #14 SQLServer code out of date w.r.t. 2017-08-22-AF 
rev.<https://github.com/kumc-bmi/nextd-study-support/issues/14>

     *   #571<https://informatics.gpcnetwork.org/trac/Project/ticket/571> 
characterization of data from next-d GPC sites
<https://informatics.gpcnetwork.org/trac/Project/ticket/571>Mei, how many do 
you have?

________________________________


--
Dan

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

Reply via email to