As I mentioned last week, I'm in a meeting (the LEK) all day, so I'm not preparing an agenda.
I expect we can go as long as we like; I've never seen gotomeeting cut off a meeting. Officially reserving extra time looks challenging; Brittany is not only participating in today's LEK but organizing all the logistics, so I don't expect she has bandwidth to deal with this. Meanwhile, I'll repeat my request to please get the discussion started in substance in email. -- Dan ________________________________________ From: gpc-dev-boun...@listserv.kumc.edu [gpc-dev-boun...@listserv.kumc.edu] on behalf of Campbell, James R [campb...@unmc.edu] Sent: Saturday, August 16, 2014 10:10 PM To: Lindsay Cowell; gpc-dev@listserv.kumc.edu Subject: RE: [gpc-informatics] #144: ETL Annotated Data Dictionary form required by PCORI Hi Lindsay I am good with scheduling a time to just discuss the ETL ADD since I suspect we may need more than an hour to work through everyone's issues. Can I suggest that we add the item to the regular scheduled Tuesday agenda and I will ask KU to add an extra hour onto the call? We can flow over if we need the extra time to agree on standardization issues and I would hope we don't go into the last week of August with questions outstanding. ETL managers or technical leads speak up to the listserv if this is a bad time Jim ________________________________________ From: Lindsay Cowell [lindsay.cow...@utsouthwestern.edu] Sent: Saturday, August 16, 2014 3:53 PM To: Campbell, James R; Phillip Reeder; Susan Morrison; Dipti Ranganathan Cc: gpc-dev@listserv.kumc.edu Subject: Re: [gpc-informatics] #144: ETL Annotated Data Dictionary form required by PCORI Hi Jim, The GPC team at UTSW met yesterday to work on completing the ETL Annotated Data Dictionary. We have many of the same questions now as we had when generating counts for the original count table. We would like to request a call during which we attempt to agree across the 10 sites on a standardized way to generate the counts (or as close as possible). Perhaps this can happen during the next two gpc-dev calls? Or perhaps we need a separate time. Thank you, Lindsay On 8/14/14, 10:17 PM, "Campbell, James R" <campb...@unmc.edu> wrote: >Nathan >I think that I have responsibility for this deliverable and so you can >forward Wisconsin response as attachment to the ticket and I will monitor >and collate for the network response to PCORI. >Jim > >James R. Campbell MD >campb...@unmc.edu >Office: 402-559-7505 >Secretary: 402-559-7299 >Pager: 402-888-1230 > >> On Aug 14, 2014, at 2:56 PM, "Wilson Nathan" <nwil...@uwhealth.org> >>wrote: >> >> Where or to whom should I send the Wisconsin data dictionary? >> >> Nathan Wilson >> >> -----Original Message----- >> From: gpc-dev-boun...@listserv.kumc.edu >>[mailto:gpc-dev-boun...@listserv.kumc.edu] On Behalf Of GPC Informatics >> Sent: Thursday, August 07, 2014 1:17 PM >> To: campb...@unmc.edu; ngra...@kumc.edu; dconno...@kumc.edu >> Cc: gpc-dev@listserv.kumc.edu >> Subject: Re: [gpc-informatics] #144: ETL Annotated Data Dictionary form >>required by PCORI >> >> #144: ETL Annotated Data Dictionary form required by PCORI >> ---------------------------------+------------------------ >> Reporter: campbell | Owner: ngraham >> Type: task | Status: assigned >> Priority: major | Milestone: popmednet >> Component: data-stds | Resolution: >> Keywords: ETL Data Dictionary | Blocked By: 145, 146 >> Blocking: | >> ---------------------------------+------------------------ >> >> Comment (by ngraham): >> >> I worked on adding the [https://bitbucket.org/njgraham/pcori-annotated- >> data-dictionary/commits/eb6e04281dfd9fd92758da1d51c7baf1d38e8e2e >>diagnosis CDM view] but ran in to performance issues - see >>ticket:146#comment:5. I plan to spend a little time trying to tune the >>query. >> >> -- >> Ticket URL: >><http://informatics.gpcnetwork.org/trac/Project/ticket/144#comment:9> >> gpc-informatics <http://informatics.gpcnetwork.org/> >> Greater Plains Network - Informatics >> _______________________________________________ >> Gpc-dev mailing list >> Gpc-dev@listserv.kumc.edu >> http://listserv.kumc.edu/mailman/listinfo/gpc-dev > >The information in this e-mail may be privileged and confidential, >intended only for the use of the addressee(s) above. Any unauthorized use >or disclosure of this information is prohibited. If you have received >this e-mail by mistake, please delete it and immediately contact the >sender. > >_______________________________________________ >Gpc-dev mailing list >Gpc-dev@listserv.kumc.edu >http://listserv.kumc.edu/mailman/listinfo/gpc-dev ________________________________ UT Southwestern Medical Center The future of medicine, today. ------------------------------------------------------------------------- This message was secured by ZixCorp(R). The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
