1.  Convene, take roll, review records and agenda; plan next meeting
     *   Meeting ID and access 
code:686-845-717<https://global.gotomeeting.com/meeting/join/686845717> call +1 
(267) 507-0008
     *   Scribe: from UW Madison. Let's use gotomeeting chat for near-real-time 
feedback to speakers on what the meeting heard.
     *   roll call: Ideally we'd copy-and-paste the attendee list from 
gotomeeting, but that feature seems to require administrative access. So let's 
just note which of the 10 sites are represented.
     *   Proposed: to accept 5 Feb 
minutes<http://www.mail-archive.com/[email protected]/msg00110.html> as 
a true record, with thanks to Supreet and Justin. I'm not sure why their 
message of February 05, 2014 2:45 PM isn't in the web archive, but it has the 
same content as my reply.
     *   Agenda review: I have several requests from Jim C. where I was hoping 
to see written (email) discussion in advance. But perhaps near-real-time text 
chat notes will work for keeping us in sync.
     *   next meeting is Tue, 18 Feb, 11am. Jim C. to send agenda and chair (or 
cancel). regrets: Connolly.
  2.  data security: volunteer to start a conversation on de-identification of 
dates with PCORI TF? 
#26<http://informatics.gpcnetwork.org/trac/Project/ticket/26>
     *   note milestone:toledo-bend due April
  3.  Data model review comments from Jay: 
ticket:10#comment:5<http://informatics.gpcnetwork.org/trac/Project/ticket/10#comment:5>
     *   note milestone:platte due May
<http://informatics.gpcnetwork.org/trac/Project/ticket/10#comment:5>
  4.  data elements for breast cancer cohort characterization: follow-up on 
input from Chrischilles in 
ticket/32#comment:8<http://informatics.gpcnetwork.org/trac/Project/ticket/32#comment:8>?
 Note also a few queries by Russ and Tamara in babel Feb 6, Feb 12.
  5.  Epic/Cerner/Marshfield liaison: next step? due date? 
#13<http://informatics.gpcnetwork.org/trac/Project/ticket/13>
  6.
Report from PCORI Data Standardization task force call 2/6/14 (JRC)
  7.
Discussion of hardware configurations for i2b2 (JRC)
  8.
Site homework in preparation for hackathon (JRC)
  9.
AMIA submission strategy fall 2014 (JRC)
  10. ticket news and status, FYI:
     *   <http://informatics.gpcnetwork.org/trac/Project/ticket/37> Stay tuned 
to trac timeline<http://informatics.gpcnetwork.org/trac/Project/timeline> if 
you want to know about all new tickets, wiki edits, etc.
        *   e.g. Ticket #37 (Modifiers not showing up in 
Babel)<http://informatics.gpcnetwork.org/trac/Project/ticket/37>
        *   Feel free to discuss any of them at any time in mail to gpc-dev.
        *   It's possible to have all ticket changes sent to all of gpc-dev, I 
think, but I doubt that's cost-effective.
        *   Use the RSS feed if you like. Tune to just tickets, etc.
     *   popmednet status FYI: Bhargav to prepare for news from PCORI. 
#14<http://informatics.gpcnetwork.org/trac/Project/ticket/14>
     *   patient, fact counts: Russ and Nathan are at UTHSCSA 
#1<http://informatics.gpcnetwork.org/trac/Project/ticket/1>
  11. plan more i2b2 demos

--
Dan

Reply via email to