What else for tomorrow?

17 Nov gpc-dev meeting 
notes<https://docs.google.com/document/d/1rTb-DUjuJ83zu-SLfs31IgfUsTYTdNemowDgZquBSag/edit#>

current proposal:

________________________________


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

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

     *   roll: all 12 
DevTeams<https://informatics.gpcnetwork.org/trac/Project/wiki/DevTeams> 
represented? KUMC, CMH, UIOWA, WISC, MCW, MCRF, UMN, UNMC, UTHSCSA (regrets: 
Bos), UTSW, MU, IU
Reminder - put institution after your name in GoToMeeting preferences

        *   today's scribe: TBD

     *   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 
(note also recent ticket comments 
report<https://informatics.gpcnetwork.org/trac/Project/report/13>):

        *
     *   Next Meeting: 24 November Scribe Volunteer?

  2.  Milestone: 
cohort-char1<https://informatics.gpcnetwork.org/trac/Project/milestone/cohort-char1>

     *   #404<https://informatics.gpcnetwork.org/trac/Project/ticket/404> FYI: 
stay tuned for instructions on sharing de-id survey results

  3.  Milestone:bc-agg-1

     *   #385 Collect BC 'Patient Mapping File' from from breast cancer survey 
sites<https://informatics.gpcnetwork.org/trac/Project/ticket/385>

  4.  Milestone: 
data-quality-q3<https://informatics.gpcnetwork.org/trac/Project/milestone/data-quality-q3>

     *   #196 (Should the "active patient" be based on visits or encounters?) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/196#comment:4> 
invalid - as-designed

     *   refined scope for #327 
<https://informatics.gpcnetwork.org/trac/Project/ticket/327> Gather 2015 3rd, 
4th quarterly QA results

        *   #290<https://informatics.gpcnetwork.org/trac/Project/ticket/290> 
integrate interim report enrollment data collection with quarterly QA review

        *   #326<https://informatics.gpcnetwork.org/trac/Project/ticket/326> 
Quality checks for terminology alignment (with fact volume) for GPC ontologies

        *   #351<https://informatics.gpcnetwork.org/trac/Project/ticket/351> 
Race, ethnicity data quality checks don't match babel counts

  5.  Milestone: 
data-domains3<https://informatics.gpcnetwork.org/trac/Project/milestone/data-domains3>

     *   #78 (shared GPC RxNORM/NDFRT medications ontology) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/78#comment:22>

     *   #67 (Demographics ontology and value sets, e.g. age) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/67#comment:37>

     *   #158 (usable view of LOINC lab terms) 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/158#comment:44>

     *   milestone target clarified: reproducible GPC, CDM refresh 
(#160<https://informatics.gpcnetwork.org/trac/Project/ticket/160>)

  6.  Milestone: 
drn-query-1<https://informatics.gpcnetwork.org/trac/Project/milestone/drn-query-1>

     *   Notes from 11 Nov meeting with DSSNI?

     *   what’s left on 
#240<https://informatics.gpcnetwork.org/trac/Project/ticket/240>?

  7.  Milestone: 
cohort-char-als<https://informatics.gpcnetwork.org/trac/Project/milestone/cohort-char-als>

     *   #380: follow-up from Nov 12 
meeting<https://informatics.gpcnetwork.org/trac/Project/ticket/380#comment:6>

  8.  Milestone: 
bariatric-study-data<https://informatics.gpcnetwork.org/trac/Project/milestone/bariatric-study-data>

     *
#283: determine GPC funding status for    bariatric 
study<http://listserv.kumc.edu/pipermail/gpc-dev/2015q4/002227.html>   McClay, 
James C
  9.  HERON etl-dev

     *   #410 (unit conversion in HERON flowsheet ETL) opended, 
closed<https://informatics.gpcnetwork.org/trac/Project/ticket/410#comment:1>

________________________________

--
Dan

_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev

Reply via email to