What else for tomorrow?

UNMC is scheduled to scribe.
https://docs.google.com/document/d/1m2RlFu_1HDaJTqAf-g63e8pXU2GBKLiMtJxQrprDuJU/edit

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; comments on the agenda? (ref 
SoftwareDev#tracking<https://informatics.gpcnetwork.org/trac/Project/wiki/SoftwareDev#tracking>)
Reminder - put site after your name in GoToMeeting 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: UNMC

     *   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(s)/scribe: July 30 Scribe: IU? UTHSCSA?

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

  2.  PCORnet CDM refresh (DRN OC)
c6r3 due July 24.

     *   Status by site:

        *   KUMC

        *   UIOWA

        *   MCW - done

        *   MCRI

        *   UNMC

           *   HELP on Loading MS SQL dates to SAS datasets for CDMV41 
tables<http://listserv.kumc.edu/pipermail/gpc-dev/2019q3/005267.html>   
Campbell, James R

        *   UTHSCSA - done

        *   UTSW

        *   MU

        *   IndianaU

           *   Jarrah / IU - hitting some errors; will send details to ask if 
others have seen likewise

        *   Utah

        *   Allina - done

        *   Intermountain

  3.  
Milestone:tumor-reg-18<https://informatics.gpcnetwork.org/trac/Project/milestone/tumor-reg-18>
 due July 31

     *   #739<https://informatics.gpcnetwork.org/trac/Project/ticket/739> HERON 
NAACCR ETL outdated by 
v18<https://informatics.gpcnetwork.org/trac/Project/ticket/739>

        *   Susan to ask our Intermountain experts about NAACCR_ID in LOINC

        *   MG to arrange a meeting with the naaccr-xml maintainer
(DC saw some progress 12 Jul)

           *   Maitainer recommends connecint with a NAACCR group that meets 
this Friday at 11am (eastern?) and every other week after. MG is not available 
this week. DC isn’t sure.

        *   
kumc-bmi/naaccr-tumor-data/issues/3<https://github.com/kumc-bmi/naaccr-tumor-data/issues/3>
 xsd:date YYYY-MM-DD vs NAACCR YYYYMMDD

     *   #435 <https://informatics.gpcnetwork.org/trac/Project/ticket/435> Test 
data
Alex: I can follow up with George
MG: I can ask Dmitri

     *   #749<https://informatics.gpcnetwork.org/trac/Project/ticket/749> 
PCORNet style TUMOR 
table<https://informatics.gpcnetwork.org/trac/Project/ticket/749>

        *   Kris: Joan has some specific fields. She submitted an ROA. I have a 
short list of columns I could share.

        *   Brad to keep an eye out for CancerCRG projects in early stages.

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

     *   #597 (spec for crosswalk to accompany i2b2 datamarts for GROUSE) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/597#comment:11> - 
spec looks OK?

  5.  
Milestone:text-notes-1<https://informatics.gpcnetwork.org/trac/Project/milestone/text-notes-1><https://informatics.gpcnetwork.org/trac/Project/ticket/335#comment:93>

     *   #335 (reduce DataBuilder dependencies to i2b2 platform: ant, JVM, 
JDBC, jboss) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/335#comment:93> - 
673e9bb181e7 release attached to 
DataBuilder<https://informatics.gpcnetwork.org/trac/Project/wiki/DataBuilder>

--
Dan

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

Reply via email to