Hi everyone, 

Below find the agenda for gpc-dev on Tuesday, Jan 15 at 11:00 a.m. CT. Our 
scribe will be UTSW.

Connect:
https://global.gotomeeting.com/meeting/join/817393381
access code: 817-393-381; call +1 (571) 317-3131

Link to notes:
https://docs.google.com/document/d/1PnUr3KYuAoiuRQRE1xs0uGRSJZ41eTUYBj0_QMZ7aTw/edit#

Let me know if you have additions/changes?

Thanks,
Laurel
--
1. Convene, take roll, review records and plan next meeting(s)
​       Roll; comments on the agenda? (ref SoftwareDev#tracking)
        Reminder - put site after your name in GoToMeeting preferences
        GPC DevTeams represented? KUMC, UIOWA, MCW, MCRI, UNMC, UTHSCSA, UTSW, 
MU, IndianaU, Utah, Allina, Intermountain
        Today's scribe: UTSW
        Comments on last week’s notes? (#12)
        Recent tickets opened/closed - FYI (i.e. not intended for discussion)
                Opened - GROUSE data refresh tickets: #731, #732, #733, #734, 
#735, #736, #737 
                Closed - #723 Finder File UNMC; #728 Finder File UTHSCSA
        Next meeting(s)/scribe: Jan 22 Marshfield? IU?
        
2. RCR - milestones:cancer-rcr-1; cancer-rcr-3 / Grouse-3
        Updates? (Remove from agenda?)

3. PCORnet CDM/Data Changes
        Data Curation Dates - REMINDER
                Cycle 6, Refresh 1 - Distributed 1/14/19; Due 2/04/19
                Cycle 6, Refresh 2 - Distributed 4/01/19; Due 4/22/19
        People Centered Research Foundation (PCRF)/PCORnet 2.0
                Updates?

4. GROUSE 
        FinderFiles - deadline to ship to GDIT is 1/4/19
                #725 IU - 
                #727 Allina, Utah, Intermountain and UIHC - Pending regulatory 
aspects. 
        Data Refresh Tracking - Check that the contacts are correct for your 
site.
                #731 KUMC
                #732 Iowa
                #733 UNMC
                #734 Marshfield
                #735 MU
                #736 UTSW
                #737 MCW
                Do other sites have approvals for submitting data for GROUSE?
        Continuing review
                IRB meeting soon, anticipate early distribution 

5. #711/ DROC #40: Predictive Models for Acute Kidney Injury using PCORnet CDM
        Updates?

6. NextD - sites: IOWA, UNMC, MCW, IU, KUMC, UTSW, MU
        #713 - NextD Data Refresh; based on CDM v4.0; pending #715
                January 5 deadline
                UNMC - 
                UTSW - 
7. #718/ DROC #42: Comparison of Outcomes of Unilateral Mastectomy and 
Contralateral Prophylactic Mastectomy with Reconstruction
        Due date is Jan 11; UNMC, UTSW to deliver by end of the month 

8. DEMO - UNMC presenting on NDC to RxNorm Mapping and allergy extract and 
coding
        Mapping files posted ahead of the meeting?

9. Tumor Registry Updated NAACCR Format; 
        NAACCR v 18 formatting will be creating needs for ETL changes; 
         
10. milestone:snow-shrine-2 , milestone:snow-shrine-3
        Group will look at expanded ACT membership and SHRINE over GROUSE. Jim 
Campbell to update trac as appropriate.
        #411 - Align SNOW SHRINE terminology with ARCH and ACT ontology for 
interoperation of query 
11. milestone:text-notes-1 De-identification; use case: #573
        Pushed out 6 months, per Hackathon6
12. Other topics?
        Upcoming demos:
                1/22 - MCW Honest Broker Data Delivery; additional staff from 
MCW to attend with Kris
                Additional topics?


______________________________________________________________________
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
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to