Please find the agenda for the DEV call tomorrow (9/15) at 11:00 AM below:

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

·         Meeting ID and access code: 686-845-717; call +1 (267) 507-0008

·         Meeting notes 
(#12<https://informatics.gpcnetwork.org/trac/Project/ticket/12>): September 16 
notes OK? today's scribe: Nate Apathy

·         Roll: all 10 DevTeams represented? Comments on the agenda?

o   KUMC, CMH, UIOWA, WISC, MCW, MCRF, UMN, UNMC, UTHSCSA, UTSW

·         new/closed/reopened tickets

o   Closed

§  # 78<https://informatics.gpcnetwork.org/trac/Project/ticket/78#comment:9> - 
shared GPC RxNORM/NDFRT medications ontology

§  # 76<https://informatics.gpcnetwork.org/trac/Project/ticket/76> - share GPC 
i2b2 metadata CSV files with GPC via PCORNet central desktop

§  #153<https://informatics.gpcnetwork.org/trac/Project/ticket/153> - Update 
UMN terms on Babel

§  #36 <https://informatics.gpcnetwork.org/trac/Project/ticket/36>  - Enhance 
MCRF i2b2 Population

§  #107<https://informatics.gpcnetwork.org/trac/Project/ticket/107> - GPC trac 
account password troubles

·         next meeting: September 23

o   Scribe volunteer?

2.       Follow-up on the Annotated Data Dictionary - any questions? Issues? 
All sites posted?

·         KUMC, CMH, UIOWA, WISC, MCW, MCRF, UMN, UNMC, UTHSCSA, UTSW

3.       Enrollment/Catchment

4.       Milestone 3.17/PopMedNet

·         Discuss moving to Distributed Responses

·         Need names for technical contact at each site to send to PCORnet DRN

5.       Review work by site: 
https://informatics.gpcnetwork.org/trac/Project/report/11

6.       Other topics?

Thanks,
Laurel

______________________________________________________________________
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